Viewing 15 posts - 48,766 through 48,780 (of 59,093 total)
toniupstny (8/15/2008)
Hmmm.... I (re)read the article Jeff pointed to as the follow-up
Heh... it's been out for quite some time...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
and frankly did...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:09 pm
Ed Thompson (8/15/2008)
Good article to grow by, and very much look forward to Part 2.
Thanks Ed... the followup is at the following URL...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:00 pm
jcrawf02 (8/15/2008)
Steve & company led you in with "T-SQL Crackerjack Jeff Moden..." on today's feature - does that mean there's a prize in every Jeff? :w00t:
Heh... no... just surprizes... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 6:52 pm
toniupstny (8/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 6:50 pm
Charles Kincaid (8/15/2008)
Re-read the original article. Jeff points out the problem with using the index and points out that you should use order by instead.
Actually, in the Running Total...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 6:46 pm
Thanks for the feedback, David.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 6:05 pm
I'm such a dummy... to do this in almost a single click, I just need to turn of the SQL Server Agent and turn it back on when I'm done....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:58 am
No, no... the deleted rows aren't a problem... my appologies for not being a bit more clear (pretty much under the gun and not thinking correctly). The rows are...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2008 at 4:25 pm
I think I've got this... I'd have to disable all 70 Log Reader Agents... and then turn on just the ones that were previously disabled. Sounds like a real...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2008 at 2:55 pm
Oh yeah... almost forgot... the reason why I don't do the copy, delete, and rename thingy is because I don't know if it'll break replication or any of the associated...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2008 at 2:49 pm
rbarryyoung (8/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2008 at 2:47 pm
GilaMonster (8/14/2008)
Having fun as an administrator today?
Oh hell no! 🙂 I'm not a "systems" type of DBA and I've never used replication before. I'm one of them...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2008 at 2:38 pm
Ok... thanks Gail. And, heh... thanks for not killing the OP for his ignorance in this area. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2008 at 2:25 pm
Aw crap! They've scheduled a job for every blood Log Reader Agent!!! I'm going to need to disable those buggers, too, huh?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2008 at 2:08 pm
GilaMonster (8/14/2008)
Jeff Moden (8/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2008 at 2:04 pm
Viewing 15 posts - 48,766 through 48,780 (of 59,093 total)