Change the Autogrowth setting from % to MB value makes sense, but I am worried with the 50 MB value, it is too low for Large Databases.

It would be...

What's more painful in understanding is your create table or insert scripts do not work and its reaaly difficult to do that all manually from my side and then...

In these 2 records, your desired ouptut needs only

" 6035BD,101422296,99,5/8/2009,360.75,150,8/10/2009,CRJ,173.16,1,,,0,150,8/27/2008,3FUP"

What is the basis for this record to be identified. I see only few column values are differing at both...

First, What is the reason to replace the Master DB on the Prod2 Server, is there any specific reason?

And it is obviously display the server name of the Prod1 since...

Agree with that Gail, checking that DB was properly detached .

And also making sure the entire set of the Files are Available in case of multiple Data and Log Files,...

Where is the distributor configured, on the local distributor or remote distributor?

Using Attach Database.

Hi,

The approach you have mentioned (to import data into SQL Server and then compare) is a right approach.

regarding your question about how to compare both the tables and then update...

Let's Assume this, Now you have Instance#1 and in that both DB#1 and DB#2 coexist and are fine as of now.

And as mentioned by you, one of the DB's (DB#2)...

Yeah, Filegroups will all be back when you restore from a full backup.

Since your DB is 330 Gb and I get the reason for the additional Filegroups, the backup plan you have is good to work with.

Just for more details, what do...

I hope you know that you cant recover the Database to a Point In Time with Simple Recovery and if that's what you are intending then the Backup Schedule is...

You mentioned all the design is the right way, just to get an Idea, have you also used Database Partitioning? and what about the Number of Data Files and Filegroups?

Is...

What is your goal to achieve here, do you want to have the Identity Values on the subscribers to be different and...

If you are planning to migrate into 2008 directly, then you are inviting disaster.

Let me explain, your application has been running on SQL Server 2000, but your post does...