All of the backups, other than the last transaction log backup must be restored WITH NORECOVERY. Once any backup has been restored WITH RECOVERY, no more backups can be applied...

It might be a concern, it might not. Without the query, that's about all that can be said.

Provided its from the same version of SQL, it can be restored. See the above link for details on how.

angie stein (7/17/2008)

---

Actually, CAN I do a shrinkfile in a mirrored environment? I was told by our contractor that you should never truncate the logs since you don't know...

Table spool/lazy spool is a temp storage of a interim resultset so that the query processor doesn't have to regenerate the resultset. Often found with sorts, aggregations in subquery, linked...

michael vessey (7/17/2008)

---

In these instances rather than issueing a backup log with truncateonly command we sheduled an hourly CHECKPOINT (for that database)

added benefit of this is that you can run...

Or you can use the newer DMVs

SELECT count(*) from sys.dm_exec_connections

You can also get the IP address fron the same dmv

SELECT login_name, HOST_NAME, client_net_address

FROM sys.dm_exec_connections c INNER JOIN sys.dm_exec_sessions s...

It is possible to restore MSDB, but the process is not the same as for one of the user databases.

See - http://msdn.microsoft.com/en-us/library/ms190749.aspx

xp_cmdshell with the appropriate proxy account created.

Look up proxy aaccounts in books online. You don't have to be admin to execute xp_cmdshell

If you're using stored procedures, consider the EXECUTE...

Mike, as GSquared suggested on another thread, perhaps you should consider getting a competant SQL consultant in to help you with the myriad of performance problems that you seem to...

Perhaps you would like to post the query, the table structure and the indexes?

For now, it looks like the plan that the optimiser picked (the coverign index with a scan)...

It's a red flag. It means that a sort or hash couldn't fit into memory and was forced to disk. Either you;re doing massive hashes and/or sorts, or you're low...

I would recommend changing that. On 64 bit with lots of memory, SQL's more than capable of using...

Just converting them to stored procs, probably not.

To fix deadlocks, you need to identify the cause of that deadlock and fix that. It's probably bad code, bad indexes or...

Looking at that, my first pass suggestion for indexs (without any testing done) would be:

ParentTable

- Clustered index on the primary key.

- Possible nonclustered index on Col2, Col3 (if they...