Yes, select a valid point in time covered between the last Full backup and last TL backup will do exactly as you stated.

EM is a really nice and simple interface...

Try change EXEC to sp_executeSQL, it will attempt to reuse the execution plan but that is the best you can hope for with a dynamically changing structure. Unless you do...

Unfortunately, there is no finite answer and I have looked at a rough one under various loads.

SHould work fine, can you post what you tried so we can point out maybe a reason why it failed.

It does, but it varies based on condition of processes running and IO to the drive the fiel is saved to. I use the black box trace frequently when try...

I had no issues moving on an unServicePacked server and I don't think you will, but I am pretty sure you will have to reinstall the SP to make sure...

Just playing, how about something like this.

DECLARE @tblname VARCHAR(255)

set @tblname = 'putyourtablenamehere'

DECLARE @colxmlstr VARCHAR(8000)

SET @colxmlstr = 'SELECT ''<fields>

'

SELECT @colxmlstr = @colxmlstr + '<field name = "' + [name] + '...

Same as any write to a HD would have. Just don't send to the same drive as your data or log files if possible. Also, it will print the information...

Restores are all sequentially. You can build a script to run to do the restore and recover on the last restore but you will not be able to do better...

You stated it is the time in seconds. I am thinking most likely seconds since midnight 1/1/1970 (GMT or not? as you will need to adjust to local time).

SQL Server

SELECT...

Not sure but usually that is a sign of not enough memory. The cache hits should be over 90%. All this means is that it was able to find some...

The Buffer Cache thing is a misreport, I forget if this SP with the OS or SQL but I believe it is a known issue.

CPU will always vary but when...

2x18GB System & Application disks RAID 1 -- This would be fine

1x18GB Log -- No redundancy, so you lose it it is gone.

2x36GB Data disks RAID 0+1 -- You can't...

quote:

---

There is a "most popular articles" under the Articles link (under resources).

Steve Jones

sjones@sqlservercentral.com

http://www.sqlservercentral.com/columnists/sjones

---

Sorry missed taht...

Yes cache buffer hit should be above 90% consitantly or you have a memory issue. Other than that, the rest sounds fine. SQL will take memory as it needs and...