I'm not a fan of intellisense, when it works, it doesn't do enough.

That said, instead of sp_who2, take a look at sys.dm_exec_requests and see if you see an active connection...

I don't know that I'd say there is a "best" strategy. However, there is one fundamental truth. Your backups are only good if you can restore them. So you run...

That's a good idea to know exactly how long it was there. To just get an idea of how long it's been there at a moment in time, take a...

When you create temporary tables, you get a recompile. When you add a row to temporary tables, you get a recompile because of the stats updates. Then, statistics can get...

Another person just recently had an issue where someone posted millions of rows and was doing sorts on unindexed columns while they did so, smacked tempdb good and hard. It's...

Steve Jones - SSC Editor (5/25/2011)

---

Is that for sure?...

WHOOP!

I'll be there.

My initial take, based on the column name, was that you have clustered GUIDs, which are absolutely prone to fragmentation, but based on what you're telling us so far, it's...

river1 (5/25/2011)

---

SELECT Liquidacao.CODLIQ, Liquidacao.NUMLIQ, Liquidacao.LANCLIQ, Liquidacao.DATALIQ, Liquidacao.VALORTRIB, Liquidacao.ANOLIQ,

Liquidacao.DESCPERIODO, Liquidacao.CODTLIQ1, Liquidacao.IMPTRIB, Liquidacao.CODDLIORIG, Liquidacao.TIPODLI, Liquidacao.CODCRORIG,

ISNULL(dbo.IMPOSTODESD.NUMIMPDESD, Imposto.NUMIMP) AS NUMIMP, Contribuinte.NOMECTB, Contribuinte.NIFCTB,

CCCredito.VALORCCCREDITO, SGTALiqData.NUMDU, SGTALiqData2.OrdemNotas, SGTALiqData.CODCR, SGTALiqData.DATAEXPIRACAO,

Liquidacao.CODANULA,...

GilaMonster (5/25/2011)

---

SQL 2000 to SQL 2005 was a major change. not a...

There are changes to the query optimizer between 2000 and 2005. Because of this, you will see some changes in behavior. Most of the time you'll see improvements or no...

You need to look at what processes you're putting through tempdb. If it's growing that much, it's because it's being used, so you need to identify what it is that...

You might want to look up a process called log shipping. I think that will do what you need much easier than what you're talking about.

Also, you won't be able...

There are instances where a poorly written query performed adequately in 2000 but doesn't perform as well in 2005/2008. Usually fixing the issues with the query fixes the problem.

That's what it's basically doing, but it's doing it in a single command as opposed to two. Why do you ask?