Viewing 15 posts - 51,301 through 51,315 (of 59,091 total)
ALZDBA (4/2/2008)
And I've always been trying to avoid implicit conversions
Heh... understood. I don't think they make a hoot in the SELECT list... but, I guess I'm gonna have...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 12:16 pm
antonio.collins (4/2/2008)
No fair working at night... my wife won't let me get geeky at night.
Heh... understood... I keep telling mine "How can I miss you if you won't go away?"...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 12:13 pm
Marios Philippopoulos (4/2/2008)
But... assuming they have valid reasons, how can this be done safely and what does it involve?
That much I do know... It's going to be just like any...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 11:41 am
J (4/2/2008)
I have also used the approach of comma-separated single parameter but it has limitations:
- the is a practical limit to the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 11:34 am
Expensive move to compare all columns if you only care if a couple have been updated...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 11:14 am
That's a big one for me... the use of "Trusted Accounts" means that I don't have to hard-code user names or passwords in any code. Very big security advantage...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 8:25 am
Tim Riley (4/2/2008)
"Msg 8164, Level 16, State 1, Procedure sp_get_composite_job_info, Line 72
An INSERT EXEC statement cannot be nested."
There are 'INSERT' statements in various...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 8:23 am
On the subject of VM's... heh... Steve said he's got friends doing it... reminds me of what everyone's Mother in the World has probably said at one time or another......
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 8:15 am
No... just leave it like the other million or so posts. It's a resource that others can search on. Your post and it's answers might help someone else...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 8:12 am
Heh... you certainly did.
I'm mostly a data troll, so I don't really know... but my gut tells me that SQL Server probably shouldn't be calling a Web Service... maybe the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 8:09 am
Thanks, Jason... I'm still a newbie when it comes to 2k5.
Hey, Matt... why is on the fly bad for this?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 8:04 am
Rags (4/1/2008)
Jeff - Like I just said to J, I'm always up for learning new ways of doing...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2008 at 8:01 am
Temp Tables are created in the SQL Server TEMPDB database and therefore require more IO resources and locking. Table Variables and Derived Tables are created in memory.
Nice try on...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:06 pm
Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:46 pm
Would you please read what I said more carefully? The code I wrote does your split the way you want it... the load stuff was just a suggestion to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:43 pm
Viewing 15 posts - 51,301 through 51,315 (of 59,091 total)