How Can I Prevent any activity on a SQL Server

I'm getting close to migrating my db's across to a new server and wonder
what is the best way to prevent users from accessing any of the db's on the
sql server?
I have a very LARGE dts package to run that will do all the work for me but
it will be running on the destination server and not sure how I can prevent
anyone other than telling them not to attach to it.
One thought was to start the server in single instance mode but I'm
unfamiliar with how it works. I could reorg the dts to run on the source
server if the single instance will do the trick.

Thanks
Paul Bergson
How about putting the source DB in read only mode?
"Paul Bergson" <pbergson_nospam@.allete.com> wrote in message
news:%236$6oNoUFHA.2436@.TK2MSFTNGP10.phx.gbl...
> I'm getting close to migrating my db's across to a new server and wonder
> what is the best way to prevent users from accessing any of the db's on
> the
> sql server?
> I have a very LARGE dts package to run that will do all the work for me
> but
> it will be running on the destination server and not sure how I can
> prevent
> anyone other than telling them not to attach to it.
> One thought was to start the server in single instance mode but I'm
> unfamiliar with how it works. I could reorg the dts to run on the source
> server if the single instance will do the trick.
>
> --
> Thanks
> Paul Bergson
>
|||If you only have a few, you could do:
ALTER DATABASE dbName SET SINGLE_USER WITH ROLLBACK IMMEDIATE
Then hope your DTS package jumps in before anyone else does.
The downside is you will not be able connect directly to the database to
monitor anything... you will have to rely on the DTS package.
Another idea perhaps is to rename the database? Other applications that
expect it to be there will break, but if you have told the users the db
would be down/inaccessible, that's probably acceptable.
This is my signature. It is a general reminder.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Paul Bergson" <pbergson_nospam@.allete.com> wrote in message
news:%236$6oNoUFHA.2436@.TK2MSFTNGP10.phx.gbl...
> I'm getting close to migrating my db's across to a new server and wonder
> what is the best way to prevent users from accessing any of the db's on
> the
> sql server?
> I have a very LARGE dts package to run that will do all the work for me
> but
> it will be running on the destination server and not sure how I can
> prevent
> anyone other than telling them not to attach to it.
> One thought was to start the server in single instance mode but I'm
> unfamiliar with how it works. I could reorg the dts to run on the source
> server if the single instance will do the trick.
>
> --
> Thanks
> Paul Bergson
>

How Can I Prevent any activity on a SQL Server

I'm getting close to migrating my db's across to a new server and wonder
what is the best way to prevent users from accessing any of the db's on the
sql server?
I have a very LARGE dts package to run that will do all the work for me but
it will be running on the destination server and not sure how I can prevent
anyone other than telling them not to attach to it.
One thought was to start the server in single instance mode but I'm
unfamiliar with how it works. I could reorg the dts to run on the source
server if the single instance will do the trick.
Thanks
Paul BergsonHow about putting the source DB in read only mode?
"Paul Bergson" <pbergson_nospam@.allete.com> wrote in message
news:%236$6oNoUFHA.2436@.TK2MSFTNGP10.phx.gbl...
> I'm getting close to migrating my db's across to a new server and wonder
> what is the best way to prevent users from accessing any of the db's on
> the
> sql server?
> I have a very LARGE dts package to run that will do all the work for me
> but
> it will be running on the destination server and not sure how I can
> prevent
> anyone other than telling them not to attach to it.
> One thought was to start the server in single instance mode but I'm
> unfamiliar with how it works. I could reorg the dts to run on the source
> server if the single instance will do the trick.
>
> --
> Thanks
> Paul Bergson
>|||If you only have a few, you could do:
ALTER DATABASE dbName SET SINGLE_USER WITH ROLLBACK IMMEDIATE
Then hope your DTS package jumps in before anyone else does.
The downside is you will not be able connect directly to the database to
monitor anything... you will have to rely on the DTS package.
Another idea perhaps is to rename the database? Other applications that
expect it to be there will break, but if you have told the users the db
would be down/inaccessible, that's probably acceptable.
This is my signature. It is a general reminder.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Paul Bergson" <pbergson_nospam@.allete.com> wrote in message
news:%236$6oNoUFHA.2436@.TK2MSFTNGP10.phx.gbl...
> I'm getting close to migrating my db's across to a new server and wonder
> what is the best way to prevent users from accessing any of the db's on
> the
> sql server?
> I have a very LARGE dts package to run that will do all the work for me
> but
> it will be running on the destination server and not sure how I can
> prevent
> anyone other than telling them not to attach to it.
> One thought was to start the server in single instance mode but I'm
> unfamiliar with how it works. I could reorg the dts to run on the source
> server if the single instance will do the trick.
>
> --
> Thanks
> Paul Bergson
>sql

