Moving symmetric keys between servers

I'm having some issues restoring a backup of database that uses native encryption onto another server. I know there are a couple of articles on this but I seem to be missing something. Any help would be greatly appreciated.

Current Server Windows 2000
Destination Server Windows 2003

The original key setup for the current server was achieved by something like this:

CREATE SYMMETRIC KEY HR01 WITH algorithm=DES encryption BY password = 'HRpassword'

Running the command select * from sys.symmetric_keys on the current server I get the following:

name principal_id symmetric_key_id key_length key_algorithm algorithm_desc create_date modify_date key_guid HR01 1 256 56 D DES 2006-11-22 16:36:01.883 2006-11-22 16:36:01.883 BBD80500-338F-47D7-B336-85D46E00F2F0

So I restored the database onto the new server and ran this script:

OPEN MASTER KEY DECRYPTION BY PASSWORD = 'Password';
ALTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY;
GO

I don't have a master key... so I go back to the original server and ran this script and did another backup:

CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'Password'
OPEN MASTER KEY DECRYPTION BY PASSWORD = 'Password';
ALTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY;

Running select * from sys.symmetric_keys on the current server now looks like this:

name principal_id symmetric_key_id key_length key_algorithm algorithm_desc create_date modify_date key_guid ##MS_DatabaseMasterKey## 1 101 128 D3 TRIPLE_DES 2007-04-23 16:03:09.183 2007-04-23 17:02:46.630 1CB0D800-0173-4A1E-B841-362B454E60AC HR01 1 256 56 D DES 2006-11-22 16:36:01.883 2006-11-22 16:36:01.883 BBD80500-338F-47D7-B336-85D46E00F2F0

I then restored the new backup onto the 2003 server and ran this script:

OPEN MASTER KEY DECRYPTION BY PASSWORD = 'Password';
ALTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY;
GO

The alter script now runs fine but I get the error message: The decryption key is incorrect when trying to open the HR01 key

We have seen other cases of problems using DES on Windows 2000 (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1122121&SiteID=1). Unfortunately the DES (DES only, not TRIPLE_DES) implementation on Win2k is not as robust as on later versions of the OS. We typically recommend against using DES, and we strongly recommend against using DES on Windows 2000 platforms (use TRIPLE_DES instead).

My personal recommendation on this case would be to try to restore the DB temporarily on a Windows 2000 machine, recover the data and re-encrypt it using TRIPLE_DES algorithm.

By the way, because you are using protection by password instead of by a certificate, the DB master key steps should not be needed in your case.

I hope this information helps. Please, let us know if there is anything else we can do to help.

-Raul Garcia

SDE/T

SQL Server Engine

Moving SQL Server

Dear all,
I have two questions
1. What is the best way to move a whole SQL server to another machine with
different machine name?
2. I tried backup all DB including master from one server then restore all
to another server. However, I found all the users in individual database ar
e
invalid but the Logins in SQL Security are ok. Why and how to solve this?
Thanks for any help.
TedmondHi,
1. What you did is exactly the good method..
2. If you restore the Master database followed with all databases then the
Logins will sync with Users in database. Incase if you find any descripancy
then
use the system procedure sp_change_users_login (see books online) to sync
the Logins with database users...
Thanks
Hari
"Tedmond" <Tedmond@.discussions.microsoft.com> wrote in message
news:030841E2-E09B-4F32-B630-AEF5D6B2392C@.microsoft.com...
> Dear all,
> I have two questions
> 1. What is the best way to move a whole SQL server to another machine with
> different machine name?
> 2. I tried backup all DB including master from one server then restore all
> to another server. However, I found all the users in individual database
> are
> invalid but thogins in SQL Security are ok. Why and how to solve this?
> Thanks for any help.
> Tedmond
>|||These articles may help:
Moving Server/Database/Logins
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to a
New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/col...se
s.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://support.microsoft.com/kb/274188 Troubleshooting Orphan Logins
http://www.support.microsoft.com/?id=240872 Resolve Permission
Issues -Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles for
SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scr...utions/1598.asp Script Roles
and Permissions
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Tedmond" <Tedmond@.discussions.microsoft.com> wrote in message
news:030841E2-E09B-4F32-B630-AEF5D6B2392C@.microsoft.com...
> Dear all,
> I have two questions
> 1. What is the best way to move a whole SQL server to another machine with
> different machine name?
> 2. I tried backup all DB including master from one server then restore all
> to another server. However, I found all the users in individual database
> are
> invalid but the Logins in SQL Security are ok. Why and how to solve this?
> Thanks for any help.
> Tedmond
>

