Moving Tranaction Logs for existing DBs

Hi,
Just wondering if anyone knows if it's possible to change
locations of a tranaction log of an exisiting database? It
seems whenever I try to detach, move the log and attach it
always looks for the transaction log in the original
location and won't let me specify the new one.
Any help appreciated. Thanks.
-BrianBrian,
While attaching it , mention the new path for the .ldf file explicitly, as
in:
EXEC sp_attach_db @.dbname = N'pubs',
@.filename1 = N'c:\Program Files\Microsoft SQL
Server\MSSQL\Data\pubs.mdf',
@.filename2 = N'c:\Program Files\Microsoft SQL
Server\MSSQL\Data\pubs_log.ldf'
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Brian R." <reaburn.brian@.colteng.com> wrote in message
news:05b201c36017$ab486ab0$a001280a@.phx.gbl...
> Hi,
> Just wondering if anyone knows if it's possible to change
> locations of a tranaction log of an exisiting database? It
> seems whenever I try to detach, move the log and attach it
> always looks for the transaction log in the original
> location and won't let me specify the new one.
> Any help appreciated. Thanks.
> -Brian

Moving to a new server

What is the best practice for moving an existing subscription to a new server?
We have a new sql server that will replace the server where my replicated database lives, so I would like to move the replicated database to the new server & change the publication to point to the new server, is this possible? Seems like it would provide the least amount of interruption....
Hilary, if you cover this in your book, what chapter?
Thanx!
The simplest way is to create a new subscription on the new server and initialize. If all the data is synced up, you could do a nosync initialization to avoid the flow of data.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
|||Good idea! Thanx!
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:uxxecZRtFHA.1168@.TK2MSFTNGP11.phx.gbl...
The simplest way is to create a new subscription on the new server and initialize. If all the data is synced up, you could do a nosync initialization to avoid the flow of data.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)

Moving stored procedures

We are moving an existing database to a new dedicated server. Is there a
way to copy all the user defined stored procedures? If so, what is it.
TIA
Michael
If you are using the backup and restore method to move the databases, the stored procedures are copied right along with the databases. I'm working on an identical project and that works fine for me. You can also use a DTS package with the copy database
feature.
"Michael Beck" wrote:

> We are moving an existing database to a new dedicated server. Is there a
> way to copy all the user defined stored procedures? If so, what is it.
> TIA
> Michael
>
>
|||You could also to sp_detach_db and sp_attach_db... in all 3 cases your
stored procedures will move with the database. They are stored inside the
database in a table called syscomments.,,, so they go automatically.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Michael Beck" <Mikeb46NoSpam@.pacbell.net> wrote in message
news:ewxJ38FZEHA.3228@.TK2MSFTNGP12.phx.gbl...
> We are moving an existing database to a new dedicated server. Is there a
> way to copy all the user defined stored procedures? If so, what is it.
> TIA
> Michael
>

Moving stored procedures

We are moving an existing database to a new dedicated server. Is there a
way to copy all the user defined stored procedures? If so, what is it.
TIA
MichaelIf you are using the backup and restore method to move the databases, the st
ored procedures are copied right along with the databases. I'm working on a
n identical project and that works fine for me. You can also use a DTS pack
age with the copy database
feature.
"Michael Beck" wrote:

> We are moving an existing database to a new dedicated server. Is there a
> way to copy all the user defined stored procedures? If so, what is it.
> TIA
> Michael
>
>|||You could also to sp_detach_db and sp_attach_db... in all 3 cases your
stored procedures will move with the database. They are stored inside the
database in a table called syscomments.,,, so they go automatically.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Michael Beck" <Mikeb46NoSpam@.pacbell.net> wrote in message
news:ewxJ38FZEHA.3228@.TK2MSFTNGP12.phx.gbl...
> We are moving an existing database to a new dedicated server. Is there a
> way to copy all the user defined stored procedures? If so, what is it.
> TIA
> Michael
>

Moving stored procedures

We are moving an existing database to a new dedicated server. Is there a
way to copy all the user defined stored procedures? If so, what is it.
TIA
MichaelYou could also to sp_detach_db and sp_attach_db... in all 3 cases your
stored procedures will move with the database. They are stored inside the
database in a table called syscomments.,,, so they go automatically.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Michael Beck" <Mikeb46NoSpam@.pacbell.net> wrote in message
news:ewxJ38FZEHA.3228@.TK2MSFTNGP12.phx.gbl...
> We are moving an existing database to a new dedicated server. Is there a
> way to copy all the user defined stored procedures? If so, what is it.
> TIA
> Michael
>

Moving SQL Database

I have a question about moving a SQL database to a new server. Right now I
have an existing SQL 2000 database on a server that will be decommissioned
and am putting in a new server to take its palace. My question is how hard is
it to move the data from the existing server to the new one once SQL is
installed. Is it just a matter of backing up and restoring the database? or
exporting and importing? I obviously dont work with SQL but this is something
I will have to do. Any document links or any help would be great!!
Thanks
Chad
Everything you ever wanted to know about moving databases between servers.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default...b;en-us;314546
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chad Guiney" <ChadGuiney@.discussions.microsoft.com> wrote in message
news:B3557EA8-4330-4AE9-B459-E9BA74A43461@.microsoft.com...
>I have a question about moving a SQL database to a new server. Right now I
> have an existing SQL 2000 database on a server that will be decommissioned
> and am putting in a new server to take its palace. My question is how hard
> is
> it to move the data from the existing server to the new one once SQL is
> installed. Is it just a matter of backing up and restoring the database?
> or
> exporting and importing? I obviously dont work with SQL but this is
> something
> I will have to do. Any document links or any help would be great!!
> Thanks
> Chad
|||Chad,
See:
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/default...b;en-us;274463
and
HOW TO: Move Databases Between Computers that are Running SQL Server
http://support.microsoft.com/default...b;en-us;314546
HTH
Jerry
"Chad Guiney" <ChadGuiney@.discussions.microsoft.com> wrote in message
news:B3557EA8-4330-4AE9-B459-E9BA74A43461@.microsoft.com...
>I have a question about moving a SQL database to a new server. Right now I
> have an existing SQL 2000 database on a server that will be decommissioned
> and am putting in a new server to take its palace. My question is how hard
> is
> it to move the data from the existing server to the new one once SQL is
> installed. Is it just a matter of backing up and restoring the database?
> or
> exporting and importing? I obviously dont work with SQL but this is
> something
> I will have to do. Any document links or any help would be great!!
> Thanks
> Chad

