There's no perfect template for how often you should run backups and how often you should test restores. You need to establish a service level agreement with your business about...

By default SQL Server comes with a whole bunch of Policies built in. To try them out, right click on the Policies folder and select Import from the context menu....

Mad-Dog (4/2/2012)

---

Grant Fritchey (4/2/2012)

---

It sounds like you might be dealing with a case of bad parameter sniffing. Instead of freeing the entire proc cache and the buffer cache (which requires...

Microsoft supplies a free tool, the Upgrade Advisor, which will validate that there are no code or structure issues keeping you from upgrading. I'd absolutely run that before starting any...

We can't see your query and we can't see your execution plan. With no knowledge, it's almost impossible to tell you what to do. As Gail said, look for problems...

It sounds like you might be dealing with a case of bad parameter sniffing. Instead of freeing the entire proc cache and the buffer cache (which requires reloading everything), try...

Absolutely run the Upgrade Advisor prior to the upgrade.

I suspect the deprecated code you're thinking of is the old ANSI 89 OUTER JOIN syntax

SELECT *

FROM Table1,Table2

WHERE Table1.ID *= TAble2.ID;

You...

I'm totally with Gail on this, remove the hints as a first step, then look at the execution plan to understand where things are going wrong.

If UserID is coming up NULL, then your problem is here:

set @UserId =(select UserId from aspnet_Users where UserName= @Username)

Not with the other statements.

Take the script you have, turn it into an ad hoc TSQL statement and run it through sp_msforeachdb

No way to know that for sure based on what you provided. It could be almost anything. Look to see if you have errors before this one. Also, if you...

If you're just moving data from a single server to a second server then you need to tune the procedures and processes in place. If you're trying to copy the...

Wrap the whole thing in a transaction first. Then, use the OUTPUT clause to output to a temp table or a table variable (a table variable would probably work well...

Exactly what I was thinking. Even if you could, and assuming you have a key constraint in place, you can't,...

Also, check for blocked processes and collect the wait stats before & during running the procedure to see what's causing stuff to slow down.