Viewing 15 posts - 26,656 through 26,670 (of 59,099 total)
mysorian (6/10/2013)
Use a parametrized query.
Yeah... and all you have to do to get to the Moon is build a rocket ship that will support human life.
Seriously... post some code....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 8:40 pm
Krishna1 (6/9/2013)
I have procedure A,B,C. Procedure A calls B and C. Procedure B and C have loops and print statement in the loop (for me to understand whats happning)....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 4:56 pm
OTF (6/10/2013)
You can use the RAISERROR Statment with the NO WAIT option to achieve the behaviour you want.
You should probably tell the "rest of the story" there. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 4:46 pm
TheSQLGuru (6/10/2013)
Tim Walker. (6/10/2013)
I'm interested to know how easy they are to implement and what benefits / issues people...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 4:31 pm
arun1_m1 (6/10/2013)
Hi,For the past few days...
Past few "[font="Arial Black"]days[/font]"??? :blink: BWAAA-HAAAA!!!!! Welcome to America where a whole lot of people have had the same problem for the past few...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 4:20 pm
Nice article, Mannie. Yes... I absolutely agree. Reading the comments is important. That's why most of the scripts I post on the forums say "Details are in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 4:03 pm
scorchpc 96170 (6/10/2013)
will do, I'll let you guys know the resultsThanks again!
Simplify the code by removing the FILLFACTOR part of the code. The indexes will rebuild with the original...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 2:36 pm
ben.brugman (6/10/2013)
Sean Lange (6/10/2013)
Secondly, this now has to create a second connection to the same server. Yes it can be done but you have to jump through a lot of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 2:33 pm
Sean Lange (6/10/2013)
g_demetriou (6/10/2013)
IIRC you can use OPENROWSET after the FROM clause
It is a bit more complicated than that. First of all you have to have ad hoc queries turned...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 1:17 pm
opc.three (6/10/2013)
Eh, and really, who needs it? 😀
Everyone who wants to avoid increasing the surface area by firing up SSIS. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 1:07 pm
Kingston Dhasian (6/6/2013)
dwain.c (6/5/2013)
Stefan Krzywicki (6/5/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 12:59 pm
The Dixie Flatline (6/4/2013)
Jeff Moden (6/4/2013)
Brandie Tarvin (6/4/2013)
1) SCREAM really loudly so everyone knows there is a problem.
2) Run out of the building as fast as possible.
3) Update...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 12:53 pm
Brandie Tarvin (6/7/2013)
...users can always find a way to mess with our data no matter how dummy-proof we make it.
Idiot's Razor: "If you make something idiot proof, only idiots will...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 12:52 pm
Brandie Tarvin (6/7/2013)
Co-worker points out problems with future process.
Boss responds: "Don't bring reality into this..."
And yes, he was joking. It was a commentary on...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 12:43 pm
plivingstone (6/10/2013)
it would be Tuesday
An example from last month:
May 27th was Bank Hoiliday Monday, so if the [Date] columns shows any date after 22nd May then it cannot be deleted.
So...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2013 at 12:41 pm
Viewing 15 posts - 26,656 through 26,670 (of 59,099 total)