Moving SQL Database

I have a question about moving a SQL database to a new server. Right now I
have an existing SQL 2000 database on a server that will be decommissioned
and am putting in a new server to take its palace. My question is how hard is
it to move the data from the existing server to the new one once SQL is
installed. Is it just a matter of backing up and restoring the database? or
exporting and importing? I obviously dont work with SQL but this is something
I will have to do. Any document links or any help would be great!!
Thanks
ChadEverything you ever wanted to know about moving databases between servers.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chad Guiney" <ChadGuiney@.discussions.microsoft.com> wrote in message
news:B3557EA8-4330-4AE9-B459-E9BA74A43461@.microsoft.com...
>I have a question about moving a SQL database to a new server. Right now I
> have an existing SQL 2000 database on a server that will be decommissioned
> and am putting in a new server to take its palace. My question is how hard
> is
> it to move the data from the existing server to the new one once SQL is
> installed. Is it just a matter of backing up and restoring the database?
> or
> exporting and importing? I obviously dont work with SQL but this is
> something
> I will have to do. Any document links or any help would be great!!
> Thanks
> Chad|||Chad,
See:
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;274463
and
HOW TO: Move Databases Between Computers that are Running SQL Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546
HTH
Jerry
"Chad Guiney" <ChadGuiney@.discussions.microsoft.com> wrote in message
news:B3557EA8-4330-4AE9-B459-E9BA74A43461@.microsoft.com...
>I have a question about moving a SQL database to a new server. Right now I
> have an existing SQL 2000 database on a server that will be decommissioned
> and am putting in a new server to take its palace. My question is how hard
> is
> it to move the data from the existing server to the new one once SQL is
> installed. Is it just a matter of backing up and restoring the database?
> or
> exporting and importing? I obviously dont work with SQL but this is
> something
> I will have to do. Any document links or any help would be great!!
> Thanks
> Chad

Moving SQL Database

I have a question about moving a SQL database to a new server. Right now I
have an existing SQL 2000 database on a server that will be decommissioned
and am putting in a new server to take its palace. My question is how hard i
s
it to move the data from the existing server to the new one once SQL is
installed. Is it just a matter of backing up and restoring the database? or
exporting and importing? I obviously dont work with SQL but this is somethin
g
I will have to do. Any document links or any help would be great!!
Thanks
ChadEverything you ever wanted to know about moving databases between servers.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/defaul...kb;en-us;314546
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chad Guiney" <ChadGuiney@.discussions.microsoft.com> wrote in message
news:B3557EA8-4330-4AE9-B459-E9BA74A43461@.microsoft.com...
>I have a question about moving a SQL database to a new server. Right now I
> have an existing SQL 2000 database on a server that will be decommissioned
> and am putting in a new server to take its palace. My question is how hard
> is
> it to move the data from the existing server to the new one once SQL is
> installed. Is it just a matter of backing up and restoring the database?
> or
> exporting and importing? I obviously dont work with SQL but this is
> something
> I will have to do. Any document links or any help would be great!!
> Thanks
> Chad|||Chad,
See:
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/defaul...kb;en-us;274463
and
HOW TO: Move Databases Between Computers that are Running SQL Server
http://support.microsoft.com/defaul...kb;en-us;314546
HTH
Jerry
"Chad Guiney" <ChadGuiney@.discussions.microsoft.com> wrote in message
news:B3557EA8-4330-4AE9-B459-E9BA74A43461@.microsoft.com...
>I have a question about moving a SQL database to a new server. Right now I
> have an existing SQL 2000 database on a server that will be decommissioned
> and am putting in a new server to take its palace. My question is how hard
> is
> it to move the data from the existing server to the new one once SQL is
> installed. Is it just a matter of backing up and restoring the database?
> or
> exporting and importing? I obviously dont work with SQL but this is
> something
> I will have to do. Any document links or any help would be great!!
> Thanks
> Chad

Moving servers