Moving SQL Server

Dear all,
I have two questions
1. What is the best way to move a whole SQL server to another machine with
different machine name?
2. I tried backup all DB including master from one server then restore all
to another server. However, I found all the users in individual database are
invalid but the Logins in SQL Security are ok. Why and how to solve this?
Thanks for any help.
Tedmond
Hi,
1. What you did is exactly the good method..
2. If you restore the Master database followed with all databases then the
Logins will sync with Users in database. Incase if you find any descripancy
then
use the system procedure sp_change_users_login (see books online) to sync
the Logins with database users...
Thanks
Hari
"Tedmond" <Tedmond@.discussions.microsoft.com> wrote in message
news:030841E2-E09B-4F32-B630-AEF5D6B2392C@.microsoft.com...
> Dear all,
> I have two questions
> 1. What is the best way to move a whole SQL server to another machine with
> different machine name?
> 2. I tried backup all DB including master from one server then restore all
> to another server. However, I found all the users in individual database
> are
> invalid but thogins in SQL Security are ok. Why and how to solve this?
> Thanks for any help.
> Tedmond
>
|||These articles may help:
Moving Server/Database/Logins
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to a
New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://support.microsoft.com/kb/274188 Troubleshooting Orphan Logins
http://www.support.microsoft.com/?id=240872 Resolve Permission
Issues -Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles for
SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script Roles
and Permissions
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Tedmond" <Tedmond@.discussions.microsoft.com> wrote in message
news:030841E2-E09B-4F32-B630-AEF5D6B2392C@.microsoft.com...
> Dear all,
> I have two questions
> 1. What is the best way to move a whole SQL server to another machine with
> different machine name?
> 2. I tried backup all DB including master from one server then restore all
> to another server. However, I found all the users in individual database
> are
> invalid but the Logins in SQL Security are ok. Why and how to solve this?
> Thanks for any help.
> Tedmond
>

Moving SQL Server

Dear all,
I have two questions
1. What is the best way to move a whole SQL server to another machine with
different machine name?
2. I tried backup all DB including master from one server then restore all
to another server. However, I found all the users in individual database are
invalid but the Logins in SQL Security are ok. Why and how to solve this?
Thanks for any help.
TedmondHi,
1. What you did is exactly the good method..
2. If you restore the Master database followed with all databases then the
Logins will sync with Users in database. Incase if you find any descripancy
then
use the system procedure sp_change_users_login (see books online) to sync
the Logins with database users...
Thanks
Hari
"Tedmond" <Tedmond@.discussions.microsoft.com> wrote in message
news:030841E2-E09B-4F32-B630-AEF5D6B2392C@.microsoft.com...
> Dear all,
> I have two questions
> 1. What is the best way to move a whole SQL server to another machine with
> different machine name?
> 2. I tried backup all DB including master from one server then restore all
> to another server. However, I found all the users in individual database
> are
> invalid but thogins in SQL Security are ok. Why and how to solve this?
> Thanks for any help.
> Tedmond
>|||These articles may help:
Moving Server/Database/Logins
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to a
New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://support.microsoft.com/kb/274188 Troubleshooting Orphan Logins
http://www.support.microsoft.com/?id=240872 Resolve Permission
Issues -Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles for
SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script Roles
and Permissions
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Tedmond" <Tedmond@.discussions.microsoft.com> wrote in message
news:030841E2-E09B-4F32-B630-AEF5D6B2392C@.microsoft.com...
> Dear all,
> I have two questions
> 1. What is the best way to move a whole SQL server to another machine with
> different machine name?
> 2. I tried backup all DB including master from one server then restore all
> to another server. However, I found all the users in individual database
> are
> invalid but the Logins in SQL Security are ok. Why and how to solve this?
> Thanks for any help.
> Tedmond
>

Moving SQL Database to a new server

I am moving a sql database from a Windows 2000 server to a new windows 2003
server. I read where there is 3 ways to do this: ? Backup and Restore
? Sp_detach_db and Sp_attach_db stored procedures
? Import and Export Data (to copy objects and data between SQL Server
databases)
My question is after reading the descriptions on these I still don't know if
I should do a backup and restore or a import and export. There will not be
anyone using the database when I will be working on it. Any suggestions?
Thanks!If it's a small db, just one data file and one log file, just detach and
re-attach. Otherwise,
I'd perform a backup and restore.
Remember to re-apply any database logins, roles, and users
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0FC783C5-0C29-4ED2-996E-3F86F6A47C55@.microsoft.com...
> I am moving a sql database from a Windows 2000 server to a new windows
2003
> server. I read where there is 3 ways to do this: . Backup and Restore
> . Sp_detach_db and Sp_attach_db stored procedures
> . Import and Export Data (to copy objects and data between SQL Server
> databases)
> My question is after reading the descriptions on these I still don't know
if
> I should do a backup and restore or a import and export. There will not
be
> anyone using the database when I will be working on it. Any suggestions?
> Thanks!|||Keep in mind the following:
1. You also have to transfer your logins from the source server to the dest.
server
2. Your jobs
3. Your custom error msg (if any) reside on system database
Sasan Saidi, MSc in CS
Senior DBA
Brascan Business Services
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armando Prato" wrote:

> If it's a small db, just one data file and one log file, just detach and
> re-attach. Otherwise,
> I'd perform a backup and restore.
> Remember to re-apply any database logins, roles, and users
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0FC783C5-0C29-4ED2-996E-3F86F6A47C55@.microsoft.com...
> 2003
> if
> be
>
>

Moving SQL Database to a new server

I am moving a sql database from a windows 2000 server to a new windows 2003
server. I read where there is 3 ways to do this: ? Backup and Restore
? Sp_detach_db and Sp_attach_db stored procedures
? Import and Export Data (to copy objects and data between SQL Server
databases)
My question is after reading the descriptions on these I still don't know if
I should do a backup and restore or a import and export. There will not be
anyone using the database when I will be working on it. Any suggestions?
Thanks!
If it's a small db, just one data file and one log file, just detach and
re-attach. Otherwise,
I'd perform a backup and restore.
Remember to re-apply any database logins, roles, and users
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0FC783C5-0C29-4ED2-996E-3F86F6A47C55@.microsoft.com...
> I am moving a sql database from a windows 2000 server to a new windows
2003
> server. I read where there is 3 ways to do this: . Backup and Restore
> . Sp_detach_db and Sp_attach_db stored procedures
> . Import and Export Data (to copy objects and data between SQL Server
> databases)
> My question is after reading the descriptions on these I still don't know
if
> I should do a backup and restore or a import and export. There will not
be
> anyone using the database when I will be working on it. Any suggestions?
> Thanks!
|||Keep in mind the following:
1. You also have to transfer your logins from the source server to the dest.
server
2. Your jobs
3. Your custom error msg (if any) reside on system database
Sasan Saidi, MSc in CS
Senior DBA
Brascan Business Services
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armando Prato" wrote:

> If it's a small db, just one data file and one log file, just detach and
> re-attach. Otherwise,
> I'd perform a backup and restore.
> Remember to re-apply any database logins, roles, and users
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0FC783C5-0C29-4ED2-996E-3F86F6A47C55@.microsoft.com...
> 2003
> if
> be
>
>

Moving SQL Database to a new server

I am moving a sql database from a windows 2000 server to a new windows 2003
server. I read where there is 3 ways to do this: â?¢ Backup and Restore
â?¢ Sp_detach_db and Sp_attach_db stored procedures
â?¢ Import and Export Data (to copy objects and data between SQL Server
databases)
My question is after reading the descriptions on these I still don't know if
I should do a backup and restore or a import and export. There will not be
anyone using the database when I will be working on it. Any suggestions?
Thanks!If it's a small db, just one data file and one log file, just detach and
re-attach. Otherwise,
I'd perform a backup and restore.
Remember to re-apply any database logins, roles, and users
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0FC783C5-0C29-4ED2-996E-3F86F6A47C55@.microsoft.com...
> I am moving a sql database from a windows 2000 server to a new windows
2003
> server. I read where there is 3 ways to do this: . Backup and Restore
> . Sp_detach_db and Sp_attach_db stored procedures
> . Import and Export Data (to copy objects and data between SQL Server
> databases)
> My question is after reading the descriptions on these I still don't know
if
> I should do a backup and restore or a import and export. There will not
be
> anyone using the database when I will be working on it. Any suggestions?
> Thanks!|||Keep in mind the following:
1. You also have to transfer your logins from the source server to the dest.
server
2. Your jobs
3. Your custom error msg (if any) reside on system database
--
Sasan Saidi, MSc in CS
Senior DBA
Brascan Business Services
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armando Prato" wrote:
> If it's a small db, just one data file and one log file, just detach and
> re-attach. Otherwise,
> I'd perform a backup and restore.
> Remember to re-apply any database logins, roles, and users
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0FC783C5-0C29-4ED2-996E-3F86F6A47C55@.microsoft.com...
> > I am moving a sql database from a windows 2000 server to a new windows
> 2003
> > server. I read where there is 3 ways to do this: . Backup and Restore
> > . Sp_detach_db and Sp_attach_db stored procedures
> > . Import and Export Data (to copy objects and data between SQL Server
> > databases)
> >
> > My question is after reading the descriptions on these I still don't know
> if
> > I should do a backup and restore or a import and export. There will not
> be
> > anyone using the database when I will be working on it. Any suggestions?
> > Thanks!
>
>

Moving SQL 7 DB to different machine SQL2000

have a SQL 7 db with stored procedures and tables and have to move it to another box with SQL2000, what is the cleanest way to do this? backup and restore?

take the complete backup of database, creat a new database on the new system with same name, and select restore database ,select the backup file for restoring. you will have to take care for the paths of the mdf and ldf file (will need to change it manually for the current backup file path). also check the "force restore" check box. I think its the right name for the check box as I don't have sql server on my system now.

your database will be moved fully and in very quick time.

Usman

|||

Thank You for the quick repsonse but i do have some more questions.

1. Will the stored procedures move correctly? especially going from 7 to 2000?

2. Also, when the DB is restored will it upgrade the DB and the stored Procedures

3. Is there an issue with the files being on differnt drives/directories?

|||

2000 should detect that the mdf and ldf belong to older version of MSSQL and will ask if you want to convert to newer version code.

BEAWARE******But there are chances that you might see some change in functionality******

Moving sql 2000 DTS packages to sql 2005 standard edition

I have been tasked with upgrading around 150 SQL Server 2000 DTS packages to SSIS in SQL Server 2005 standard edition. I made a backup of the 2000 database upon which the DTS packages operate and restored it to the SQL 2005 server. So far, so good. I have the database in place. Now I need to get the DTS packages themselves into the SLQ 2005 server. I think I need to check my install and make sure that I have the SQL Server 2000 DTS services installed on the SQL 2005 server. I can do that.

However, I wonder what would be the most effective way to physically get the packages from the SQL 2000 server to the SQL 2005 server. Should I use structured storage files? If so, how do I go about opening them in SQL 2005 in order to save them to SQL server 2005?

I should mention that these packages make heavy use of ActiveX scripting so I am looking at rewriting them from scratch to be SSIS packages. I just need the packages on the SQL Server 2005 box so I can make sure I am creating exactly the same functionality in 2005 as existed in SQL server 2000. Each DTS 2000 individual package tends to be fairly simple and I think I can greatly improve the process by consolidating them.

Thanks in advance for any advice.

S. Wells

You'll need the DTS2000 editor by teh sounds of it. Downloadable from here: http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

-Jamie

|||

Thanks Jamie,

It does appear that this will give me what I need. I had read another, earlier, post on the forum that indicated the legacy components did not have to be separately installed now that 2005 is in production release if one had chosen to install integration services. I did not realize that the designer was not installed as part of the legacy DTS components install. I looked all over the BI interface and could not see where I could open a DTS package and then save it to SQL 2005.

