Viewing 15 posts - 53,206 through 53,220 (of 59,089 total)
Well, kind'a... haven't taken the time to CTE this puppy, yet... if you do, would you mind sharing it, please? Thanks...
The "key" is that at least one of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:18 am
Thanks for the feedback, Martin. Yeah, I have a grand love for such 3rd party shenanigan's myself... my favorite is loading data from a table into a Temp Table,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 4:48 am
Pretty much spot on...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 4:18 am
From what you've posted, I'd say just change the delimiter.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 4:13 am
Heh... considering that the OP said...
My friend faced the above questions in his recent interview.
... I'd have to agree 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 3:30 am
My bad... didn't say it correctly...
We don't allow individuals to create their own databases... just the DBA's. They're logged in with SA privs so no problems there.
We also require...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 3:24 am
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
Viewing 15 posts - 53,206 through 53,220 (of 59,089 total)