I am planing to build a new sql 2000 serevr on a new
server machine, so that I can upgrade the existing servers
to a new spec and have failover clustering.
I plan to copy all the database to the new server using
the copy wizard, this will copy all the SP etc from the
origal server to the new server, but how can you copy 200+
dts packages to this new server without going into each
package and saving it to the new locationHow about this
Transferring DTS Packages
(http://www.sqldts.com/Default.aspx?204)
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Allan" <penstona@.sitel.co.uk> wrote in message
news:067501c39c73$881c8b50$a101280a@.phx.gbl...
> I am planing to build a new sql 2000 serevr on a new
> server machine, so that I can upgrade the existing servers
> to a new spec and have failover clustering.
> I plan to copy all the database to the new server using
> the copy wizard, this will copy all the SP etc from the
> origal server to the new server, but how can you copy 200+
> dts packages to this new server without going into each
> package and saving it to the new location
>|||Try the DTSBackup tool that is available on SQLDTS.com.
--
Jacco Schalkwijk
SQL Server MVP
"Allan" <penstona@.sitel.co.uk> wrote in message
news:067501c39c73$881c8b50$a101280a@.phx.gbl...
> I am planing to build a new sql 2000 serevr on a new
> server machine, so that I can upgrade the existing servers
> to a new spec and have failover clustering.
> I plan to copy all the database to the new server using
> the copy wizard, this will copy all the SP etc from the
> origal server to the new server, but how can you copy 200+
> dts packages to this new server without going into each
> package and saving it to the new location
>|||SQL Server store DTS packages in MSDB database.
So, if you are going to transfer your DBs from old 2K to a
new 2K Server, you can just make backup/restore operation.
Make sure you transfer MSDB database for the DTS packages.
You also can have a problem with system logins.
Take a look at this article about this issue:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;246133&Product=sql
Regards.
---
All information provided above AS IS.
>--Original Message--
>I am planing to build a new sql 2000 serevr on a new
>server machine, so that I can upgrade the existing
servers
>to a new spec and have failover clustering.
>I plan to copy all the database to the new server using
>the copy wizard, this will copy all the SP etc from the
>origal server to the new server, but how can you copy
200+
>dts packages to this new server without going into each
>package and saving it to the new location
>.
>

Moving RS To A New Web Server Problems

Like several other users I have had problems moving to a new web server:
1) backup existing RS databases on database machine
2) delete existing RS databases on database machine
3) install RS on new Web Server
3a) allow RS to create databases on the original database machine using the
same connection ID
4) delete RS databases from database machine
5) restore original databases to database machine
6) access new web server and;
6a) receive a message that the database is not activated and get pointed to
BOL
6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
7) use the (unclear) BOL documentation to issue the command:
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
8) get back an error message:
Failure To Start Web Server.
NT Service Not Started.
9) kick a small dog and write this note.
thanks in advance for your help.
dlrDid you backup the keys using rskeymgmt.exe'
"Dennis Redfield" wrote:
> Like several other users I have had problems moving to a new web server:
> 1) backup existing RS databases on database machine
> 2) delete existing RS databases on database machine
> 3) install RS on new Web Server
> 3a) allow RS to create databases on the original database machine using the
> same connection ID
> 4) delete RS databases from database machine
> 5) restore original databases to database machine
> 6) access new web server and;
> 6a) receive a message that the database is not activated and get pointed to
> BOL
> 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> 7) use the (unclear) BOL documentation to issue the command:
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> 8) get back an error message:
> Failure To Start Web Server.
> NT Service Not Started.
> 9) kick a small dog and write this note.
>
> thanks in advance for your help.
> dlr
>
>|||yes! and...
dlr
"Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> Did you backup the keys using rskeymgmt.exe'
> "Dennis Redfield" wrote:
> > Like several other users I have had problems moving to a new web server:
> >
> > 1) backup existing RS databases on database machine
> > 2) delete existing RS databases on database machine
> > 3) install RS on new Web Server
> > 3a) allow RS to create databases on the original database machine using
the
> > same connection ID
> > 4) delete RS databases from database machine
> > 5) restore original databases to database machine
> > 6) access new web server and;
> > 6a) receive a message that the database is not activated and get pointed
to
> > BOL
> > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > 7) use the (unclear) BOL documentation to issue the command:
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > 8) get back an error message:
> > Failure To Start Web Server.
> > NT Service Not Started.
> > 9) kick a small dog and write this note.
> >
> >
> > thanks in advance for your help.
> >
> > dlr
> >
> >
> >|||Restore the keys to the new web server. You may need to restart
ReportService and IIS. I had to do the same thing before:
1) Backup the keys
2) install the RS on the new Web Server
3) Restore the keys
4) It worked for me. Did not need to use rsactivate.
"Dennis Redfield" wrote:
> yes! and...
> dlr
> "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
> news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > Did you backup the keys using rskeymgmt.exe'
> >
> > "Dennis Redfield" wrote:
> >
> > > Like several other users I have had problems moving to a new web server:
> > >
> > > 1) backup existing RS databases on database machine
> > > 2) delete existing RS databases on database machine
> > > 3) install RS on new Web Server
> > > 3a) allow RS to create databases on the original database machine using
> the
> > > same connection ID
> > > 4) delete RS databases from database machine
> > > 5) restore original databases to database machine
> > > 6) access new web server and;
> > > 6a) receive a message that the database is not activated and get pointed
> to
> > > BOL
> > > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > > 7) use the (unclear) BOL documentation to issue the command:
> > >
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > 8) get back an error message:
> > > Failure To Start Web Server.
> > > NT Service Not Started.
> > > 9) kick a small dog and write this note.
> > >
> > >
> > > thanks in advance for your help.
> > >
> > > dlr
> > >
> > >
> > >
>
>|||ok. I will try it.
dlr
"Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> Restore the keys to the new web server. You may need to restart
> ReportService and IIS. I had to do the same thing before:
> 1) Backup the keys
> 2) install the RS on the new Web Server
> 3) Restore the keys
> 4) It worked for me. Did not need to use rsactivate.
> "Dennis Redfield" wrote:
> > yes! and...
> > dlr
> > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
> > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > Did you backup the keys using rskeymgmt.exe'
> > >
> > > "Dennis Redfield" wrote:
> > >
> > > > Like several other users I have had problems moving to a new web
server:
> > > >
> > > > 1) backup existing RS databases on database machine
> > > > 2) delete existing RS databases on database machine
> > > > 3) install RS on new Web Server
> > > > 3a) allow RS to create databases on the original database machine
using
> > the
> > > > same connection ID
> > > > 4) delete RS databases from database machine
> > > > 5) restore original databases to database machine
> > > > 6) access new web server and;
> > > > 6a) receive a message that the database is not activated and get
pointed
> > to
> > > > BOL
> > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > > > 7) use the (unclear) BOL documentation to issue the command:
> > > >
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > 8) get back an error message:
> > > > Failure To Start Web Server.
> > > > NT Service Not Started.
> > > > 9) kick a small dog and write this note.
> > > >
> > > >
> > > > thanks in advance for your help.
> > > >
> > > > dlr
> > > >
> > > >
> > > >
> >
> >
> >|||Now This Is Fun.
Restored The Key File.
Exe reports success.
Start Web Browser and Receive Message:
This edition of Reporting Services does not support web farm deployment.
(rsInvalidRSEditionConfiguration) Get Online Help
Get Online Help returns:
You cannot use the Standard edition of Reporting Services to deploy multiple
report servers in a Web farms.
Web Farm! What Web Farm? Argh!
dlr
"Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> Restore the keys to the new web server. You may need to restart
> ReportService and IIS. I had to do the same thing before:
> 1) Backup the keys
> 2) install the RS on the new Web Server
> 3) Restore the keys
> 4) It worked for me. Did not need to use rsactivate.
> "Dennis Redfield" wrote:
> > yes! and...
> > dlr
> > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
> > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > Did you backup the keys using rskeymgmt.exe'
> > >
> > > "Dennis Redfield" wrote:
> > >
> > > > Like several other users I have had problems moving to a new web
server:
> > > >
> > > > 1) backup existing RS databases on database machine
> > > > 2) delete existing RS databases on database machine
> > > > 3) install RS on new Web Server
> > > > 3a) allow RS to create databases on the original database machine
using
> > the
> > > > same connection ID
> > > > 4) delete RS databases from database machine
> > > > 5) restore original databases to database machine
> > > > 6) access new web server and;
> > > > 6a) receive a message that the database is not activated and get
pointed
> > to
> > > > BOL
> > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > > > 7) use the (unclear) BOL documentation to issue the command:
> > > >
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > 8) get back an error message:
> > > > Failure To Start Web Server.
> > > > NT Service Not Started.
> > > > 9) kick a small dog and write this note.
> > > >
> > > >
> > > > thanks in advance for your help.
> > > >
> > > > dlr
> > > >
> > > >
> > > >
> >
> >
> >|||I will do the following to solve this problem (if possible)
- Remove Reporting Services Completely from the Web server machine.
- Reboot the computer
- Install SQL standard on the Web services machine (this is temp. only)
- Install reporting services and select the local SQL server
- It should work fine with no reports defined
- use rsconfig.exe to point to the rs database server
- use rskeysmgmt to restore the keys
- restart ReportService service and IIS
- If every thing works fine, you can remove SQL Server from the web server box
Hope this will help
"Dennis Redfield" wrote:
> Now This Is Fun.
> Restored The Key File.
> Exe reports success.
> Start Web Browser and Receive Message:
> This edition of Reporting Services does not support web farm deployment.
> (rsInvalidRSEditionConfiguration) Get Online Help
> Get Online Help returns:
> You cannot use the Standard edition of Reporting Services to deploy multiple
> report servers in a Web farms.
>
> Web Farm! What Web Farm? Argh!
> dlr
>
> "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > Restore the keys to the new web server. You may need to restart
> > ReportService and IIS. I had to do the same thing before:
> >
> > 1) Backup the keys
> > 2) install the RS on the new Web Server
> > 3) Restore the keys
> > 4) It worked for me. Did not need to use rsactivate.
> >
> > "Dennis Redfield" wrote:
> >
> > > yes! and...
> > > dlr
> > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
> > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > Did you backup the keys using rskeymgmt.exe'
> > > >
> > > > "Dennis Redfield" wrote:
> > > >
> > > > > Like several other users I have had problems moving to a new web
> server:
> > > > >
> > > > > 1) backup existing RS databases on database machine
> > > > > 2) delete existing RS databases on database machine
> > > > > 3) install RS on new Web Server
> > > > > 3a) allow RS to create databases on the original database machine
> using
> > > the
> > > > > same connection ID
> > > > > 4) delete RS databases from database machine
> > > > > 5) restore original databases to database machine
> > > > > 6) access new web server and;
> > > > > 6a) receive a message that the database is not activated and get
> pointed
> > > to
> > > > > BOL
> > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > >
> > >
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > 8) get back an error message:
> > > > > Failure To Start Web Server.
> > > > > NT Service Not Started.
> > > > > 9) kick a small dog and write this note.
> > > > >
> > > > >
> > > > > thanks in advance for your help.
> > > > >
> > > > > dlr
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||same results!
sad really.
I will open a support call on this monday.
dlr
"Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> I will do the following to solve this problem (if possible)
> - Remove Reporting Services Completely from the Web server machine.
> - Reboot the computer
> - Install SQL standard on the Web services machine (this is temp. only)
> - Install reporting services and select the local SQL server
> - It should work fine with no reports defined
> - use rsconfig.exe to point to the rs database server
> - use rskeysmgmt to restore the keys
> - restart ReportService service and IIS
> - If every thing works fine, you can remove SQL Server from the web server
box
> Hope this will help
> "Dennis Redfield" wrote:
> > Now This Is Fun.
> > Restored The Key File.
> > Exe reports success.
> >
> > Start Web Browser and Receive Message:
> > This edition of Reporting Services does not support web farm deployment.
> > (rsInvalidRSEditionConfiguration) Get Online Help
> >
> > Get Online Help returns:
> > You cannot use the Standard edition of Reporting Services to deploy
multiple
> > report servers in a Web farms.
> >
> >
> > Web Farm! What Web Farm? Argh!
> >
> > dlr
> >
> >
> > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > Restore the keys to the new web server. You may need to restart
> > > ReportService and IIS. I had to do the same thing before:
> > >
> > > 1) Backup the keys
> > > 2) install the RS on the new Web Server
> > > 3) Restore the keys
> > > 4) It worked for me. Did not need to use rsactivate.
> > >
> > > "Dennis Redfield" wrote:
> > >
> > > > yes! and...
> > > > dlr
> > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
message
> > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > Did you backup the keys using rskeymgmt.exe'
> > > > >
> > > > > "Dennis Redfield" wrote:
> > > > >
> > > > > > Like several other users I have had problems moving to a new web
> > server:
> > > > > >
> > > > > > 1) backup existing RS databases on database machine
> > > > > > 2) delete existing RS databases on database machine
> > > > > > 3) install RS on new Web Server
> > > > > > 3a) allow RS to create databases on the original database
machine
> > using
> > > > the
> > > > > > same connection ID
> > > > > > 4) delete RS databases from database machine
> > > > > > 5) restore original databases to database machine
> > > > > > 6) access new web server and;
> > > > > > 6a) receive a message that the database is not activated and get
> > pointed
> > > > to
> > > > > > BOL
> > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
<834304>
> > > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > > >
> > > >
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > 8) get back an error message:
> > > > > > Failure To Start Web Server.
> > > > > > NT Service Not Started.
> > > > > > 9) kick a small dog and write this note.
> > > > > >
> > > > > >
> > > > > > thanks in advance for your help.
> > > > > >
> > > > > > dlr
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||This may be because of the edition of RS (Standard) as per below MSDN
link..Please check!
Sushil
"Dennis Redfield" wrote:
> same results!
> sad really.
> I will open a support call on this monday.
> dlr
> "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> > I will do the following to solve this problem (if possible)
> >
> > - Remove Reporting Services Completely from the Web server machine.
> > - Reboot the computer
> > - Install SQL standard on the Web services machine (this is temp. only)
> > - Install reporting services and select the local SQL server
> > - It should work fine with no reports defined
> > - use rsconfig.exe to point to the rs database server
> > - use rskeysmgmt to restore the keys
> > - restart ReportService service and IIS
> > - If every thing works fine, you can remove SQL Server from the web server
> box
> >
> > Hope this will help
> >
> > "Dennis Redfield" wrote:
> >
> > > Now This Is Fun.
> > > Restored The Key File.
> > > Exe reports success.
> > >
> > > Start Web Browser and Receive Message:
> > > This edition of Reporting Services does not support web farm deployment.
> > > (rsInvalidRSEditionConfiguration) Get Online Help
> > >
> > > Get Online Help returns:
> > > You cannot use the Standard edition of Reporting Services to deploy
> multiple
> > > report servers in a Web farms.
> > >
> > >
> > > Web Farm! What Web Farm? Argh!
> > >
> > > dlr
> > >
> > >
> > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > > Restore the keys to the new web server. You may need to restart
> > > > ReportService and IIS. I had to do the same thing before:
> > > >
> > > > 1) Backup the keys
> > > > 2) install the RS on the new Web Server
> > > > 3) Restore the keys
> > > > 4) It worked for me. Did not need to use rsactivate.
> > > >
> > > > "Dennis Redfield" wrote:
> > > >
> > > > > yes! and...
> > > > > dlr
> > > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
> message
> > > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > > Did you backup the keys using rskeymgmt.exe'
> > > > > >
> > > > > > "Dennis Redfield" wrote:
> > > > > >
> > > > > > > Like several other users I have had problems moving to a new web
> > > server:
> > > > > > >
> > > > > > > 1) backup existing RS databases on database machine
> > > > > > > 2) delete existing RS databases on database machine
> > > > > > > 3) install RS on new Web Server
> > > > > > > 3a) allow RS to create databases on the original database
> machine
> > > using
> > > > > the
> > > > > > > same connection ID
> > > > > > > 4) delete RS databases from database machine
> > > > > > > 5) restore original databases to database machine
> > > > > > > 6) access new web server and;
> > > > > > > 6a) receive a message that the database is not activated and get
> > > pointed
> > > > > to
> > > > > > > BOL
> > > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
> <834304>
> > > > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > > > >
> > > > >
> > >
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > > 8) get back an error message:
> > > > > > > Failure To Start Web Server.
> > > > > > > NT Service Not Started.
> > > > > > > 9) kick a small dog and write this note.
> > > > > > >
> > > > > > >
> > > > > > > thanks in advance for your help.
> > > > > > >
> > > > > > > dlr
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Sorry! forgot to add link ..
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSerrors/htm/Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings_rsInvalidRSEditionConfiguration.asp
"Dennis Redfield" wrote:
> same results!
> sad really.
> I will open a support call on this monday.
> dlr
> "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> > I will do the following to solve this problem (if possible)
> >
> > - Remove Reporting Services Completely from the Web server machine.
> > - Reboot the computer
> > - Install SQL standard on the Web services machine (this is temp. only)
> > - Install reporting services and select the local SQL server
> > - It should work fine with no reports defined
> > - use rsconfig.exe to point to the rs database server
> > - use rskeysmgmt to restore the keys
> > - restart ReportService service and IIS
> > - If every thing works fine, you can remove SQL Server from the web server
> box
> >
> > Hope this will help
> >
> > "Dennis Redfield" wrote:
> >
> > > Now This Is Fun.
> > > Restored The Key File.
> > > Exe reports success.
> > >
> > > Start Web Browser and Receive Message:
> > > This edition of Reporting Services does not support web farm deployment.
> > > (rsInvalidRSEditionConfiguration) Get Online Help
> > >
> > > Get Online Help returns:
> > > You cannot use the Standard edition of Reporting Services to deploy
> multiple
> > > report servers in a Web farms.
> > >
> > >
> > > Web Farm! What Web Farm? Argh!
> > >
> > > dlr
> > >
> > >
> > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > > Restore the keys to the new web server. You may need to restart
> > > > ReportService and IIS. I had to do the same thing before:
> > > >
> > > > 1) Backup the keys
> > > > 2) install the RS on the new Web Server
> > > > 3) Restore the keys
> > > > 4) It worked for me. Did not need to use rsactivate.
> > > >
> > > > "Dennis Redfield" wrote:
> > > >
> > > > > yes! and...
> > > > > dlr
> > > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
> message
> > > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > > Did you backup the keys using rskeymgmt.exe'
> > > > > >
> > > > > > "Dennis Redfield" wrote:
> > > > > >
> > > > > > > Like several other users I have had problems moving to a new web
> > > server:
> > > > > > >
> > > > > > > 1) backup existing RS databases on database machine
> > > > > > > 2) delete existing RS databases on database machine
> > > > > > > 3) install RS on new Web Server
> > > > > > > 3a) allow RS to create databases on the original database
> machine
> > > using
> > > > > the
> > > > > > > same connection ID
> > > > > > > 4) delete RS databases from database machine
> > > > > > > 5) restore original databases to database machine
> > > > > > > 6) access new web server and;
> > > > > > > 6a) receive a message that the database is not activated and get
> > > pointed
> > > > > to
> > > > > > > BOL
> > > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
> <834304>
> > > > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > > > >
> > > > >
> > >
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > > 8) get back an error message:
> > > > > > > Failure To Start Web Server.
> > > > > > > NT Service Not Started.
> > > > > > > 9) kick a small dog and write this note.
> > > > > > >
> > > > > > >
> > > > > > > thanks in advance for your help.
> > > > > > >
> > > > > > > dlr
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||indeed. that is the error page I AM GETTING NOW. What Web Farm?
I testing a realistic disaster recovery plan.
I started with a Web Server and a database server.
I simulate a database
crash and move backups of the existing database to a new machine and
Microsoft tells me I need a lic for a web farm!
Is this reasonable? In a pig's eye, perhaps.
thanks for playing.
dlr
"sushild" <sushild@.discussions.microsoft.com> wrote in message
news:91510B97-526F-4CCE-9638-880A73899022@.microsoft.com...
> Sorry! forgot to add link ..
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSerrors/htm/Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings_rsInvalidRSEditionConfiguration.asp
> "Dennis Redfield" wrote:
> > same results!
> > sad really.
> > I will open a support call on this monday.
> > dlr
> > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> > > I will do the following to solve this problem (if possible)
> > >
> > > - Remove Reporting Services Completely from the Web server machine.
> > > - Reboot the computer
> > > - Install SQL standard on the Web services machine (this is temp.
only)
> > > - Install reporting services and select the local SQL server
> > > - It should work fine with no reports defined
> > > - use rsconfig.exe to point to the rs database server
> > > - use rskeysmgmt to restore the keys
> > > - restart ReportService service and IIS
> > > - If every thing works fine, you can remove SQL Server from the web
server
> > box
> > >
> > > Hope this will help
> > >
> > > "Dennis Redfield" wrote:
> > >
> > > > Now This Is Fun.
> > > > Restored The Key File.
> > > > Exe reports success.
> > > >
> > > > Start Web Browser and Receive Message:
> > > > This edition of Reporting Services does not support web farm
deployment.
> > > > (rsInvalidRSEditionConfiguration) Get Online Help
> > > >
> > > > Get Online Help returns:
> > > > You cannot use the Standard edition of Reporting Services to deploy
> > multiple
> > > > report servers in a Web farms.
> > > >
> > > >
> > > > Web Farm! What Web Farm? Argh!
> > > >
> > > > dlr
> > > >
> > > >
> > > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in
message
> > > > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > > > Restore the keys to the new web server. You may need to restart
> > > > > ReportService and IIS. I had to do the same thing before:
> > > > >
> > > > > 1) Backup the keys
> > > > > 2) install the RS on the new Web Server
> > > > > 3) Restore the keys
> > > > > 4) It worked for me. Did not need to use rsactivate.
> > > > >
> > > > > "Dennis Redfield" wrote:
> > > > >
> > > > > > yes! and...
> > > > > > dlr
> > > > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
> > message
> > > > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > > > Did you backup the keys using rskeymgmt.exe'
> > > > > > >
> > > > > > > "Dennis Redfield" wrote:
> > > > > > >
> > > > > > > > Like several other users I have had problems moving to a new
web
> > > > server:
> > > > > > > >
> > > > > > > > 1) backup existing RS databases on database machine
> > > > > > > > 2) delete existing RS databases on database machine
> > > > > > > > 3) install RS on new Web Server
> > > > > > > > 3a) allow RS to create databases on the original database
> > machine
> > > > using
> > > > > > the
> > > > > > > > same connection ID
> > > > > > > > 4) delete RS databases from database machine
> > > > > > > > 5) restore original databases to database machine
> > > > > > > > 6) access new web server and;
> > > > > > > > 6a) receive a message that the database is not activated and
get
> > > > pointed
> > > > > > to
> > > > > > > > BOL
> > > > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
> > <834304>
> > > > > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > > > > >
> > > > > >
> > > >
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > > > 8) get back an error message:
> > > > > > > > Failure To Start Web Server.
> > > > > > > > NT Service Not Started.
> > > > > > > > 9) kick a small dog and write this note.
> > > > > > > >
> > > > > > > >
> > > > > > > > thanks in advance for your help.
> > > > > > > >
> > > > > > > > dlr
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||opps. actually simulate a web server crash (not a database crash) and move
web server to a new machine.
Microsoft tells me I need a lic for a web farm!
Is this reasonable? In a pig's eye, perhaps.
dlr
"Dennis Redfield" <dennis.redfield@.acadia-ins.com> wrote in message
news:uN6TkiBwEHA.2120@.TK2MSFTNGP14.phx.gbl...
> indeed. that is the error page I AM GETTING NOW. What Web Farm?
> I testing a realistic disaster recovery plan.
> I started with a Web Server and a database server.
> I simulate a database
> crash and move backups of the existing database to a new machine and
> Microsoft tells me I need a lic for a web farm!
> Is this reasonable? In a pig's eye, perhaps.
> thanks for playing.
> dlr
>
> "sushild" <sushild@.discussions.microsoft.com> wrote in message
> news:91510B97-526F-4CCE-9638-880A73899022@.microsoft.com...
> > Sorry! forgot to add link ..
> >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSerrors/htm/Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings_rsInvalidRSEditionConfiguration.asp
> >
> > "Dennis Redfield" wrote:
> >
> > > same results!
> > > sad really.
> > > I will open a support call on this monday.
> > > dlr
> > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > > news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> > > > I will do the following to solve this problem (if possible)
> > > >
> > > > - Remove Reporting Services Completely from the Web server machine.
> > > > - Reboot the computer
> > > > - Install SQL standard on the Web services machine (this is temp.
> only)
> > > > - Install reporting services and select the local SQL server
> > > > - It should work fine with no reports defined
> > > > - use rsconfig.exe to point to the rs database server
> > > > - use rskeysmgmt to restore the keys
> > > > - restart ReportService service and IIS
> > > > - If every thing works fine, you can remove SQL Server from the web
> server
> > > box
> > > >
> > > > Hope this will help
> > > >
> > > > "Dennis Redfield" wrote:
> > > >
> > > > > Now This Is Fun.
> > > > > Restored The Key File.
> > > > > Exe reports success.
> > > > >
> > > > > Start Web Browser and Receive Message:
> > > > > This edition of Reporting Services does not support web farm
> deployment.
> > > > > (rsInvalidRSEditionConfiguration) Get Online Help
> > > > >
> > > > > Get Online Help returns:
> > > > > You cannot use the Standard edition of Reporting Services to
deploy
> > > multiple
> > > > > report servers in a Web farms.
> > > > >
> > > > >
> > > > > Web Farm! What Web Farm? Argh!
> > > > >
> > > > > dlr
> > > > >
> > > > >
> > > > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in
> message
> > > > > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > > > > Restore the keys to the new web server. You may need to restart
> > > > > > ReportService and IIS. I had to do the same thing before:
> > > > > >
> > > > > > 1) Backup the keys
> > > > > > 2) install the RS on the new Web Server
> > > > > > 3) Restore the keys
> > > > > > 4) It worked for me. Did not need to use rsactivate.
> > > > > >
> > > > > > "Dennis Redfield" wrote:
> > > > > >
> > > > > > > yes! and...
> > > > > > > dlr
> > > > > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
> > > message
> > > > > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > > > > Did you backup the keys using rskeymgmt.exe'
> > > > > > > >
> > > > > > > > "Dennis Redfield" wrote:
> > > > > > > >
> > > > > > > > > Like several other users I have had problems moving to a
new
> web
> > > > > server:
> > > > > > > > >
> > > > > > > > > 1) backup existing RS databases on database machine
> > > > > > > > > 2) delete existing RS databases on database machine
> > > > > > > > > 3) install RS on new Web Server
> > > > > > > > > 3a) allow RS to create databases on the original database
> > > machine
> > > > > using
> > > > > > > the
> > > > > > > > > same connection ID
> > > > > > > > > 4) delete RS databases from database machine
> > > > > > > > > 5) restore original databases to database machine
> > > > > > > > > 6) access new web server and;
> > > > > > > > > 6a) receive a message that the database is not activated
and
> get
> > > > > pointed
> > > > > > > to
> > > > > > > > > BOL
> > > > > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
> > > <834304>
> > > > > > > > > 7) use the (unclear) BOL documentation to issue the
command:
> > > > > > > > >
> > > > > > >
> > > > >
> > >
>
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > > > > 8) get back an error message:
> > > > > > > > > Failure To Start Web Server.
> > > > > > > > > NT Service Not Started.
> > > > > > > > > 9) kick a small dog and write this note.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > thanks in advance for your help.
> > > > > > > > >
> > > > > > > > > dlr
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>

