Viewing 15 posts - 53,941 through 53,955 (of 59,072 total)
Heh... thanks for sharing the solution!
It does show that in order to solve a problem, we sometimes need to know everything about the problem. But a fine line can...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:49 am
Sure... the "N" part of the N(N) thing is just a way of assigning the derived table an alias of "N". The "(N)" part of that assigns the only...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:38 am
Concur... We'd all be in deep doo-doo if we had to write "generic" solutions that met all needs from SQL Server 6.5 through 2k8.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:20 am
Hi Rudy,
Do you happen to have an MS URL that states that so that I can calm some of the current "panic" occurring at work?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:14 am
Hi Michael,
VB and Excel returns the same value.
I'm currently coding T-SQL again to see where the problem lies.
Be specific, please... what value is that?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:12 am
However, I don't want the lines with all the fields (about 150 for my table).
Not a problem... it'll depend on the actual query you write.
In addition, I want the values...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:00 am
Ok... are we working in VB or T-SQL???
And, please provide a sample of the input that you currently have that is not being transformed to your liking as well...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 7:38 am
p.s. And a million rows isn't much so far as SQL Server is concerned... certainly, it's not sufficient for justification of 2k5 or 2k8. I've got lookup tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2007 at 9:26 am
My recommendation would be... unless you have an immediate need for the Security enhancements, there's not much you can't do in a relatively simple manner in 2k T-SQL including Row_Number,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2007 at 9:22 am
aureolin (11/24/2007)
you'll never see me use a While Loop to create a list of contiguous dates... I'll always use a Tally table for that (and a lot more).
Sounds like a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2007 at 8:54 am
In the example previously given, there are 2 groups... 1 has 3 data points and the other has 4. Would you provide the "8 data points" for the example...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2007 at 7:48 am
Funny thing... you never know if you solved their problem when they don't respond 😉 Pretty rude, too... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2007 at 9:48 pm
Sure... anytime you return less, it will usually return faster.
Lemme ask... are you using the GRID mode, or the TEXT mode? As you probably know, the Grid mode is...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2007 at 2:04 pm
I know... old post... but, I've gotta ask...
Why in the the world would you do a SELECT * with no criteria on a table that contains 180,000 rows? You...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2007 at 1:02 pm
Dang... not good... hides the "problem".
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2007 at 11:32 am
Viewing 15 posts - 53,941 through 53,955 (of 59,072 total)