Heh... thanks, Lowell... you're too kind :blush:

Clarence,

If your barcodes/customer numbers get above 11,000, you can very easily change the "Tally" table to a million, but I wouldn't go much higher...

It's an SQL Server 2000 forum... no CTE's here...

Hi Mick,

Long time, no see...

Just an FYI... be real careful about using SET ROWCOUNT... if the queries after the SET have ORDER BY on large tables, you're going to...

...or duplicated data...

Doesn't matter if it's varchar or not... your method still works...

declare @i decimal(10,2)

Set @i = 1078.734

PRINT REPLACE(@i,'.','')

Already did... look at my previous post... the one where I tell you to just lock the table. Also, Remi asked how many total rows are in the table......

Yeah, I know it's not "monitoring"... but, when you figure out that the hardware is doing it's very best and you're still having performance problems...

Step 1... search code for cursors

Step...

Cherie,

Just a tip in case you didn't know... if you get such an error in Query Analyzer (message window), the first thing you should probably do is to double click...

Heard you can get paid for drinking beer 😉 Still looking for that one 😀

Yeah, huh? Can you feel the love there? :laugh:

Greg,

Check for "System Stored Procedures, Overview" in the Index of Books Online. Gives a fairly large listing of "supported" system stored procedures. There are also some "extended" stored...

If it's only 100K rows, lock the table when you do the delete... it'll take less than 10 seconds if you do it right.

Of course, if you have 72 indexes...

Knock knock... not locked...

Like I said... there's a couple of summary articles on SQLServerCentral.com... just do a search for them... some thing like "Differences between SQL Server 2000 and 2005" should do...

Of course,...

Piet van der Westhuizen (9/26/2007)

---

OK I made it sound very simple.

My data looks like this in tblTransactions (all hypothetical) 🙂

Factory Item PurchasePeriod Spend

=============================

Fact1 ...