Viewing 15 posts - 53,401 through 53,415 (of 59,064 total)
Just do a SELECT 1/0.... trust me, it'll throw an error 😉
December 23, 2007 at 11:30 pm
Correct... If the IDENTITY column is the last column, you wouldn't need a list of columns in the INSERT clause.
Heh... I've got a real live appreciation for being a bit...
December 23, 2007 at 10:59 pm
Absinthe (12/23/2007)
1.
I was not saying that the code was fast, merely that it specifically satisfied the described problem of doing it inline without...
December 23, 2007 at 7:07 pm
C'mon, Midan... this one is easy. Figure it out. If you're returning a column you don't want, then remove it from the SELECT list!
December 23, 2007 at 6:37 pm
Here's an example of how bad your "gee-whiz" factor code is... first, create the following test table... yeah, I know... It uses SELECT INTO... just do it...
--===== Create and populate...
December 23, 2007 at 5:58 pm
Not worth the risk? What risk? I think you're over reacting to "Clone SQL Advise". SELECT INTO will create a new table with a million rows in...
December 23, 2007 at 5:19 pm
Why? And, pretty sure it's not possible.
December 23, 2007 at 5:15 pm
AndrewSQLDBA (12/23/2007)
December 23, 2007 at 5:13 pm
Then take a look at "recursive CTE" in Books On Line for 2k5 and look for "Using a recursive common table expression to display a hierarchical list". They've got...
December 23, 2007 at 5:06 pm
Good to see I'm not the only one stuck with 7 year old software at work, Ian. To keep up though, I finally broke down and installed the Dev...
December 23, 2007 at 7:57 am
Absinthe (12/21/2007)
Jeff Moden (12/21/2007)
The best answer for SQL Server 2000 is, in fact, the Temp Table solution. It's nasty fast, especially if you use a SELECT/INTO.
Red Flag time again....
December 23, 2007 at 1:04 am
A covering index could certainly help... but there's a lot of things that will change an Index Seek into and Index Scan... usually non-sargeable WHERE clauses and ON clauses. ...
December 23, 2007 at 12:22 am
Then, it should be a single table. If you make it an "adjacency" (parent/child) model, you may be ok depending on how you're going to drill down and how...
December 23, 2007 at 12:20 am
Not only is it a "doosie", but it's darned near a duplicate...
http://www.sqlservercentral.com/Forums/Topic435994-361-1.aspx
December 23, 2007 at 12:10 am
Which "above script"... don't waste time, be specific, please.
You also said you wanted to update the table with address info... heh... what if a person has 2 addresses?
December 23, 2007 at 12:07 am
Viewing 15 posts - 53,401 through 53,415 (of 59,064 total)