1

Topic: Help to understand, why the broad gull grew to 400 . And how correctly to reduce it

Good afternoon.
The basis file hardly less than 2 , and a broad gull file was inflated to 430 .
Request:

select name, recovery_model_desc, log_reuse_wait_desc from sys.databases

It turns out, recovery_model_desc = SIMPLE, and log_reuse_wait_desc = REPLICATION
The database is in a simple mode of recovery, and I suspect that a problem of it: log_reuse_wait_desc = REPLICATION.
On request (what above), all bases have log_reuse_wait_desc = NOTHING, except for the problem.
How correctly to translate problem basis in log_reuse_wait_desc = NOTHING?
And the main thing how then to reduce a basis broad gull?

2

Re: Help to understand, why the broad gull grew to 400 . And how correctly to reduce it

_UUS wrote:

I suspect that a problem of it: log_reuse_wait_desc = REPLICATION.

yes.
Probably, replication was in that basis from which this recovered from .
Look at a forum for "replication removal".

_UUS wrote:

And the main thing how then to reduce a basis broad gull?

Simply make  a broad gull file.

3

Re: Help to understand, why the broad gull grew to 400 . And how correctly to reduce it

alexeyvg wrote:

it is passed...
Yes.
Probably, replication was in that basis from which this recovered from .
Look at a forum for "replication removal".
it is passed...
Simply make  a broad gull file.

as that so to make?:

use [__];
dbcc shrinkfile (2, 10)

4

Re: Help to understand, why the broad gull grew to 400 . And how correctly to reduce it

alexeyvg;
Thanks. The question solved