Pretty much the worst thing you could do to a SQL Server database. In short: It sacrifices performance to gain space.

learn more… | top users | synonyms (1)

1
vote
1answer
508 views

Stop never ending backup in SQL Server 2012 Express

Our production database log file has grown to consume all disk space on our server. I know it's bad practice but I want to be able to shrink it in order to restore the service as soon as possible. ...
0
votes
1answer
31 views

Using SHRINKDATABASE to shrink a Database by a certain amount

I have a database which the users are going to do some data cleansing on. They should do this every 6 months but have left it for 18 months. After they have cleansed the data I want to shrink the ...
0
votes
1answer
8 views

Shrink configuration & content database in Sharepoint DBs

There was some argument between me and a college about for how we should shrink DBs. We knew that shrinking should be manual and only if required. We run in a case that configuration DBs reached to ...
1
vote
0answers
1k views

DBCC SHRINKFILE EMPTYFILE not emptying

Trying to remove an extra database file from a database using EMPTYFILE on SQL Server 2008 R2. use [MYDATABASE] DBCC SHRINKFILE (MY_DATABASE_7, EMPTYFILE); use master ALTER ...
1
vote
0answers
131 views

Why does shrinking the transaction log generate lots of log (LOP_SHRINK_NOOP) and not shrink the log?

I just tried shrinking an overly big log file (FULL recovery model). This operation is not expected to always succeed and indeed the log was not shrunk. But I observed that a lot of new log was ...
0
votes
0answers
91 views

Transactional Replication issue due to big Transaction Log in sql server 2008 r2

I want an answer of question and that would be highly appreciated Scenario: First of all i am an IT guy from Sports Field and using SQL Server 2008R2. I have 2 production servers server 1 and Server ...
0
votes
0answers
74 views

Relationship between file shrink and used memory in SQL Server

Some background info: this is a test SQL Server 2012, with restored databases from production servers, all of them with over 20% space available in the data file, up to even 50%. I'd rather restore as ...