Viewing 15 posts - 36,211 through 36,225 (of 59,102 total)
I certainly could be wrong but, from the following entry in the log you posted, it looks like something may be starting up on the server BEFORE SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2010 at 8:41 am
GilaMonster (10/29/2010)
p.s. The last integrity check of any of these databases was almost 2 years ago. You like living dangerously?
That actually brings up a good subject. Do you happen...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2010 at 8:09 am
PaulB-TheOneAndOnly (10/29/2010)
Don't put in your resume anything that can be used against you or better rephrasing it: don't lie to the extend that your CV is your death warrant.
Or, as...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2010 at 7:52 am
GilaMonster (10/29/2010)
Alvin Ramard (10/29/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2010 at 7:49 am
Nah... I've seen your code on other threads. I just got lucky here. If the data had 5 elements, our code would have been a whole lot more...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2010 at 7:46 am
If you always have 3 parts, the following will do the trick. I've not tested it to see if it's any faster but I do know that 3 REVERSEs...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 6:21 pm
I wouldn't "be" a 100 years ago... I would have died 148 years ago from blood poisoning or 146 years ago from a really nasty case of double Pneumonia.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 6:08 pm
Craig Farrell (10/29/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 5:41 pm
Grant Fritchey (10/29/2010)
Jeff Moden (10/28/2010)
Brandie Tarvin (10/28/2010)
Now I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 8:42 am
GSquared (10/29/2010)
Jeff Moden (10/29/2010)
Paul White NZ (10/27/2010)
Jeff Moden (10/27/2010)
Steve Jones - SSC Editor (10/27/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 8:23 am
Lynn Pettis (10/29/2010)
The OP is generating a flat file, so in my opinion formatting the date in T-SQL is acceptable as there is no GUI or reporting tool.
Just for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 8:16 am
I'll certainly Google it but we know how that sometimes goes... so let me ask... for those of you who have gone through a SOX audit on SQL Server (or...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 6:26 am
{Flat file} Ah... so I see. I missed that in the OP. Thanks, Lynn.
It really is still an issue that the original data has a non-DATETIME column...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 6:11 am
WayneS (10/28/2010)
So you've got two SQL Spackle articles already done?
I do. I also ran into a couple of problems at work recently and solved them. They're also something...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 6:08 am
Paul White NZ (10/27/2010)
Jeff Moden (10/27/2010)
Steve Jones - SSC Editor (10/27/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2010 at 6:04 am
Viewing 15 posts - 36,211 through 36,225 (of 59,102 total)