When it ballons again run this query and post the results (or do your research, you'll find that info quite easily).

SELECT log_reuse_wait_desc FROM sys.databases where name = 'tempdb'

the bottom line...

DECLARE @d DECIMAL(10,10)

SET @d = 1.0

--fails

DECLARE @d DECIMAL(20,10)

SET @d = 1.0

--works fine!

This is for sql 2005 but it's still relevant to sql 2000.

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

Waiting on checkpoint??

Are you talking about log_reuse_wait? Which would be a little moot in simple recovery.

Or task waits, where your copy of the activity monitor script could come in...

Somethings along those ling could do it too... just to have 2 options.

SELECT

T.name,

STUFF((

SELECT

...

Don't use XML.

I'm not the expert in that domain but a simple csv file with bulk insert usually flies the data in. Everytime I,ve been near xml it's always...

Jeffrey Williams-493691 (8/9/2011)

---

Don't drop the nonclustered indexes - disable...

Oh for God's sake => http://www.microsoft.com/sqlserver/en/us/product-info/compare.aspx

Couldn't find the same layout for 2008 but => http://recruitmentexchange.com/download/SQL2008_editions_features.pdf

Here, now you can all move on! 😀

My link still works. I strongly recommend you at least look at the code samples.

Sean Lange (8/9/2011)

---

The confusion of pages in a windows application may well be the first clue that they are not actually sure what the question is. Windows apps don't have...

Ok, then check if the join logic is correct. Distinct / group by <usually> should not be required for this if the table design is correct. It might...

SELECT * FROM

(

SELECT id, WorkerID, LaborRateID ROW_NUMBER() OVER(PARTITION BY WorkerID ORDER BY id DESC) AS rn FROM ...

) dta

WHERE rn = 1

There might be a way to do it...

Best book around for that... and free => http://www.sqlservercentral.com/articles/books/65831/

Jayanth_Kurup (8/9/2011)

---

Oops , my mistake . I tried running Backup Log with truncate only and it didnt bring the size down.

However MSDN state the following

NO_LOG | TRUNCATE_ONLY

Removes the inactive...

<Almost> no change. Bottom line is that every single estimate is wrong, at every level.

Let's try to clean this mess up.

Take the first query. Start using joins, remove...

Don't be.

I'm just explaining the hidden reason behind our lack of answers on a very simple question. If you really want...