Heh... you should compare those with STUFF 😉

There's a bunch of "sys.All_" views that are "server wide".

Thanks for the feedback folks. 🙂

Sure, you could sub RowNum for *... not sure it matters for performance here as it might in other places. * allows it to pick the best index it...

Heh... that's probably why I'll continue to use S-Q-L... 😛

Truncate can be rolled back within an explicit transaction just as Adam said... try it on a table that can easily be rebuilt like a Tally table...

Google for sp_MSForEachTable...

The past "rocks", too... had to use rocks because the Abacus hadn't...

Heh... I gotta agree with that...

Moot point now, though... I just found out that they want to aggregate the aggregates in these views across the databases. Gotta trade in...

Ummm... be very careful using CROSS APPLY... it's just another way of making a "correlated subquery" which qualifies as RBAR and can be very slow.

I'm pretty sure recursion will be a performance killer here... please check out the XML code at the following URL (last bluish/purple code box in the article)...

http://www.sqlservercentral.com/articles/Test+Data/61572/

Forgive me for doing just a quick scan of the threads... couldn't you use the Information_Schema views for this?

Um.... if it's not a 3rd party application, check the "Model" database... sp_MSrepl_PAL_rolecheck is a sproc from the Master database and shouldn't exist anywhere else.

Compare what's in the sp_MSrepl_PAL_rolecheck sproc...

pauls2 (4/7/2008)

---

One of these days I'll actually recognize for myself when to use a tally table 😀 I have one built but didn't think to use it. ...

Now, there's a heck of a compliment. 😀 Thanks, MrPoleCat!