Again, thanks.

S. Wells

|||

Just a quick note to say that there is a new version (an update to the previous link):

Instead of:

Feature Pack for Microsoft SQL Server 2005 - November 2005
http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Download from:

Feature Pack for Microsoft SQL Server 2005 - April 2006
http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&DisplayLang=en

6th item down:

Microsoft SQL Server 2000 DTS Designer Components

The Microsoft SQL Server 2000 Data Transformation Services (DTS) package designer is a design tool used by developers and administrators of SQL Server 2005 servers to edit and maintain existing DTS packages until they can be upgraded or recreated in the SQL Server 2005 Integration Services package format. After installing this download, SQL Server 2005 users can continue to edit and maintain existing DTS packages from the Object Explorer in SQL Server 2005 Management Studio and from the Execute DTS 2000 Package Task Editor in Business Intelligence Development Studio, without needing to reinstall the SQL Server 2000 tools. The DTS package designer in this download was formerly accessed from the Data Transformation Services node in SQL Server 2000 Enterprise Manager.
Audience(s): Customer, Developer
X86 Package (SQLServer2005_DTS.msi) - 5088 KB

Also look at

SQL Server 2005 Books Online

SQL Server 2005 Integration Services Backward Compatibility
Updated: 17 July 2006
http://msdn2.microsoft.com/en-us/library/ms143706.aspx

General Compatibility between DTS and SSIS
Because Integration Services is an entirely new product, and not a version upgrade, you will not encounter software conflicts between DTS and SSIS.

You can install both DTS and SSIS on the same server.
You can run both DTS and SSIS packages on the same server when both products are installed. You can run DTS packages, even when the SQL Server 2000 tools are not present, by using an updated version of the DTS runtime that is installed with Integration Services.
You can save DTS packages in the MSDB database of a SQL Server 2000 or SQL Server 2005 instance. You can save SSIS packages only on a SQL Server 2005 instance.
You can edit DTS packages, even when the SQL Server 2000 tools are not present, by using an updated version of the DTS Designer that is available for download. You cannot edit DTS packages in Business Intelligence Development Studio. You can edit SSIS packages only in BI Development Studio.

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 Replicated Databases to a replacement SQL Server

Any advice that can be offered on this subject would be much appreciated.

We are debating whether to backup/restore the replicated databases or simply copy the mdf and ldf files accross and Attach them. The question is whether the replication information is retained for the publshed objects when the files are copied across? Alernatively, must we use backup/restore with KEEP_REPLICATION set for the restore?

We also plan to back up and restore the distribution, publication, master, msdb etc databases as well as rename the SQL Server to have the same name as the original.

Do these things need to happen in any particular order?

Does the timing of the renaming of the SQL Server matter?

At least some of the these operations (restoring the master database and renaming the SQL Server) need to be done in single user mode. Is is best to restore all the system databases in single user mode?

Lastly, is it necsssary (from a SQL Server point of viewpoint) to rename the computer to have the same name as the SQL Server?

Thanks,

Dick Campbell

You can do either of the options. However there are pros and cons for each of the approaches. I am assuming here that you are doing backup/restore or copy of mdf/ldf of the publisher server (But it applies to the subscriber also).

1. Backup/restore.

You can backup and restore the databases on a different (secondary) server. However you cannot expect that replication will work automatically when your primary server goes down. You will need to resetup replication on ths secondary box.

2. Copy of mdf/ldf.

This can be done too. However the steps you will need to follow are:

a. Copy the files from prmary to a backup location

b. Lets assume your primary now goes down

c. Now you will need to rename the secondary server to the primary server, then install SQL Server and replace the mdf/ldf from on this machine with the ones from the backup location. Replication should then work fine.

My above recommendations defintely apply for Merge replication. They may also apply to Transactonal rpelication but there could be some caveats.

You should defintely try out the scenarios on your test machines.

Moving replicated database to a new machine

