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
>
Showing posts with label across. Show all posts
Showing posts with label across. Show all posts
Monday, March 26, 2012
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
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
>
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
>
Wednesday, March 21, 2012
How can I move a database?
Hi
I am having to move a database from one pc to another and would like to know
the best way to do so making sure that users and logins come across as well.
I am using MSDE 2000 Rel A and am moving it from a Windows 2000 pc to a
Windows XP Prof 2002 SP2 machine.
I have sucessfully installed MSDE on the new pc and can view it through
DBAMgr2k.
I need to know how to create the database and pull across all the
properties.
I tried generating an SQL script for all objects but when I tried to run it
on the XP machine (using DBAMgr2k) I received a "Count field incorrect or
syntax error" message.
Any help would be much appreciated.
Thanks
June
Hello,
Please read the article and go ahead based on the steps defined. This help
you to move all the user databases and system databases to new server.
Since you are moving the system databases you will get the Logins, users,
Jobs,... to the new environment automatically.
http://support.microsoft.com/kb/224071
Thanks
Hari
"June Macleod" <junemacleod@.btconnect.com> wrote in message
news:csKdncKr1KVXoD_YRVnyjQA@.bt.com...
> Hi
> I am having to move a database from one pc to another and would like to
> know
> the best way to do so making sure that users and logins come across as
> well.
> I am using MSDE 2000 Rel A and am moving it from a Windows 2000 pc to a
> Windows XP Prof 2002 SP2 machine.
> I have sucessfully installed MSDE on the new pc and can view it through
> DBAMgr2k.
> I need to know how to create the database and pull across all the
> properties.
> I tried generating an SQL script for all objects but when I tried to run
> it
> on the XP machine (using DBAMgr2k) I received a "Count field incorrect or
> syntax error" message.
> Any help would be much appreciated.
> Thanks
> June
>
|||That worked well.
Many thanks
June
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23g60%23WyMHHA.4992@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Please read the article and go ahead based on the steps defined. This
help[vbcol=seagreen]
> you to move all the user databases and system databases to new server.
> Since you are moving the system databases you will get the Logins, users,
> Jobs,... to the new environment automatically.
> http://support.microsoft.com/kb/224071
> Thanks
> Hari
>
> "June Macleod" <junemacleod@.btconnect.com> wrote in message
> news:csKdncKr1KVXoD_YRVnyjQA@.bt.com...
or
>
I am having to move a database from one pc to another and would like to know
the best way to do so making sure that users and logins come across as well.
I am using MSDE 2000 Rel A and am moving it from a Windows 2000 pc to a
Windows XP Prof 2002 SP2 machine.
I have sucessfully installed MSDE on the new pc and can view it through
DBAMgr2k.
I need to know how to create the database and pull across all the
properties.
I tried generating an SQL script for all objects but when I tried to run it
on the XP machine (using DBAMgr2k) I received a "Count field incorrect or
syntax error" message.
Any help would be much appreciated.
Thanks
June
Hello,
Please read the article and go ahead based on the steps defined. This help
you to move all the user databases and system databases to new server.
Since you are moving the system databases you will get the Logins, users,
Jobs,... to the new environment automatically.
http://support.microsoft.com/kb/224071
Thanks
Hari
"June Macleod" <junemacleod@.btconnect.com> wrote in message
news:csKdncKr1KVXoD_YRVnyjQA@.bt.com...
> Hi
> I am having to move a database from one pc to another and would like to
> know
> the best way to do so making sure that users and logins come across as
> well.
> I am using MSDE 2000 Rel A and am moving it from a Windows 2000 pc to a
> Windows XP Prof 2002 SP2 machine.
> I have sucessfully installed MSDE on the new pc and can view it through
> DBAMgr2k.
> I need to know how to create the database and pull across all the
> properties.
> I tried generating an SQL script for all objects but when I tried to run
> it
> on the XP machine (using DBAMgr2k) I received a "Count field incorrect or
> syntax error" message.
> Any help would be much appreciated.
> Thanks
> June
>
|||That worked well.
Many thanks
June
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23g60%23WyMHHA.4992@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Please read the article and go ahead based on the steps defined. This
help[vbcol=seagreen]
> you to move all the user databases and system databases to new server.
> Since you are moving the system databases you will get the Logins, users,
> Jobs,... to the new environment automatically.
> http://support.microsoft.com/kb/224071
> Thanks
> Hari
>
> "June Macleod" <junemacleod@.btconnect.com> wrote in message
> news:csKdncKr1KVXoD_YRVnyjQA@.bt.com...
or
>
Subscribe to:
Posts (Atom)