How Can I Prevent any activity on a SQL Server

I'm getting close to migrating my db's across to a new server and wonder
what is the best way to prevent users from accessing any of the db's on the
sql server?
I have a very LARGE dts package to run that will do all the work for me but
it will be running on the destination server and not sure how I can prevent
anyone other than telling them not to attach to it.
One thought was to start the server in single instance mode but I'm
unfamiliar with how it works. I could reorg the dts to run on the source
server if the single instance will do the trick.
--
Thanks
Paul BergsonHow about putting the source DB in read only mode?
"Paul Bergson" <pbergson_nospam@.allete.com> wrote in message
news:%236$6oNoUFHA.2436@.TK2MSFTNGP10.phx.gbl...
> I'm getting close to migrating my db's across to a new server and wonder
> what is the best way to prevent users from accessing any of the db's on
> the
> sql server?
> I have a very LARGE dts package to run that will do all the work for me
> but
> it will be running on the destination server and not sure how I can
> prevent
> anyone other than telling them not to attach to it.
> One thought was to start the server in single instance mode but I'm
> unfamiliar with how it works. I could reorg the dts to run on the source
> server if the single instance will do the trick.
>
> --
> Thanks
> Paul Bergson
>|||If you only have a few, you could do:
ALTER DATABASE dbName SET SINGLE_USER WITH ROLLBACK IMMEDIATE
Then hope your DTS package jumps in before anyone else does.
The downside is you will not be able connect directly to the database to
monitor anything... you will have to rely on the DTS package.
Another idea perhaps is to rename the database? Other applications that
expect it to be there will break, but if you have told the users the db
would be down/inaccessible, that's probably acceptable.
--
This is my signature. It is a general reminder.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Paul Bergson" <pbergson_nospam@.allete.com> wrote in message
news:%236$6oNoUFHA.2436@.TK2MSFTNGP10.phx.gbl...
> I'm getting close to migrating my db's across to a new server and wonder
> what is the best way to prevent users from accessing any of the db's on
> the
> sql server?
> I have a very LARGE dts package to run that will do all the work for me
> but
> it will be running on the destination server and not sure how I can
> prevent
> anyone other than telling them not to attach to it.
> One thought was to start the server in single instance mode but I'm
> unfamiliar with how it works. I could reorg the dts to run on the source
> server if the single instance will do the trick.
>
> --
> Thanks
> Paul Bergson
>

How can I launch a report without generating it automatically?

I am accessing a report in IE by typing the following link in the address field:

http://localhost/ReportServer/Pages/ReportViewer.aspx?/Reports/TheNameOfMyReport

When the page is loaded, the report is generated automatically because all report parameters have default values.

How can I modify my report so that it is not automatically generated? I would like to wait until the user clicks on "View Report" before rendering the report.

As a temporary solution, I removed the default value of one report parameter but I would like to get it to work even if I leave all default values in.

I have seen sites where they describe a list of extra parameters you can include in the url to modify the behavior of the report like:

&rs:Command=Render

&rs:Format=Excel

&rc:NoHeader=true ...

but I haven't seen anything to tell the reporting engine not to render a report.

Any help would be appreciated, thx.

Is this not possible. I am also looking forward to a way to do the same?|||This appears to be only possible with your workaround above or by using the Reportviewer control in Visual Studio.