My rule of thumb is to open it up... see how big it get's between backups... and then make it's initial size twice that big to handle "contingencies". Other...

Hi Tod,

I think you're headed down the right path... you haven't said anything (yet) that I don't think can be done in T-SQL. Your re-evaluation of the situation sounds...

Ok... 3rd time I've asked... If you let us know what the CLR is supposed to do, we can tell you if it can be done in T-SQL and maybe...

You bet... thanks for the feedback, Eric.

Ah crud... my bad... I gotta learn to read which forum these are in... I know squat about reporting services... my appologies.

Ah... just a note... if the concatenation exceeds 8000 characters in SQL Server 2000, there's virtually no chance of displaying the full width of the concatenation and we may have...

... If the max number of Sequences is not known... we can convert this to something a bit more dynamic...

Typically, yes... correlated subqueries tend to be slower than a nice derived table...

Hi Tod,

Still would like to know what the CLR does (general explanation would do) because there's a lot of times when folks will write a CLR instead of doing it...

I guess my first question would be... what does the CLR do?

??

Ack... agreed... I missed that... not enough coffee... :hehe:

Not sure I'd waste my time benchmarking for that...

Why not just Google a bunch of articles about SQL Server Maintenance... lot's of them say "why"...

It doesn't... from the way you were talking, I thought you were using a "blank formatted" spreadsheet file as a template that you copied for new files.

What are you currently...

Nice 2k5 solution... but I'm pretty sure that it won't work in 2k... 😉