re-install Windows, how to restore databases?

I have SQL Server 2000 running on Windows 2000 Professional, and need
to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
databases used for client development work. After upgrading Windows,
and re-installing SQL Server, how can I reconnect all of the existing
databases without too much work? I'd rather not have to backup, add,
and restore each one individually.How about scripting it. Write some TSQL using a cursor to loop sysdatabases and backup each
databases using dynamic SQL. Then use a similar way to restore based on the files in that directory.
For the restore part, you can use some of the code I have at:
http://www.karaszi.com/SQLServer/util_restore_all_in_file.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<rgurganus@.citidc.com> wrote in message
news:1124991326.785503.210230@.f14g2000cwb.googlegroups.com...
>I have SQL Server 2000 running on Windows 2000 Professional, and need
> to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
> databases used for client development work. After upgrading Windows,
> and re-installing SQL Server, how can I reconnect all of the existing
> databases without too much work? I'd rather not have to backup, add,
> and restore each one individually.
>|||Hi,
You can detach the databases and Copy both Data and log files.
After reinstalling win2000 you can attach it back
regards,
--
Herbert
"rgurganus@.citidc.com" wrote:
> I have SQL Server 2000 running on Windows 2000 Professional, and need
> to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
> databases used for client development work. After upgrading Windows,
> and re-installing SQL Server, how can I reconnect all of the existing
> databases without too much work? I'd rather not have to backup, add,
> and restore each one individually.
>|||Yes, but with 64+ different databases, I was hoping to avoid detatching
each one, and re-attaching each one. I'm coming out of a MySQL
background, where this would be a piece of cake. You'd just copy the
whole data directory where all the database files are, and restart the
service. Oh well...|||Did you read my post?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<rgurganus@.citidc.com> wrote in message news:1125068039.740731.98460@.g49g2000cwa.googlegroups.com...
> Yes, but with 64+ different databases, I was hoping to avoid detatching
> each one, and re-attaching each one. I'm coming out of a MySQL
> background, where this would be a piece of cake. You'd just copy the
> whole data directory where all the database files are, and restart the
> service. Oh well...
>|||Yes, thanks. That may help. I'm just giving into dislike and bashing
of MS SQL in general. Systems should make things easier, not more
difficult. :(

re-install Windows, how to restore databases?

I have SQL Server 2000 running on Windows 2000 Professional, and need
to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
databases used for client development work. After upgrading Windows,
and re-installing SQL Server, how can I reconnect all of the existing
databases without too much work? I'd rather not have to backup, add,
and restore each one individually.
How about scripting it. Write some TSQL using a cursor to loop sysdatabases and backup each
databases using dynamic SQL. Then use a similar way to restore based on the files in that directory.
For the restore part, you can use some of the code I have at:
http://www.karaszi.com/SQLServer/uti...ll_in_file.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<rgurganus@.citidc.com> wrote in message
news:1124991326.785503.210230@.f14g2000cwb.googlegr oups.com...
>I have SQL Server 2000 running on Windows 2000 Professional, and need
> to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
> databases used for client development work. After upgrading Windows,
> and re-installing SQL Server, how can I reconnect all of the existing
> databases without too much work? I'd rather not have to backup, add,
> and restore each one individually.
>
|||Hi,
You can detach the databases and Copy both Data and log files.
After reinstalling win2000 you can attach it back
regards,
Herbert
"rgurganus@.citidc.com" wrote:

> I have SQL Server 2000 running on Windows 2000 Professional, and need
> to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
> databases used for client development work. After upgrading Windows,
> and re-installing SQL Server, how can I reconnect all of the existing
> databases without too much work? I'd rather not have to backup, add,
> and restore each one individually.
>
|||Yes, but with 64+ different databases, I was hoping to avoid detatching
each one, and re-attaching each one. I'm coming out of a MySQL
background, where this would be a piece of cake. You'd just copy the
whole data directory where all the database files are, and restart the
service. Oh well...
|||Did you read my post?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<rgurganus@.citidc.com> wrote in message news:1125068039.740731.98460@.g49g2000cwa.googlegro ups.com...
> Yes, but with 64+ different databases, I was hoping to avoid detatching
> each one, and re-attaching each one. I'm coming out of a MySQL
> background, where this would be a piece of cake. You'd just copy the
> whole data directory where all the database files are, and restart the
> service. Oh well...
>
|||Yes, thanks. That may help. I'm just giving into dislike and bashing
of MS SQL in general. Systems should make things easier, not more
difficult.

re-install Windows, how to restore databases?

I have SQL Server 2000 running on Windows 2000 Professional, and need
to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
databases used for client development work. After upgrading Windows,
and re-installing SQL Server, how can I reconnect all of the existing
databases without too much work? I'd rather not have to backup, add,
and restore each one individually.How about scripting it. Write some TSQL using a cursor to loop sysdatabases
and backup each
databases using dynamic SQL. Then use a similar way to restore based on the
files in that directory.
For the restore part, you can use some of the code I have at:
http://www.karaszi.com/SQLServer/ut...all_in_file.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<rgurganus@.citidc.com> wrote in message
news:1124991326.785503.210230@.f14g2000cwb.googlegroups.com...
>I have SQL Server 2000 running on Windows 2000 Professional, and need
> to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
> databases used for client development work. After upgrading Windows,
> and re-installing SQL Server, how can I reconnect all of the existing
> databases without too much work? I'd rather not have to backup, add,
> and restore each one individually.
>|||Hi,
You can detach the databases and Copy both Data and log files.
After reinstalling win2000 you can attach it back
regards,
--
Herbert
"rgurganus@.citidc.com" wrote:

> I have SQL Server 2000 running on Windows 2000 Professional, and need
> to upgrade this to Windows 2000 Server. In SQL, I have 64 separate
> databases used for client development work. After upgrading Windows,
> and re-installing SQL Server, how can I reconnect all of the existing
> databases without too much work? I'd rather not have to backup, add,
> and restore each one individually.
>|||Yes, but with 64+ different databases, I was hoping to avoid detatching
each one, and re-attaching each one. I'm coming out of a MySQL
background, where this would be a piece of cake. You'd just copy the
whole data directory where all the database files are, and restart the
service. Oh well...|||Did you read my post?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<rgurganus@.citidc.com> wrote in message news:1125068039.740731.98460@.g49g2000cwa.googlegroup
s.com...
> Yes, but with 64+ different databases, I was hoping to avoid detatching
> each one, and re-attaching each one. I'm coming out of a MySQL
> background, where this would be a piece of cake. You'd just copy the
> whole data directory where all the database files are, and restart the
> service. Oh well...
>|||Yes, thanks. That may help. I'm just giving into dislike and bashing
of MS SQL in general. Systems should make things easier, not more
difficult.

reinstall of the subscriber server

We are using SQL 2K std with s4 and are using Push subscription method.
We need to upgrade some hardware in the subscriber server which will require
us to do a total reinstall of the OS and SQL server software. Since we are
using push subscription, most of the replication settings are on the
publishing server. When we do the server upgrade, I will stop the
distribution agent so it won't do any transfer until the server is up. I
like to know if I back up the subscriber database and restore it on the same
upgraded server. Will the replication work like as usual? Are there any
steps I need to consider?
wingman
As long as the server name, database name, and IP address are identical this
will work.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@.microsoft.com...
> We are using SQL 2K std with s4 and are using Push subscription method.
> We need to upgrade some hardware in the subscriber server which will
> require
> us to do a total reinstall of the OS and SQL server software. Since we
> are
> using push subscription, most of the replication settings are on the
> publishing server. When we do the server upgrade, I will stop the
> distribution agent so it won't do any transfer until the server is up. I
> like to know if I back up the subscriber database and restore it on the
> same
> upgraded server. Will the replication work like as usual? Are there any
> steps I need to consider?
> wingman
|||As long as the distribution agent was stopped and you restore the database
ensuring that you keep replication settings, then you should be able to
simply resume the distribution agent and it will catch up. In the event
that it fails for some reason, you will have to reinitialize it.
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@.microsoft.com...
> We are using SQL 2K std with s4 and are using Push subscription method.
> We need to upgrade some hardware in the subscriber server which will
> require
> us to do a total reinstall of the OS and SQL server software. Since we
> are
> using push subscription, most of the replication settings are on the
> publishing server. When we do the server upgrade, I will stop the
> distribution agent so it won't do any transfer until the server is up. I
> like to know if I back up the subscriber database and restore it on the
> same
> upgraded server. Will the replication work like as usual? Are there any
> steps I need to consider?
> wingman
|||Z,
Thanks for the suggestion. I need some clarification of your statement
"ensuring that you keep replication settiings". Since we are using the
'Push' subscription, as far as I know, all replication settings are in the
publishing computer. Are there other settings in the subscriber server that
I should know about? Also, if I restore the subscriber database from the
backup, should the settings (if any) be restored as well?
wingman
"Z" wrote:

> As long as the distribution agent was stopped and you restore the database
> ensuring that you keep replication settings, then you should be able to
> simply resume the distribution agent and it will catch up. In the event
> that it fails for some reason, you will have to reinitialize it.
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@.microsoft.com...
>
>
|||Thanks.
One quick follow-up question. I understand the idea of the purpose of the
log reader agent and I don't need to shut it down for what I am planning to
do. I noticed that if I want to delete a subscriber database, I need to shut
the log reader agent down because the log reader agent is running a command
"rplcmds' and is connected to the subscriber database. First of all, is my
finding correct? Secondly, can you explain what this command does?
wingman
"Hilary Cotter" wrote:

> As long as the server name, database name, and IP address are identical this
> will work.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@.microsoft.com...
>
>
|||You don't need to shut down the log reader to delete the subscription
database, rather you need to shut down the distribution agent. The log
reader is connected to the publication database and the distribution
database. I am unfamiliar with the rplcmds command.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:1F21FF5C-083A-43CB-9EA6-59EC9A103AA2@.microsoft.com...[vbcol=seagreen]
> Thanks.
> One quick follow-up question. I understand the idea of the purpose of the
> log reader agent and I don't need to shut it down for what I am planning
> to
> do. I noticed that if I want to delete a subscriber database, I need to
> shut
> the log reader agent down because the log reader agent is running a
> command
> "rplcmds' and is connected to the subscriber database. First of all, is
> my
> finding correct? Secondly, can you explain what this command does?
> wingman
> "Hilary Cotter" wrote: