insert into dest_tablename (col1,....coln) as

select col1.....coln from source_tablename

**** column name(1....n) from source must be matching with columnname(1.....n) destination.

i dont think there would be any major difference in moving the database to 2008 or 2008R2, so same strategy is appicable.

Post upgrade, need to make sure that stats are...

ok, so you saying that you restoring the backup on blank database and you not able to restore it?

Instead of restoring on newly created database, why not restore it with...

have you checked the edition? I was referring to same edition. You will get such error in backup restore even though you have same version but idfferent edition

yes, if the job you going to take for money and not for charity.

The very first question to consultant...whats the offer and benefit they giving?

1) backup set holds the backup of other database.

this error is because of version confliction or product confliction. What I mean is, if backup was taken in 2008 ent....

Hi Gail,

One interesting thing to bring in your notice....

After starting the sql in single user mode and connecting instance using sqlcmd and then running dbcc checkdb, the error no...

have you updated the stats post upgrade?

Also generating execution plan can give you more option.

As well running query with 'set statistics IO on' will give you information on...

i think instead of this, you need to script out all user and run the script on 2005.

Follow this link for generating script for login transfer:-

http://support.microsoft.com/kb/246133

ok, thanks Gail. Will give a try if that is the only option left here.

i see....

I tried to play with it...have configured vbs as CPU utilisation as 1% but not getting any alert....

so i am thinking of 2 reason:-

1)server not constantly more than 2%....

try sql hints like with nolock or maxdop... if it can help

I might be wrong,

but want to know that how the alert is connecting your job or knowing the threshold limit of cpu usage which you mentioned in vbs.

if can be, then exclude those objects in your trace.

have you considered robocopy? It have the additional switch which ignore the existing file and copy onle new copies.