If it's LiteSpeed, you have to use LiteSpeed to restore it. You can use the utility to uncompress it and then restore it.

Also, if it wasn't LiteSpeed, you can try...

By the way, all these examples are for local variables, not parameters. There is a distinct difference. Unless the statement is recompiled, the values within variables will not be "sniffed"...

SQLKnowItAll (4/2/2012)

---

Lynn Pettis (4/2/2012)

---

Grant Fritchey (4/2/2012)

---

Lynn Pettis (4/2/2012)

---

In SQL Server 2008 and...

Lynn Pettis (4/2/2012)

---

In SQL Server 2008 and newer when running Enterprise Edition,...

To check when the last time statistics were updated, use the STATS_DATE function.

The rules for when auto update fires are a bit more complicated. They're listed here.

If you add...

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