Viewing 15 posts - 51,256 through 51,270 (of 59,098 total)
{insert sounds of cheers and applause here}
Congrats one and all! Job well done!
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 11:17 pm
To further Jacob's suggestion... here's the test code...
--===== Do a couple of presets for appearance
SET NOCOUNT ON
SET ANSI_WARNINGS OFF
--===== Simulate a 2...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 11:12 pm
Only way to tell is to see the code 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 10:50 pm
You will never get an INDEX SEEK using SELECT *... only index scans.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 10:48 pm
Not enough coffee, Sergiy... which method are you recommending to use?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 10:45 pm
How many items can you have? Also, should they all be in separate columns or ???
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 10:41 pm
Heh... I handed Babbage gears 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 10:14 pm
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
Viewing 15 posts - 51,256 through 51,270 (of 59,098 total)