Database Research & Development

  • Home
  • NoSQL
    • NoSQL
    • Cassandra
  • Databases
    • Database Theory
    • Database Designing
    • SQL Server Coding Standards
    • SQL Server
    • PostgreSQL
    • MySQL
    • Greenplum
    • Linux
  • Interviews
    • SQL Server Interviews
    • MySQL Interviews
    • SQL Puzzles
  • DBA Scripts
    • SQL Server DBA Scripts
    • PostgreSQL DBA Scripts
    • MySQL DBA Scripts
    • Greenplum DBA Scripts
  • Home
  • Blog Archives !
  • (: Laugh@dbrnd :)
  • Contact Me !
sqlserverinterviews
Home 2017 May SQL Server: Why Shrink Database is bad, Check the practical demonstration

SQL Server: Why Shrink Database is bad, Check the practical demonstration

This article is half-done without your Comment! *** Please share your thoughts via Comment ***

Few of SQL Server DBAs are frequently executing Shrink on database or data files. Why? because they are gaining more free space after shrink.

You can find N number of theory on, why you should not shrink your database or data file in SQL Server?

Instead of big theory, I am sharing full practical demonstration on this. You should not shrink your database or data files otherwise it generates massive fragmentation for your tables and indexes. Still, you can shrink your log file, but after full backup only.

Create a test database and use it:

1
2
3
4
5
CREATE DATABASE Test_Shrink
GO
 
Use Test_Shrink
GO

Create a sample table:

1
2
3
4
5
CREATE DATABASE Test_Shrink
GO
 
Use Test_Shrink
GO

Create second sample table with clustered index:

1
2
3
4
5
6
7
8
CREATE TABLE tbl_test2
(
id INT IDENTITY(1,1)
,tag CHAR (7000) DEFAULT 'dbrnd'
)
GO
CREATE CLUSTERED INDEX pk_test2 ON tbl_test2 (id);
GO

Insert few sample records in both the tables:

1
2
3
4
5
INSERT INTO tbl_test1 DEFAULT VALUES;
GO 1500
INSERT INTO tbl_test2 DEFAULT VALUES;
GO 1500

Check the average fragmentation of Index:

1
2
3
4
5
6
7
8
9
10
SELECT
[avg_fragmentation_in_percent]
FROM sys.dm_db_index_physical_stats
(
DB_ID (N'Test_Shrink'), OBJECT_ID (N'tbl_test2'), 1, NULL, 'LIMITED'
)
GO
 
--The result is:
--0.33%

Drop one sample table to test Shrink:

1
2
DROP TABLE tbl_test1;
GO

Shrink your database:

1
2
DBCC SHRINKDATABASE (Test_Shrink);
GO

Check the fragmentation of index:
You can find below result like 99.6% fragmentation for Index. Before shrink database, it was just 0.33%.

1
2
3
4
5
6
7
8
9
10
SELECT
[avg_fragmentation_in_percent]
FROM sys.dm_db_index_physical_stats
(
DB_ID (N'Test_Shrink'), OBJECT_ID (N'tbl_test2'), 1, NULL, 'LIMITED'
)
GO
 
--The result is:
--99.6%

Now, REBUILD your index to remove the fragmentation:

1
2
ALTER INDEX pk_test2 ON tbl_test2 REBUILD
GO

Check the fragmentation of index:

1
2
3
4
5
6
7
8
9
10
SELECT
[avg_fragmentation_in_percent]
FROM sys.dm_db_index_physical_stats
(
DB_ID (N'Test_Shrink'), OBJECT_ID (N'tbl_test2'), 1, NULL, 'LIMITED'
)
GO
 
--The result is:
-- 0%

May 25, 2017Anvesh Patel
SQL Server: Who dropped a table, find out from Transaction LogSQL Server Interview: If Outer transaction ROLLBACK, what happens to Inner transaction

Leave a Reply Cancel reply

CAPTCHA
Refresh

*

Anvesh Patel
Anvesh Patel

Database Engineer

May 25, 2017 SQL ServerAnvesh Patel, database, database research and development, dbrnd, fragmentation, Shrink Database, SQL Query, SQL Server, SQL Server Administrator, SQL Server Error, SQL Server Monitoring, SQL Server Performance Tuning, SQL Server Programming, SQL Server Tips and Tricks, TSQL
About Me!

I'm Anvesh Patel, a Database Engineer certified by Oracle and IBM. I'm working as a Database Architect, Database Optimizer, Database Administrator, Database Developer. Providing the best articles and solutions for different problems in the best manner through my blogs is my passion. I have more than six years of experience with various RDBMS products like MSSQL Server, PostgreSQL, MySQL, Greenplum and currently learning and doing research on BIGData and NoSQL technology. -- Hyderabad, India.

About DBRND !

dbrnd

This is a personal blog (www.dbrnd.com).

Any views or opinions represented in this blog are personal and belong solely to the blog owner and do not represent those of people, institutions or organizations that the owner may or may not be associated with in professional or personal capacity, unless explicitly stated.

Feel free to challenge me, disagree with me, or tell me I’m completely nuts in the comments section of each blog entry, but I reserve the right to delete any comment for any reason whatsoever (abusive, profane, rude, or anonymous comments) - so keep it polite.

The content of this website is protected by copyright. No portion of this website may be copied or replicated in any form without the written consent of the website owner.

Recent Comments !
  • Anvesh Patel { Sure will do... } – May 27, 12:43 PM
  • Anvesh Patel { Great... } – May 27, 12:41 PM
  • Anvesh Patel { Great... } – May 27, 12:39 PM
  • Anvesh Patel { Great... } – May 27, 12:36 PM
  • Anvesh Patel { Great... } – May 27, 12:28 PM
  • Anvesh Patel { Great... } – May 27, 12:27 PM
  • Anvesh Patel { Great... } – May 27, 12:16 PM
  • Older »
Follow Me !
  • facebook
  • linkedin
  • twitter
  • youtube
  • google
  • flickr
© 2015 – 2019 All rights reserved. Database Research & Development (dbrnd.com)
Posting....