Moving ReportServer and ReportServerTempDB to a different drive.

I need to move these databases from the C to the E driver on the existing server. I found instructions on how to move to a different server but I could not find specific instructions on moving these databases on what I need to dor. Has anyone been successfully in moving these databases to a different drive? If so, I would be grateful in you sharing your knowledge.

Thanks.

While these databases contain metadata for SSRS, they are not particularly special otherwise, just detach/re-attach them as you would any other database :)

If you're unclear on how to attach/detach, take a look at the sp_attach_db and sp_detach_db sprocs in books online (FYI, SSRS will need to be shut down while you do this or you won't be able to detach in the first place since it will have open connections)

Hope this helps!

|||I am familiar with the attach and detach stored procedures, so I will try this out on one of our virtual servers. Thanks a lot.

Moving my SQL 7.0 databases to a new server to replace the old server

My existing SQL server is an old box that can no longer cope with the load. I need to replace it with a brand new box.

I am looking for a comprehensive set of steps that I could follow to ensure that the transition to the new server goes well.

I'm looking to transfer all my user databases but I'm not so sure whether I have to backup and restore my system databases to the new server as well.

I want to name the new server the same as the old server since I will be taking the old server out of production but I'm not sure whether I should rename the server AFTER I move over all the database and how that would affect SQL. Or should I first rename the old server, remove it out of the domain, then name my new server with the same name as my old server, and then proceed with the SQL installation and the moving of the databases.

