what version is your SQL instance?

VDI backwards compatibilty has a known issue with VLDB's and SQLVDI errors

what was the attach command you used?

you have ceated a primary zone and not a secondary?

As both name servers are DC's set them to AD integrated too

you stated DC2 is a virtual server, just for clarification what hypervisor are you using to render this VM?

:blush: doh log backup missed that one

our maint jobs dont perform log backups on system db's either. Incidentally Jeff that error is from the SQL log by the looks of...

Jeff

can you post the actual error from the Redgate Backup log file on the server. It defaults to

c:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\instancename

this is only true for MS VS2005, under VMware...

set up column filters for the databasename (containing the object) and Textdata columns.

assuming you were catching a table called "Blobdata" set the filter on textdata to

Like %Blobdata%

install a new instance and migrate the objects then remove the old instance afterwards

once you have updated usages and indexes\stats run the following against the database

dbcc checkdb (mydatabase) with all_errormsgs, no_infomsgs, data_purity

what is the version of your sql instance?

K. Brian Kelley (12/15/2008)

---

This should be taken care of automatically thanks to the Windows Time service. The first DC (assuming it's holding the role of PDC emulator) should be set...

ensure the virtual DC's clock is constantly in sync otherwise it could become orphaned from the domain

just use the update, dont rely on the updates being correct when done in the 2000 database. When moving from SQL2000 to 2005 always update stats and usage.

when you share a folder in windows you have a share tab and a security tab. Share permissions and security permissions are different and need to be configured correctly...