Viewing 15 posts - 53,221 through 53,235 (of 59,098 total)
I happened to be doing a little research on different methods for finding "gaps" and ran across this article. Here's a much faster way to find gaps... and, it...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 3:04 am
Now, I'm worried for you... the practice of "finding gaps" in a "sequence" column is usually accompanied by the insane idea that you'd ever reuse missing numbers. The INT...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 2:03 am
Gail is 100% correct... if all you want to do is add a "sequence" number to the table, then just add an IDENTITY column as she described.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 1:13 am
I always create them as "dbo" and grant privs... saves a lot of hassle...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:39 pm
I think keeping them in separate databases is usually a good idea... allows for customization by customer, if need be. If you write a script to accept a little...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:34 pm
You must have slept through that part of the 431 prep...
Please tell me they don't actually teach how to use Triangular Joins to derive running totals 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:29 pm
Just so everyone knows... that little slice of computational heaven will not parse the entire list if a number just happens to straddle the 4000 character mark. Instead, it...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 2:41 pm
Also, if a fellow by the name of "Madhivanan" responds to this thread, he's got some very good advice on OpenRowSet...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 1:18 pm
OpenRowSet is one fine way... please the following URL...
http://www.sql-server-helper.com/tips/read-import-excel-file-p01.aspx
That'll get you started... there are a couple of "finesse" tricks that we can talk about later on, but you need the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 1:17 pm
Mike C (1/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 1:06 pm
colin Leversuch-Roberts (1/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 1:02 pm
I appologize for the semantics... but, in SQL Server 2000, unless you take on the TEXT datatype as an input parameter, the largest character based variable you can define is...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 12:39 pm
Steve Jones - Editor (1/1/2008)
Or this: http://www.sqlservercentral.com/articles/Stored+Procedures/2977/
Heh... you think that's going to work on SQL Server 2000? This is a 2k forum, ya know 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 12:19 pm
Heh... if it's a very well written query, it will always run the CPU to 100%... just for a very, very short time... and that's the goal... get everything done...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 12:13 pm
Actually... good... typing on a blog lickety-split is one of the things that I'd like to get away from during an NCAA game. Leave your bloody laptops at home....
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 9:02 am
Viewing 15 posts - 53,221 through 53,235 (of 59,098 total)