Deployment and Configuration

I have several clients using several SQL server databases that have all been
setup on one machine which they access remotely using terminal services. Each
client has their own software installation with their own set of databases.
So, there would be many client installations on the same machine. How would i
setup reporting services so that each client has their own set of reports?
How would i go about deploying the reports for each client given that the
clients' databases would have different names and hence the connection
strings will be different? Please help!
regardsSet up a datasource for each client - unless you have hundreds, in which case
I am not sure.sql

Deploying SMO/RMO Applications to non-sql2005 servers.

Hi All,
Is it possible to deploy smo/rmo applications to servers and clients without installing the sql server 2005 client tools? Can I simply include the used assenblies or is there any dependance on some ActiveX objects or other configuration actions that must be performed for SMO/RMO to work?
regards,
Tore Birkeland
Yes, it is possible to deploy SMO/RMO applications without installing SQL Server 2005 client tools. The SQL Server 2005 RTM will include SMO redist setup file that you can use for your SMO-based applications. SMO relies on .NET Framework 2.0 and SQL Native Client.

Deploying Report Server behind web servers

We'd like to deploy our report servers behind our web tier in the app tier
in order to prevent our clients from being able to use url access directly.
My main concern has to do with a chance that a client may attempt to alter
the content of report parameters or otherwise probe around.
Our web code is able to forward requests to the report server and render
reports correctly, but toolbar functionality seems to be broken. The web
developer tells me that the toolbar functionality is too stateful, so
paging (as an example) won't work.
Is what we're trying to do (request forwarding) unsupported? Are my fears
regarding exposing the report server in our DMZ unwarranted? If so, I must
be missing something.What about building your own interfaace or getting the Report Stream from
Reporting Webservice to Qrite the Stream to the browser ? There you could
lock down your reporting server and connect to the RS with special lockedup
credentials.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"JoeA" <joea@.nospam.net> schrieb im Newsbeitrag
news:Xns963D69BAFC14Emailmailcom@.207.46.248.16...
> We'd like to deploy our report servers behind our web tier in the app tier
> in order to prevent our clients from being able to use url access
> directly.
> My main concern has to do with a chance that a client may attempt to alter
> the content of report parameters or otherwise probe around.
> Our web code is able to forward requests to the report server and render
> reports correctly, but toolbar functionality seems to be broken. The web
> developer tells me that the toolbar functionality is too stateful, so
> paging (as an example) won't work.
> Is what we're trying to do (request forwarding) unsupported? Are my fears
> regarding exposing the report server in our DMZ unwarranted? If so, I
> must
> be missing something.|||Thanks for the reply. We have considered that - however we didn't want to
have to recreate all of the goodies in the toolbar.
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
in news:#1t7uEQRFHA.2136@.TK2MSFTNGP14.phx.gbl:
> What about building your own interfaace or getting the Report Stream
> from Reporting Webservice to Qrite the Stream to the browser ? There
> you could lock down your reporting server and connect to the RS with
> special lockedup credentials.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>

dependacy files of sql server for deployment setup applicaton

Respected Sir
this thing I knew 2 year later, unfortunately forget and missplace

I want to not depend on sql server 2000 clients , can I include some dll s in my vb6 setup sothat I may not depend on sql server client to install all my clients
I want to add dependancy files of sql server in my deployment setup of application written in vb6 ans sql server
plz help me
Can anybody provide liste of these filesConnectivity to SQL Server should be enabled in baseline installs of Windows XP, Windows 2000, Windows 2003 and may be part of Windows NT SP4 (can't remember and it's been a while).

In Windows XP, 2000 and 2003 you can type cliconfg at a command prompt to get the SQL Server Client Configuration utility; I don't believe that any install of SQL Client tools is required.

You should be able to test/validate connectivity by creating a simple text file, rename it to [something.UDL] and then double clicking on it to start the Universal Data Link wizard. Set the parameters (SQL Server driver, SQL Server name, user name, password and default database) and then click on the Test Connection button.

Regards,

hmscott