SQL won't easily give you the totals at the bottom of columns. Your front end would do that.

It is important to test and be sure. You might have great techniques in your toolbox, but they won't always apply.

One of the weird things about SQL is your "rules"...

How big is the db?

A blanket, weekly schedule can work, but it can use more resources than needed. There are lots of scripts on this site that calculate fragmentation and...

That is indeed, scary

Thanks, grass....

That always gets me a chuckle. I think you might need a dual rotor chopper for that mission!

It can fragment, and you'd need to rebuild the clustered index to fix this. In EE you can do this online.

Or I do!!!!! :w00t:

Very interesting.

SQL does mark the physical records in a heap, AFAIK, with something to be sure they are unique. I have heard before that the optimizer likes clustered indexes, so...

this help?

http://msdn.microsoft.com/en-us/library/ms179316(SQL.90).aspx

http://msdn.microsoft.com/en-us/library/aa337560(SQL.90).aspx

Out of curiosity, where did that syntax come from (original post)? another platform or SQL version?

Not really. The backup runs as the service account, so it needs rights to get across the network.

Note that network backups are not recommended. If there's any network hiccup, the...

Answers changed, points awarded back.

Sorry

As many as you want.

I know there might be a max stored procedure byte count (or batch size), but apart from that, as many as you want.

How many do...

I'd experiment with the counts. I've had systems run better with 1000 than 10,000, but it's varied. Test a little, maybe for few batches and get timings.

How are you compiling as a script? Perhaps there's something in the script that gets left out. For example, a GO might terminate a batch, and let the rest of...