Here is some code from my backup process that provides a datetime stamp for my transaction log backup files.

declare @CurrDate datetime;

set @CurrDate = getdate();

select N'_' +

...

Okay, but 9999 is a four digit number....

That comes to this, do you have x years experience or 1 year experience x times over. I have seen both. I believe I am in the former...

I'll do a little digging. Second question, though, could you use a uniquely named global temp table (##Temp01)?

😎

I'll have to do some more research, but I seem to remember reading somewhere that TRY/CATCH in T-SQL doesn't catch all errors. I'll try and find where I saw...

James Raddock (6/5/2008)

---

Disagree. Each product release is finite and static.

I don't say I'm a SQL Server expert, I say I'm an expert at SQL Server 2005. Unless you know everything...

Nope. You have to start all over with the initial restore from your full backup.

😎

The extended stored procedure xp_getfiledetails no longer exists in SQL Server 2005. I just double checked my servers (I have both SQL Server 2000 and SQL Server 2005 still)...

Your code:

RESTORE DATABASE [db1]

FROM DISK = N'J:\SQLBackups\db1_backup_200805310215.bak'

WITH FILE = 1,

MOVE N'Reporting_Data' TO N'e:\Microsoft SQL Server\MSSQL\Data\db1.MDF',

MOVE N'Reporting_Log' TO N'd:\Microsoft SQL Server\MSSQL\Logs\db1_Log.LDF', ...

I got it right. When I read the question, I interpreted it to mean will the the two queries return the same result set. Obviously, some people read...

One thing I will suggest (strongly), test it in a test DB first to ensure it does what you expect.

Sometimes going off topic is refreshing. I've also seen it spark other thoughts and ideas. Sort of like stepping back from the trees so you can see the...

Backup the production database and restore it to your test instance.

😎

Do a search for this undocumented Microsoft stored procedure: sys.sp_MSforeachtable.

😎

Yes. REPLACE tells SQL to overwrite an existing database.

😎