Viewing 15 posts - 51,241 through 51,255 (of 59,091 total)
rbarryyoung (4/7/2008)
Well, NOT IN has had some bugs in SQL Server 2000, so that is certainly possible. They are mostly cleared up in Sql2005.
What kind of bugs, Barry?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2008 at 6:51 am
You will never get an INDEX SEEK using SELECT *... only index scans.
My most sincere apologies... the comment above does NOT apply to INDEXED VIEWs.
What matters is what you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2008 at 6:36 am
rbarryyoung (4/6/2008)
Jeff Moden (4/6/2008)
Heh... I handed Babbage gears 😉Good one. 🙂
I was serious about my Uncle though, he really did do all of that stuff.
I have no...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2008 at 5:57 am
Either way, you're going to annoy someone!
Not to worry... Anyone who actually takes the time to get upset at either isn't someone you have to worry about offending because, although...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2008 at 5:51 am
If it's temporary... (from Books Online)
SET IDENTITY_INSERT [ database_name . [ schema_name ] . ] table { ON | OFF }
If it's permanent removal you want, you'll need to define...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 11:42 pm
My apologies... see the following URL for how to make a Tally table...
http://www.sqlservercentral.com/scripts/Advanced+SQL/62486/
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 11:27 pm
This is the second time this same question has been asked... and just like I said on that identical post, directly updating system tables is a form of "Death by...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 11:23 pm
We're getting there... in the example you just gave, should 1 2 3 be in a single column or 3 columns? If 3 columns, what shall be their names?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2008 at 11:19 pm
{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
Viewing 15 posts - 51,241 through 51,255 (of 59,091 total)