Also, I do have a maintenance plan, DTS packages and some jobs set up on my old server that I would also like to move to the new server.

Is there a web page that explains all the steps in granular detail ?

SQL Server 2005 Books Online actually has pretty good info on this. I just did a search on "upgrade 7.0" and it provided a good roadmap.

Paul

Moving my SQL 7.0 databases to a new server to replace the old server

My existing SQL server is an old box that can no longer cope with the load. I need to replace it with a brand new box.

I am looking for a comprehensive set of steps that I could follow to ensure that the transition to the new server goes well.

I'm looking to transfer all my user databases but I'm not so sure whether I have to backup and restore my system databases to the new server as well.

I want to name the new server the same as the old server since I will be taking the old server out of production but I'm not sure whether I should rename the server AFTER I move over all the database and how that would affect SQL. Or should I first rename the old server, remove it out of the domain, then name my new server with the same name as my old server, and then proceed with the SQL installation and the moving of the databases.

Also, I do have a maintenance plan, DTS packages and some jobs set up on my old server that I would also like to move to the new server.

Is there a web page that explains all the steps in granular detail ?

SQL Server 2005 Books Online actually has pretty good info on this. I just did a search on "upgrade 7.0" and it provided a good roadmap.

Paul

Moving Log Shipping Monitor

