May 15, 2003 at 7:05 am
We are migrating some of our databases from SQL 2K Std Ed. to SQL 2K Ent. Ed. both SP3. The new server is a DL760 running WinAS with 8GB ram. We will be keeping both servers live in a production environment. I have heard that you cannot backup and restore an Ent. Ed. database to Std. Ed. Is this true? If so, what other restrictions are there? Can I create a linked server between version and share some of the data? Will replication work between servers? Any info would be helpful. Any documentation or white papers on this would be great. Thanks!
May 15, 2003 at 7:29 am
quote:
I have heard that you cannot backup and restore an Ent. Ed. database to Std. Ed. Is this true?
Don't think so.
quote:
Can I create a linked server between version and share some of the data? Will replication work between servers?
Sure you can.
What you have to consider are the edition-specific features in EE you may already use in your EE database will not work in STD edition such as index view, Distributed Partitioned views etc. You also loss the Parallel DBCC, Parallel CREATE INDEX, Enhanced Read-Ahead and Scan as well as Log Shipping.
May 15, 2003 at 4:36 pm
There are no issues with backing up/restoring databases between the different editions of SQL Server that I have experienced. We routinely perform exactly that between Developer Edition, Standard Edition and Enterprise Edition.
There ARE issues related to mixing SQL SP levels, particularly SP0 with SP1+ due to the changes in system tables that SP1 brought about. You may or may not run into those issues depending on whether your database was participating in SQL Replication.
If I recall correctly, SP1 automatically updated all the system tables to the new schema required for SP1+ SQL Replication. As of SP2, the system tables were not updated unless you implemented SQL Replication.
Review the changes outlined in the SQL Service Packs for more information.
David R Buckingham, MCDBA,MCSA,MCP
May 16, 2003 at 6:32 am
Thanks for the comments. It helps to know what other people are doing. We got to the point in the project where we did a few restores from Ent. to Std. Ed. and things worked fine. Another migration question if you don't mind. In this project we are splitting the work of one server across two servers. With that in mind, what is the best way to migrate DTS packages and scheduled jobs. Only some of them will be moved to the new box. And server names will change. We have several hundred packages and jobs. What has been your experience?
May 16, 2003 at 7:25 am
See following link for how to transfer DTS packages between servers.
http://www.sqldts.com/default.aspx?6,105,204,0,1
In term of jobs, you can script them from EM and recreate them in your new server.
May 19, 2003 at 8:47 pm
Honestly, we use very few DTS packages. In almost all cases, the ETL operations are either coded in the application layer or in stored procedures.
Another suggestion would be to utilize SQLDMO to help automating the scripting, changing the server name, and recreating them on the new server.
SQLDMO can be used from any COM compliant language, such as Visual Basic, C++, or even Visual FoxPro.
David R Buckingham, MCDBA,MCSA,MCP
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply