Viewing 15 posts - 53,431 through 53,445 (of 59,098 total)
Heh... still at it even late on Christmas Eve, huh, Steve?
Merry Christmas, my friend...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2007 at 4:51 pm
Provided that you haven't disabled the built in administrator account...
Log into the WINDOWS server as the Administrator of the server.
Open Query Analyzer using the Windows NT authentication mode.
Run sp_password to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2007 at 3:42 pm
I'm basically wanting to write an in house app that will update my stored procedures across many databases that we have.
What do you want to do to the stored procedures?...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2007 at 2:59 pm
I'll go a little further to help practicing on indexes... here's how to build a million row table of test data... the details are in the comments...
--===== Create and populate...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2007 at 10:43 am
Just do a SELECT 1/0.... trust me, it'll throw an error 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
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!
--Jeff Moden
Change is inevitable... Change for the better is not.
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2007 at 5:19 pm
Why? And, pretty sure it's not possible.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2007 at 5:15 pm
AndrewSQLDBA (12/23/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
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....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2007 at 1:04 am
Viewing 15 posts - 53,431 through 53,445 (of 59,098 total)