Viewing 15 posts - 51,961 through 51,975 (of 59,067 total)
In fact, i am having hundreds of columns in each of nearly eight tables.
I'm all done taking pot shots at a problem that keeps changing... Please, clearly define the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 3:59 am
Are you happy with the performance?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 9, 2008 at 9:50 pm
Gary E. Vernon (3/8/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 9, 2008 at 9:13 am
I dunno... to me, killing everyone's connection seems to violate a 24x7 SLA. I've used the same method at the table level before without killing any connections with no...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 9, 2008 at 9:10 am
That would be exactly correct... that's why I said "Code is not the only thing to consider where performance is concerned." 😀
By the way... if you're getting these times...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 9, 2008 at 8:50 am
Heh... I can explain that... since it's a "script", it may not be subject to the normal "code release" steps within a company, it's callable from DTS or SSIS, it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 9, 2008 at 8:44 am
No... I meant the LIKE thingy you wrote... but, I get it now... and, yes, you must've been bored 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 9:08 pm
Nicely done! Podcast is pretty darned cool, too!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 8:53 pm
Do what, Barry? Maybe I'm tired but I don't get what you're solving... please explain.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 7:51 pm
Mo,
Donn's method will do you just fine. If it needs to somehow be automated, let us know.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 7:42 pm
Yep. This is exactly what I meant. It runs once per each returned row from the main query. In my tests I was running FOR XML one...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 7:37 pm
rbarryyoung (3/8/2008)
FYI, varchar based date/time columns virtually always have bad data in them.
Nary a truer word spoken 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 7:31 pm
Good article... thanks for posting it. Just about anything by Adam is worth a look-see.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 7:08 pm
That's exactly what I was talking about... you asked why I would use something that I knew was slower... I knew that for the application I wanted, it would be...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 6:46 pm
One more thing... you left an extra comma at the end of your two outputs 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2008 at 5:42 pm
Viewing 15 posts - 51,961 through 51,975 (of 59,067 total)