Same here .. nice question!

It's nice to know how SQL Server uses his space 🙂

Even in Chrome, I can not...

I've tried to use Notepad, but still 1 line in the code box.

I use IE9.

When I'm at work, I will try to use Chrome...

Nice question, glad I received a point 🙂

But you can disable or Re-enable a Table for Full-Text Indexing 🙂

http://technet.microsoft.com/en-us/library/ms142536.aspx

I had the same problem for the index rebuild.

A possible solution was to reorganise the index in place of rebuilding.

And when reorganizing, take log backups frequently...

I had the help of...

No I don't append 🙂

I will do a check exist...

It's indeed the same filename for the log backup... I will change this in the script.

I already made an extra job step, when the log backups failed the next step...

I see.. the backup filename of this job is the same as the one from the backup job.

So if I change the log backup filename of this script, this can't...

I've created an extra step in the job...

So when the logging step fails, I'll restart this step...

But this isn't a good solution 🙁

I've start using the script and check job's in production.

But today I've received an error with the log backups...

Seems the extra log backup (each minute while reorganizing index) came in...

Hey Ninja's_RGR'us,

As promised, I would reply after our testing.

I've test the index (exported the table and index) on my desktop here.

And it worked well!

Went from 83.82% to 0,01%.

Tested the stopping...

Temporary solution: add a scheduled task in Windows to start the bat file... this works

But that...

Your start as DBA'er 🙂

I don't know the configuration of your db's, but when this would be your daily maintenance plan, I will put your recovery models into 'Simple', so...

And how do you check if the cleanup task started before the log backup?

But I don't understand why you make this chain?

You make a full backup and directly a log...