sorry to fall back in so late ... meeting time

Joining is just a question of good old maths ... sets and subsets.

so, you have full and log-backups up til monday, right ?

You have full or bulk-logged recovery model ?

If you take a new log-backup (incremental), you can restore the full with...

did you enter the fully qualified name in EM ?

'MyW2k3SQL2KServer.theotherdomain.theotherdomainsuffix' ?

add a country-code column to your tables and create a partitioned view.

This way sqlserver may serve you best if you want to avoid dynamic sql.

check BOL

With dynamic sql you might...

have the frist step of your fullbackup doing this :

EXEC MSDB.DBO.sp_update_job @job_name = N'MyserverLog_Incremental', @new_name = N'FullbackupProcedure_Disabled - MyserverLog_Incremental', @enabled = 0

and add a last step doing :

EXEC MSDB.DBO.sp_update_job...

Take a look at Intervention system for runaway jobs 

it needs to be updated for sql2ksp3. But it might get you on track.

- compare execution plans !

How is this one doing  ? (don't like it myself but give it a try  &nbsp

That's what you get when your interviewer only has his/her mandatory-questions-list but without a clue what it's all about

"Is it possible that the insert trigger is firing prior to the commit tran? "

Yes !

the trigger is launched at command-time ( insert...

- backup your transactionlog !

Do you have a fullbackup taken before this incident, to which the logbackup can be applied ?

If yes, restore the fullbackup with another dbname using the...

make sure each db has at least one .mdf _and_ one .ldf file !

Also keep your backups !

As lholman mentioned, if sqlserver did...

in the backup-folder you'll mostly find .bak-files. These contain regular sqlserver backup-files. (these are to be user with the "restore database"-commandser)

The ones with .mdf, .ndf or .ldf are sqlserver data-...

If you have recent backups, restore will be possible with "restore db" (as long as you stay with the same version or with a higher version of sqlserver).

run DBCC CHECKDB ! see BOL 

Oops. Overlooked the select

back to profiler then