They indicated it was already resolved in 2000.  We have not seen the problem since moving, and I was unable to recreate it there.

What version of SQL, if 7 this is a known problem. We actually had the DB grown 2 or 3 times it's before size. Even after deleting a large amount...

Actually I would consider an Archive table

Select ? Into Archive_Inv_DeT WHERE ...

Select ? Into Archive_Inv_Hdr ...

Then Delete

For good luck put a marker in the Archive table indicating the date...

Not sure if even this would help.

Went to a MS presentation, last year so the memory is fuzzy, about Win2003.  They did demo some form of software that did do...

I sent these off to you folks.  Please give me any feedback etc.

Do use my personal e-mail. please.

As far as the growth script request, that will need to be developed.

I...

And Thankyou for posting the solution

I had sent Brian an article with scripts that do this automatically.

Still waiting to hear back from him on their decision.

I would look at something else.  No good ideas, but it looks like some software installation had problems.

FYI I am running Win2003 EE, with SQL2k EE without any issue's.

Not hit...

I had a similiar problem, but will agree with Happycat, NEVER use AutoShrink.

I do use autogrow, but usually by an amount, not %.  I'd rather wait for a big grow...

It's ugly but it works

 LEFT(Convert(Char(16), CAST(TBRows AS Money), 1), 13) AS '        Rows',

The LEFT ... strips off the decimal points.

Using Money), 1 puts in the commas.

You can adjust the Char(16)...

Try this, if it works you will lose any recoverablity to this point.

Change Recovery mode to Simple

Stop / Start the DB

Shrink the Log

Return the Recovery Mode.

Backup

Make Maint Plan !!!

Glad to help.  I drove me crazy for awhile until I figured it out.

Check that you have the GUEST account properly setup.  I had a similiar issue with ODBC connctors and found that someone (possibly me :-}) had deleted the guest account.  There...

Still testing, but I think fhanlon's trick did it.

This just goes to show that sometimes you need to NOT overthink the problem.  I was working with 2 subselects joined and...

It will be recreated smaller at the next restart of SQL.  Not always easy/possible with Production.