Like others in this posting, we haven't even completed our SQL 2000 upgrades.  It takes time and money, not to mention there was a steeper learning curve with SQL 2005. ...

Are you using WININTERNALS? It writes event log entries that state that exact message.  If possible, disable WININTERNALS and you'll see the entries disappear.  I have our server admin looking into...

As alluded to earlier, a transaction log which is growing, is usually indicative of a lot of transactions, from INSERT/UPDATE/DELETES to DDL statements.  With the growth of the transaction log coupled with...

Yes, you can access SQL Server 2005 Express Edition with the Management Studio from SQL Server 2005 Developer Edition.

Yes, you can install the 32-bit version of SQL Server on a Windows 64-bit OS.  The differences are the 32bit/64bit differences.

What type of replication and publication?  Depending on this you may be able to replicate with SQL 2000 to 2005.  Here's an exerpt from the books on-line.

Subscriber version depends on...

Dont use the 2000 wizard.  What does the query plan show.  Are there a lot of TABLE SCANS, or INDEX SCANS, HASH JOINS (memory intensive), BOOKMARKS?

Double check to make sure...

Other than resorting to the last SQL 2000 backup, as mentioned above, you cannot go back to SQL 2000.

The only other technique is to export the data from SQL 2005...

The previous post is correct.  Here's something else to consider:

Add a ProductCodeSuffix column that contains the "C".

OR

Just return the ProductCode with a "C" concatinated at the end.  You could use a view.

1...

Thanks all.

If you haven't already noticed, you cannot DEBUG script on 64-bit.  It doesn't stop at break-points.  The only lame way I found to debug is to add the old MSGBOX...

As stated in the previous reponse, you cannot restore 2005 db to a 2000 database.  Your only option is to recreate the schema, then export/import the data.

Basically, that's what merge replication does.  When a change is made at subscriber or publisher these changes will be merged so that all data is the same, barring row-filters which...

Have you considered a full install instead of the upgrade?  Create a new SQL 2005 instance, then upgrade the databases individually by restoring, or using DETACH/ATTACH.  Ideally you would want...

Open Server Network Utility

Select TCP/IP

Check "HideServer"