Hello.
I'm running SQL Server 2000 (sp3a) and am moving the installation to a new
machine one database at a time (by using Backup/Restore). The new machine
and SQL installation also has a new name that is being kept.
The databases that I've moved thus far are not replicated databases so it's
been easy.
I'm uncertain about this approach when it comes to replicated databases. I
can find no information on Microsoft's site when it comes to moving a
"replicated" database other than a mention of it in one of their KB
articles, and it says something like "Find and read more information about
moving replicated databases", and that's it.
All input is welcome.
Thanks in advance,
Mike
Mike,
are you moving the publisher or subscriber? Is the new box named the same?
Is it in the same domain/trust relationship? Are the service startup
accounts the same? These are all important variables in deciding which way
to do it, or if it is even possible.
Regards,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
"Mike Lopez" <MichaelLopez@.Emmerel.com> wrote in message
news:eAaZ6gJnEHA.3564@.tk2msftngp13.phx.gbl...
> Hello.
> I'm running SQL Server 2000 (sp3a) and am moving the installation to a new
> machine one database at a time (by using Backup/Restore). The new machine
> and SQL installation also has a new name that is being kept.
> The databases that I've moved thus far are not replicated databases so
it's
> been easy.
> I'm uncertain about this approach when it comes to replicated databases. I
> can find no information on Microsoft's site when it comes to moving a
> "replicated" database other than a mention of it in one of their KB
> articles, and it says something like "Find and read more information about
> moving replicated databases", and that's it.
> All input is welcome.
> Thanks in advance,
> Mike
>
|||Hi Paul. Thanks for the response.
I'm moving the publisher. The new box is named differently. Same
domain/trust. Service startup accounts are the same (domain account)..
Furthermore the distributor is a separate machine. That machine acts as both
the distributor and subscriber machine.
In my humble opinion the difference in the machine names are the deal
breaker.
What's your thoughts?
Thanks again,
Mike
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:e5V%23XrJnEHA.2864@.tk2msftngp13.phx.gbl...
> Mike,
> are you moving the publisher or subscriber? Is the new box named the same?
> Is it in the same domain/trust relationship? Are the service startup
> accounts the same? These are all important variables in deciding which way
> to do it, or if it is even possible.
> Regards,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
> "Mike Lopez" <MichaelLopez@.Emmerel.com> wrote in message
> news:eAaZ6gJnEHA.3564@.tk2msftngp13.phx.gbl...
> it's
>
|||Mike,
from experience I agree. Replication enters the servername in several system
tables, which then breaks it if you move the publisher to another,
differently named server. Most people script out the publication, move the
publishing database to the new server, modify the script with the new
servername and logins and recreate the publication on the new server. You
may be able to do a nosync initialization in this case, provided you
synchronize before moving the database and prevent any modifications.
Regards,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi again, Paul.
Yeah, that's pretty much what I was thinking.
I didn't realize that it was possible to do a nosynch initialization. That's
good because two of these databases are huge, and I spent a weekend setting
them up for replication the first time.
Thanks again,
Mike
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%233Sy9ZKnEHA.2764@.TK2MSFTNGP10.phx.gbl...
> Mike,
> from experience I agree. Replication enters the servername in several
> system
> tables, which then breaks it if you move the publisher to another,
> differently named server. Most people script out the publication, move the
> publishing database to the new server, modify the script with the new
> servername and logins and recreate the publication on the new server. You
> may be able to do a nosync initialization in this case, provided you
> synchronize before moving the database and prevent any modifications.
> Regards,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

Moving MSDE SQL Server with OSQL

I am a complete neophyt to SQL. I am attempting to restore a backup from a
MSDE 2000 SQL server from a peer to peer server to a server running Small
Business Server 2003 using OSQL. (In other words I’m moving the database to
a dedicated server.) I performed a RESTORE DATABASE xxx FROM DISK=
‘PATHNAME’ WITH REPLACE
OSQL responded with “RESTORE DATABASE successfully processed xxx pages” Now
I need to run some stored procedures to fix the orphaned user issue, but when
I attempt to login to the database with user “sa” no matter what password I
use I can’t get in. (I’m not sure there is a user “sa” in the restored
database). From what I’ve read, I believe a may need to run the
sp_changedbowner command, but I’m not sure what login I need to change to.
Also, I DID NOT move any "system files" ie master.mdf or model.mdf files. Do
these have to be moved as well? Any suggestions would be greatly
appreciated. Thanks in advance.
Mark G
First, you need to know the new SQL Server (on your Smaill Business
Server2003) has mixed security mode enabled (Only Windows security is
enabled by default installation). If not, you would obviously cannot use
"sa" ( and cannot use any username/password pair in that matter).
To use OSQL.exe tool, you do not have to use "sa" though, you can use -E
swicth with osql.exe to log into SQL Server with trusted connection (Windows
Authentication). Of course you need to log onto your computer as local
admin.
"Mark Grantom" <mgrantom@.swbell.net[no spam]> wrote in message
news:D218EA2E-9D0B-4372-8E22-A58E8FBA1F96@.microsoft.com...
>I am a complete neophyt to SQL. I am attempting to restore a backup from a
> MSDE 2000 SQL server from a peer to peer server to a server running Small
> Business Server 2003 using OSQL. (In other words I'm moving the database
> to
> a dedicated server.) I performed a RESTORE DATABASE xxx FROM DISK=
> 'PATHNAME' WITH REPLACE
> OSQL responded with "RESTORE DATABASE successfully processed xxx pages"
> Now
> I need to run some stored procedures to fix the orphaned user issue, but
> when
> I attempt to login to the database with user "sa" no matter what password
> I
> use I can't get in. (I'm not sure there is a user "sa" in the restored
> database). From what I've read, I believe a may need to run the
> sp_changedbowner command, but I'm not sure what login I need to change to.
> Also, I DID NOT move any "system files" ie master.mdf or model.mdf files.
> Do
> these have to be moved as well? Any suggestions would be greatly
> appreciated. Thanks in advance.
> --
> Mark G
|||hi Mark,
Mark Grantom wrote:
> I am a complete neophyt to SQL. I am attempting to restore a backup
> from a MSDE 2000 SQL server from a peer to peer server to a server
> running Small Business Server 2003 using OSQL. (In other words I'm
> moving the database to a dedicated server.) I performed a RESTORE
> DATABASE xxx FROM DISK= 'PATHNAME' WITH REPLACE
> OSQL responded with "RESTORE DATABASE successfully processed xxx
> pages" Now I need to run some stored procedures to fix the orphaned
> user issue, but when I attempt to login to the database with user
> "sa" no matter what password I use I can't get in. (I'm not sure
> there is a user "sa" in the restored database). From what I've read,
> I believe a may need to run the sp_changedbowner command, but I'm not
> sure what login I need to change to. Also, I DID NOT move any "system
> files" ie master.mdf or model.mdf files. Do these have to be moved
> as well? Any suggestions would be greatly appreciated. Thanks in
> advance.
chances are the problem is related to authentication... MSDE installs by
default only allowing trusted connections and not allowing mixed security
connections relating to SQL Server logins and password credentials.. if
this is the case, you can have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;285097 for further
info about how to "hack" the Windows registry to allow trusted and mixed
security authenticated connections..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||OK, I forgot to say, I did log in with entrusted option to do the initial
RESTORE. I can change to the mixed login option by modifying the registry no
problem. Do I then move the "system files" or not. If so, how? Thanks
Mark G
"Andrea Montanari" wrote:

> hi Mark,
> Mark Grantom wrote:
> chances are the problem is related to authentication... MSDE installs by
> default only allowing trusted connections and not allowing mixed security
> connections relating to SQL Server logins and password credentials.. if
> this is the case, you can have a look at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;285097 for further
> info about how to "hack" the Windows registry to allow trusted and mixed
> security authenticated connections..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> OK, I forgot to say, I did log in with entrusted option to do the
> initial RESTORE. I can change to the mixed login option by modifying
> the registry no problem. Do I then move the "system files" or not.
> If so, how? Thanks
why do you like to "move" system database as well? transferring system
databases between different instances is not a very safe operation.. I'd
not...
you've better "stay" with the new instance ones... you "only" have to
re-create all the "original" desired/required logins and remap them to your
user's databases via that system stored procedure you already mentionned,
so_change_users_login..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||I went back and read my messages twice. I don't "like" to move system
databases. In fact I have NEVER moved a system database. I'm not entirely
certain WHAT a system database is although I do have my suspicions. Remember
I am a rank beginner with SQL. I did ask twice, whether I NEEDED to move
system databases. I take it from your response that the answer is NO? Also,
I checked my system and the "mixed" login mode was already enabled in the
registry. I don't believe that I have a user "sa". How do I create this
user? Thanks.
Mark G
"Andrea Montanari" wrote:

