Viewing 15 posts - 54,856 through 54,870 (of 59,098 total)
Adding an Identity column to each table isn't that much work if you write a little dynamic SQL to do it for you... especially if you have it all worked...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 5:56 am
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:22 am
It's an SQL Server 2000 forum... no CTE's here...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:16 am
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:13 am
...or duplicated data...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:03 am
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,'.','')
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:02 am
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......
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 11:53 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:31 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:19 pm
Heard you can get paid for drinking beer 😉 Still looking for that one 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:14 pm
Yeah, huh? Can you feel the love there? :laugh:
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:13 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:06 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 9:50 pm
Knock knock... not locked...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 9:46 pm
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,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 7:30 am
Viewing 15 posts - 54,856 through 54,870 (of 59,098 total)