Is it possible to move the log shipping monitor to a different server
without having to re-create the log pairs? hardware on our existing log
shipping monitor server is failing and we need to bring it down,
hopefully for good. We have another server to be used as the monitoring
server and I'm trying to find the best scenario for this change.
Also, is it possible to have more than one log shipping monitor? I'm
thinking of adding some redundency in the event of a server crash.
Thanks,
DannyTry the below steps to change the Monitor Server
1. Script the "Log Shipping Alert - Backup" and "Log Shipping Alert -
Restore" jobs from the current monitor server
2. Run the following query on current monitor server and save the output -
select maintenance_plan_id from msdb.dbo.log_shipping_primaries
select secondary_plan_id from msdb.dbo.log_shipping_secondaries
3. Execute the scripts created in Step 1 on the new monitor server
4. Execute the following stored proc on the new monitor server -
sp_add_log_shipping_primary
@.primary_server_name = '<primary server name>' ,
@.primary_database_name = '<primary database name>'
,@.maintenance_plan_id = '<maintenance Plan ID from first select command
in Step 2>'
,@.backup_threshold = <backup threshold - should be at least 3 times the
freq of
backup job the value is in minutes>
,@.threshold_alert = '14420'
,@.threshold_alert_enabled = 1
,@.planned_outage_start_time = 0
,@.planned_outage_end_time = 0
,@.planned_outage_weekday_mask = 0
5. Execute the following select statement to get the Primary_ID -
select primary_id from msdb.dbo.log_shipping_primaries where
primary_server_name = '<primary server name>' and primary_database_name =
'<primary database name>'
6. Execute the following stored procedure on the new monitor server -
sp_add_log_shipping_secondary @.primary_id = <primary id retrieved in Step 5>
, @.secondary_server_name = '<Secondary Server name>'
, @.secondary_database_name = '<secondary database name>'
, @.secondary_plan_id = '<Comes from second select statement in Step 2>'
, @.copy_enabled = 1
, @.load_enabled = 1
, @.out_of_sync_threshold = <out-of-sync threshold should be at least 3
times
the freq of copy/restore jobs the value is in minutes>
, @.threshold_alert = '14421'
, @.threshold_alert_enabled = 1
, @.planned_outage_start_time = 0
, @.planned_outage_end_time = 0
, @.planned_outage_weekday_mask = 0
7. Execute the following statement on the Primary and secondary servers to
get the current monitor login information. Verify that the customer has 1
for logon type before proceeding with step 8. If they do not have this
field set to 1, tell them
that for the time being we will change the authentication mode to NT and
then we can change this later on once the monitor is completely migrated -
select * from msdb.dbo.log_shipping_monitor
go
8. Execute the following command on both Primary and all secondary servers
to change the monitor information -
delete from msdb.dbo.log_shipping_monitor
go
sp_define_log_shipping_monitor '<New monitor server name>', 1, NULL, 1
go
9. This should complete the migration. Test that the monitor server icon
appears under Management tree (Enterprise Manager). When you click this Log
Shipping Monitor, there should be the new pair that you just added. Once
the jobs are working successfully the last copied/loaded file field will be
updated to
reflect the changes.
Hope this helps
Vishal Gandhi