> hi Mark,
> Mark Grantom wrote:
> why do you like to "move" system database as well? transferring system
> databases between different instances is not a very safe operation.. I'd
> not...
> you've better "stay" with the new instance ones... you "only" have to
> re-create all the "original" desired/required logins and remap them to your
> user's databases via that system stored procedure you already mentionned,
> so_change_users_login..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> I went back and read my messages twice. I don't "like" to move system
> databases. In fact I have NEVER moved a system database. I'm not
> entirely certain WHAT a system database is although I do have my
> suspicions. Remember I am a rank beginner with SQL. I did ask
> twice, whether I NEEDED to move system databases. I take it from
> your response that the answer is NO?
you usually do not have to... when you installed the "new" SQL Server/MSDE
instance it installed with it's own system databases... so you are ok with
them..

> Also, I checked my system and
> the "mixed" login mode was already enabled in the registry. I don't
> believe that I have a user "sa". How do I create this user? Thanks.
"sa" login can not be created... it's created at installation time.. and you
have it for sure
what is the exact exception you are reported with when connecting using "sa"
credentials?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||I get:
Login failed for user 'sa'.
Mark G
"Andrea Montanari" wrote:

> hi Mark,
> Mark Grantom wrote:
> you usually do not have to... when you installed the "new" SQL Server/MSDE
> instance it installed with it's own system databases... so you are ok with
> them..
> "sa" login can not be created... it's created at installation time.. and you
> have it for sure
> what is the exact exception you are reported with when connecting using "sa"
> credentials?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> I get:
> Login failed for user 'sa'.
with something else, like "not associated with a trusted connection"?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply

Moving Master, Msdb and Model

I've seen the articles about restoring from backup for
the above. But how do you move these databases to a
different location/drive? Thanks.INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/defaul...b;EN-US;q224071
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"GoMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d94401c4548c$833ffd20$a601280a@.phx
.gbl...
> I've seen the articles about restoring from backup for
> the above. But how do you move these databases to a
> different location/drive? Thanks.|||This article should be helpful:
http://support.microsoft.com/defaul...kb;en-us;224071
Russell Fields
"GoMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d94401c4548c$833ffd20$a601280a@.phx
.gbl...
> I've seen the articles about restoring from backup for
> the above. But how do you move these databases to a
> different location/drive? Thanks.

Moving Master, Msdb and Model

I've seen the articles about restoring from backup for
the above. But how do you move these databases to a
different location/drive? Thanks.
INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/default...;EN-US;q224071
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"GoMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d94401c4548c$833ffd20$a601280a@.phx.gbl...
> I've seen the articles about restoring from backup for
> the above. But how do you move these databases to a
> different location/drive? Thanks.
|||This article should be helpful:
http://support.microsoft.com/default...b;en-us;224071
Russell Fields
"GoMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d94401c4548c$833ffd20$a601280a@.phx.gbl...
> I've seen the articles about restoring from backup for
> the above. But how do you move these databases to a
> different location/drive? Thanks.

Moving Master, Msdb and Model

I've seen the articles about restoring from backup for
the above. But how do you move these databases to a
different location/drive? Thanks.INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q224071
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"GoMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d94401c4548c$833ffd20$a601280a@.phx.gbl...
> I've seen the articles about restoring from backup for
> the above. But how do you move these databases to a
> different location/drive? Thanks.|||This article should be helpful:
http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
Russell Fields
"GoMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d94401c4548c$833ffd20$a601280a@.phx.gbl...
> I've seen the articles about restoring from backup for
> the above. But how do you move these databases to a
> different location/drive? Thanks.