Viewing 15 posts - 51,256 through 51,270 (of 59,091 total)
Bob Boursaw (4/6/2008)
With all due respect, I have read Ken's post about 200 times over this weekend and unfortunately, due to my lack of experience and knowledge with SQL,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 10:12 pm
If I need to insert constants, I use INSERT/SELECT... if I need to insert more than one row of constants, I use INSERT/SELECT/UNION ALL... I can't actually remember the last...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 9:59 pm
Composite PK's are wonderful... but not for this problem. It would be so much easier if you had an IDENTITY column named RowNum because, like I said, this is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 9:56 pm
Jack Corbett (4/6/2008)
Essentially a unique clustered index is a primary key. A primary key defines uniqueness and, in SQL Server, when created defaults to a clustered index.
True... it also...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 9:45 pm
Actually, you need to go back and review Kent's response... it's pretty much spot on.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 7:21 pm
What is the Primary Key of the table called "Test"?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 7:10 pm
It is possible in a view if you create a column called "TableName". Look at how they do it with the Information_Schema views... particularly the Information_Schema.Columns view.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 9:53 am
Gates should give everyone who bought Vista a free copy of XP to install whilst we all wait for a decent version of Windows (7?) to come out in 2009....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 9:36 am
Since it worked fine for both Matt and I, I've got to ask... are you actually using SQL Server or are you using some other RDBMS?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 9:32 am
jos.haemers (4/6/2008)
I've posted a CREATE script for the facttable with a few records. I can't post any queries because there an no queries yet. In the future the customer wants...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 9:30 am
Heh... and I thought I was old... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 9:20 am
Rather than "warming the cache"... try analyzing the code to see where indexes would help you solve the problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2008 at 11:07 am
As previously stated, Cursor and loops of this nature WILL kill any hopes of performance...
Your pseudo code said...
-- IF TotalPrice > 0 ...sqlCodeHere
What do you want to do for...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2008 at 11:03 am
Something is very wrong here... the original query posted by the OP works just fine.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2008 at 11:00 am
You might want to post the CREATE statement for your fact table and maybe 10 or so rows of data (see the URL in my signature line for the right...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2008 at 10:55 am
Viewing 15 posts - 51,256 through 51,270 (of 59,091 total)