Moving Log Shipping Monitor

Is it possible to move the log shipping monitor to a different server
without having to re-create the log pairs? Hardware on our existing log
shipping monitor server is failing and we need to bring it down,
hopefully for good. We have another server to be used as the monitoring
server and I'm trying to find the best scenario for this change.
Also, is it possible to have more than one log shipping monitor? I'm
thinking of adding some redundency in the event of a server crash.
Thanks,
DannyTry the below steps to change the Monitor Server
1. Script the "Log Shipping Alert - Backup" and "Log Shipping Alert -
Restore" jobs from the current monitor server
2. Run the following query on current monitor server and save the output -
select maintenance_plan_id from msdb.dbo.log_shipping_primaries
select secondary_plan_id from msdb.dbo.log_shipping_secondaries
3. Execute the scripts created in Step 1 on the new monitor server
4. Execute the following stored proc on the new monitor server -
sp_add_log_shipping_primary
@.primary_server_name = '<primary server name>' ,
@.primary_database_name = '<primary database name>'
,@.maintenance_plan_id = '<maintenance Plan ID from first select command
in Step 2>'
,@.backup_threshold = <backup threshold - should be at least 3 times the
freq of
backup job the value is in minutes>
,@.threshold_alert = '14420'
,@.threshold_alert_enabled = 1
,@.planned_outage_start_time = 0
,@.planned_outage_end_time = 0
,@.planned_outage_weekday_mask = 0
5. Execute the following select statement to get the Primary_ID -
select primary_id from msdb.dbo.log_shipping_primaries where
primary_server_name = '<primary server name>' and primary_database_name ='<primary database name>'
6. Execute the following stored procedure on the new monitor server -
sp_add_log_shipping_secondary @.primary_id = <primary id retrieved in Step 5>
, @.secondary_server_name = '<Secondary Server name>'
, @.secondary_database_name = '<secondary database name>'
, @.secondary_plan_id = '<Comes from second select statement in Step 2>'
, @.copy_enabled = 1
, @.load_enabled = 1
, @.out_of_sync_threshold = <out-of-sync threshold should be at least 3
times
the freq of copy/restore jobs the value is in minutes>
, @.threshold_alert = '14421'
, @.threshold_alert_enabled = 1
, @.planned_outage_start_time = 0
, @.planned_outage_end_time = 0
, @.planned_outage_weekday_mask = 0
7. Execute the following statement on the Primary and secondary servers to
get the current monitor login information. Verify that the customer has 1
for logon type before proceeding with step 8. If they do not have this
field set to 1, tell them
that for the time being we will change the authentication mode to NT and
then we can change this later on once the monitor is completely migrated -
select * from msdb.dbo.log_shipping_monitor
go
8. Execute the following command on both Primary and all secondary servers
to change the monitor information -
delete from msdb.dbo.log_shipping_monitor
go
sp_define_log_shipping_monitor '<New monitor server name>', 1, NULL, 1
go
9. This should complete the migration. Test that the monitor server icon
appears under Management tree (Enterprise Manager). When you click this Log
Shipping Monitor, there should be the new pair that you just added. Once
the jobs are working successfully the last copied/loaded file field will be
updated to
reflect the changes.
Hope this helps
Vishal Gandhi