supposing your production db is PRODDB (Recovery=FULL), and you have restored the dump to LEGACYDB

you have the problem of getting the lost 80M rows from LEGACYDB into PRODDB without blowing...

a production DBA should understand what TSQL workload is being thrown at the db-engine, for comparisons or trend analysis (call it capacity planning if you wish). what I mean is...

correct as stated [will still keep existing column collations]. or ...

1. script all current tables without explicit collation [and pref in dependency order]

2. install SQL200x to get the instance to...

If you have the SQL configs correct, then it is looking more like a security issue with the credentials you [or middleware] are presenting to AD. perhaps relates to what...

in SQL2005 you can create triggers that fire on DDL or server events (in addition to earlier DML statement activity) see BOL extract as below.

However I suggest you would NOT...

obviously you need to have setup the provider first and with various settings

below script from SSMS on my DEV box - hope it helps you setup your environment

- change the...

sysobjects still exists in SQL2005 as a migration, but is a VIEW

- you can see it in SSMS under system views

not sure if is still [will be] in SQL2008 as...

disconnected pattern relies on optimistic concurrency, but you would have to have a way to detect such conflicts. Fortunately there are several solutions, especially timestamp type

each time a row gets...

guesses

1. data in that row has incompatible datatype [so you need some cast/convert function]

2. index and/or keyset cursor is flawed [metadata needs refreshing]

3. somebody DB2-side trashed the row [transient, depending...

as standard you can call these sprocs

exec sp_helpdb

exec sp_spaceused

and in SSMS (SQL2005-SP2) you can right-click on your db, Reports, StandardReports

- a useful screenshot of numbers but not easy to persist...

in SQL2005 it is possible to configure the pub for DDL changes, so these will flow through with no extra effort

sp_addpublication @replicate_ddl=1

http://msdn2.microsoft.com/en-us/library/ms151870.aspx

- all clever stuff but arguable whether...

basic dogma is that all db's should conform to 3NF and have PK's to reflect content

- could be either natural key (red,blue,green,..) or synthetic (IDENTITY 1,2,3..)

in the absence of natural...

using Merge Replication implies possibility of conflicts and need for resolution strategy

- this has been largely roll-your-own in SQL200x [e.g. with RMO] if basic offering no good

MS is putting lotsa...

suggest you read Books Online (BOL) on the topic - you will get much more sense that such a vague request to this forum !

here is a URL to get...

AFAIK that is not a supported facility.

SQL200x -> SQL200x is fine (OK the compact editions can only be subscribers)

Oracle -> SQL200x is possible (SQL Enterprise Edition ONLY)

where latter creates lotsa...