{"id":46040,"date":"2026-07-30T08:30:38","date_gmt":"2026-07-30T06:30:38","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=46040"},"modified":"2026-07-30T08:36:37","modified_gmt":"2026-07-30T06:36:37","slug":"green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/","title":{"rendered":"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash"},"content":{"rendered":"\n

How often do I come across this sort of problem when visiting clients? Even more with our customers\u2019 service desk (support) SLAs.<\/p>\n\n\n\n

We turn up on a Monday morning and there are alerts from the weekend saying<\/p>\n\n\n\n

[MSSQL] – Instance Dark_Vador-Data(F:): Disk space in GB on server Death_Star is critical<\/em><\/p>\n\n\n\n

Info: NOT OK – Free space: 20 MB out of 200 GB<\/em><\/p>\n\n\n\n

The storage is almost full and:
– no projects were deployed over the weekend
– no exceptional data loads were scheduled
– nobody works at the weekend<\/p>\n\n\n\n

A strange phenomenon to come across on a Monday morning….<\/p>\n\n\n\n

On closer inspection, the findings are surprising; we can see that a database within the instance has been undergoing regular autogrowth for weeks…<\/p>\n\n\n\n

Every day, there are several regular autogrowth on the data file for this database until the saturation of the disk.<\/p>\n\n\n\n

Who is the culprit?<\/p>\n\n\n\n

Not the business data, but one or more tables named xxxxLog or Historyxxx, or the combination of both HistoryLog!<\/p>\n\n\n\n

PS: It\u2019s an example but in the reality before the weekend, we will have Warnings and in the majority of the cases we react before the critical alert of course!<\/p>\n\n\n\n

Data created to diagnose a problem, track an activity or maintain a history, which is then never cleaned up or has a default retention period that is too long and unsuitable for the context, is not always easy to detect.<\/p>\n\n\n\n

On the other hand, it\u2019s always easier to expand disk capacity without too much effort, and everything runs smoothly in an ideal world\u2026<\/p>\n\n\n\n

We, however, are Green SQL Server DBA; we\u2019ll look deeper.
Our curiosity will lead us to challenge the business on these points.<\/p>\n\n\n\n

The AUDIT<\/h2>\n\n\n\n

First, you need to know the autogrowth settings for these databases and how the data file growth.
Here is a simple script that shows the settings:<\/p>\n\n\n\n

SELECT\n    DB_NAME(database_id) AS DatabaseName,\n    name AS LogicalFileName,\n    type_desc AS FileType,\n    physical_name AS PhysicalFileName,\n    size \/ 128.0 AS CurrentSizeMB,\n    CASE\n        WHEN is_percent_growth = 1\n            THEN CAST(growth AS VARCHAR(10)) + ' %'\n        ELSE CAST(growth \/ 128 AS VARCHAR(10)) + ' MB'\n    END AS AutoGrowth,\n    max_size,\n    CASE\n        WHEN max_size = -1 THEN 'Unlimited'\n        ELSE CAST(max_size \/ 128 AS VARCHAR(20)) + ' MB'\n    END AS MaxSize\nFROM sys.master_files where type_desc='ROWS' AND database_id > 4\nORDER BY\n    DatabaseName,\n    FileType,\n    LogicalFileName;\n<\/code><\/pre>\n\n\n\n
Like for my precedent blog \u201cGreen SQL Server DBA Tips \u00a0#1 \u2013 Are unnecessary indexes cluttering up your database?<\/a><\/strong>\u201d, I use the Dynamics database as example:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
In my script, I exclude all system databases and the Log File to be concentrated to the Data File.<\/p>\n\n\n\n
Now, I need to have the data file growth. This is through the default trace file and the event 92:<\/p>\n\n\n\n
DECLARE @TraceFile NVARCHAR(500);\n\nSELECT @TraceFile = path\nFROM sys.traces\nWHERE is_default = 1;\n\nIF @TraceFile IS NULL\nBEGIN\n    RAISERROR('Default Trace is disabled.',16,1);\n    RETURN;\nEND\n\n;WITH GrowthEvents AS\n(\n    SELECT\n        DB_NAME(DatabaseID) AS DatabaseName, FileName, CAST(StartTime AS DATE) AS GrowthDate,\n        DATEPART(YEAR, StartTime) AS YearNum, DATEPART(WEEK, StartTime) AS WeekNum,\n        DATEPART(MONTH, StartTime) AS MonthNum, IntegerData * 8.0 \/ 1024 AS GrowthMB\n    FROM fn_trace_gettable(@TraceFile, DEFAULT)\n    WHERE EventClass IN (92) -- 92 is data growth\n)\n\nSELECT DatabaseName,FileName,GrowthDate,COUNT(*) AS GrowthEvents,SUM(GrowthMB) AS TotalGrowthMB\nFROM GrowthEvents GROUP BY DatabaseName,FileName,GrowthDate ORDER BY DatabaseName, GrowthDate\n<\/code><\/pre>\n\n\n\n
As I don\u2019t have any growth on the dynamicsBC database, I switch to the M-Files database for my example:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
We have here some daily growth…<\/p>\n\n\n\n
Go to see if we have historical or log tables in M-Files with this simple script who give us\u00a0 the table and the row count and MB:<\/p>\n\n\n\n
SELECT s.name AS Schema_Name,t.name AS Table_Name,\n    SUM(p.rows) AS Row_Count, CAST(SUM(a.total_pages) * 8.0 \/ 1024 AS DECIMAL(18,2)) AS SizeMB\nFROM sys.tables t INNER JOIN sys.schemas s     ON t.schema_id = s.schema_id\nINNER JOIN sys.indexes i ON t.object_id = i.object_id\nINNER JOIN sys.partitions p ON i.object_id = p.object_id  AND i.index_id = p.index_id\nINNER JOIN sys.allocation_units a ON p.partition_id = a.container_id\nWHERE t.name LIKE 'Histor%' OR t.name LIKE '%Log'\nGROUP BY s.name, t.name ORDER BY SizeMB DESC;\n<\/code><\/pre>\n\n\n\n
\"\"<\/figure>\n\n\n\n
The ANALISYS<\/h2>\n\n\n\n
In my case, we can see that we have 383550 lignes (19.73Mb) on the table named OBJECTTYPECHANGELOG for a M-Files database.<\/p>\n\n\n\n
It\u2019s only ~20MB here but in few months perhaps 20 GB or more…
<\/p>\n\n\n\n
As a Green SQL Server DBA, I will contact the owner of M-Files project otherwise don’t forget that dbi services has also the expertise in ECM tools like M-Files.<\/p>\n\n\n\n
The IMPACT<\/h2>\n\n\n\n
Like in my precedent post, we will have the same impacts<\/p>\n\n\n\n
The first impact is on DML INSERT operations.<\/strong><\/p>\n\n\n\n
With every insertion, the log or historical information is written to the table and update perhaps also index and at the end is never used by a query.<\/p>\n\n\n\n
The second impact is the storage and the backup<\/strong><\/p>\n\n\n\n
If the log table represents ~20 GB of the database.<\/p>\n\n\n\n
It\u2019s 20 GB backed up unnecessarily, 20 GB restored unnecessarily and, above all, 20 GB stored unnecessarily and just for one environment.<\/p>\n\n\n\n
If you have Dev, Test, PreProd & Prod and all in HA\u2026 I let you do the calculation but it\u2019s more 100 GB!<\/p>\n\n\n\n
The third impact is on the maintenance plan<\/strong><\/p>\n\n\n\n
The following operations must also handle the log\/historical tables:
\u2013 Rebuild Index
\u2013 Reorganise Index
\u2013 CheckDB
\u2013 Backups
\u2013 Restores<\/p>\n\n\n\n
Each growth of log\/historical tables extends the maintenance windows\u2026<\/p>\n\n\n\n
The ADVISE<\/h2>\n\n\n\n
You really need to be careful before deleting anything in these table.<\/p>\n\n\n\n
Don\u2019t Truncate the table because you see it!<\/p>\n\n\n\n
First see with the vendor if a purge or a retention parameter exists through the application. <\/p>\n\n\n\n
In my case with M-Files and the table OBJECTTYPECHANGELOG, in the administration interface, you can configure the retention. Go to challenge your M-Files team on it! \ud83d\ude09<\/p>\n\n\n\n
Finally, for every large log or historical table, you need to ask yourself the following questions:
\u2013 Who uses it?
\u2013 How often?
\u2013 Is there a legal obligation?
\u2013 What retention period is required?
\u2013 Can it be archived?
\u2013 Can it be purged?<\/p>\n\n\n\n
The Green SQL Server DBA Score<\/h2>\n\n\n\n
Like for my precedent post, I setup a \u2018SQL Server DBA Score\u2019 to use for my tips on the subject:<\/p>\n\n\n\n
Data growth per month<\/strong><\/td>Score<\/strong><\/td><\/tr>
0 to 2<\/td>10<\/td><\/tr>
3 to 5<\/td>8<\/td><\/tr>
6 to 10<\/td>5<\/td><\/tr>
11 to 20<\/td>2<\/td><\/tr>
> 20<\/td>0<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
A traditional SQL Server DBA or system administrator will see a data disk full and says:<\/p>\n\n\n\n
“How much GB need we to extend the disk?”<\/strong><\/p>\n\n\n\n
A Green SQL Server DBA sees a data disk full and says:<\/p>\n\n\n\n
“Why is my disk full and what can I do?”<\/strong><\/p>\n\n\n\n
Just like adding a larger trunk doesn’t make a car more efficient, adding more GB doesn’t make a database healthier.<\/p>\n\n\n\n
The greenest SQL Server DBA is not the one with the largest disks but it’s the one that keeps only data that continues to deliver value. \ud83d\ude80<\/p>\n\n\n\n
Think about it and begin now to see if you have cases!<\/p>\n\n\n\n
See you soon for the next one! <\/p>\n","protected":false},"excerpt":{"rendered":"
How often do I come across this sort of problem when visiting clients? Even more with our customers\u2019 service desk (support) SLAs. We turn up on a Monday morning and there are alerts from the weekend saying [MSSQL] – Instance Dark_Vador-Data(F:): Disk space in GB on server Death_Star is critical Info: NOT OK – Free […]<\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","_members_access_role":[],"_members_access_error":""},"categories":[229,198,368,525,1,99],"tags":[51],"type_dbi":[],"class_list":["post-46040","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","category-development-performance","category-enterprise-content-management","category-non-classifiee","category-sql-server","tag-sql-server"],"acf":[],"yoast_head":"\nGreen SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash\" \/>\n<meta property=\"og:description\" content=\"How often do I come across this sort of problem when visiting clients? Even more with our customers\u2019 service desk (support) SLAs. We turn up on a Monday morning and there are alerts from the weekend saying [MSSQL] – Instance Dark_Vador-Data(F:): Disk space in GB on server Death_Star is critical Info: NOT OK – Free […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-30T06:30:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-30T06:36:37+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/07\/autogrowth01.png\" \/>\n\t<meta property=\"og:image:width\" content=\"892\" \/>\n\t<meta property=\"og:image:height\" content=\"556\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"St\u00e9phane Haby\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"St\u00e9phane Haby\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/\"},\"author\":{\"name\":\"St\u00e9phane Haby\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0bfb7484ae81c8980fc2b11334f803b\"},\"headline\":\"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash\",\"datePublished\":\"2026-07-30T06:30:38+00:00\",\"dateModified\":\"2026-07-30T06:36:37+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/\"},\"wordCount\":913,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/07\\\/autogrowth01.png\",\"keywords\":[\"SQL Server\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\",\"Development & Performance\",\"Enterprise content management\",\"Non classifi\u00e9(e)\",\"SQL Server\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/\",\"name\":\"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/07\\\/autogrowth01.png\",\"datePublished\":\"2026-07-30T06:30:38+00:00\",\"dateModified\":\"2026-07-30T06:36:37+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0bfb7484ae81c8980fc2b11334f803b\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/07\\\/autogrowth01.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/07\\\/autogrowth01.png\",\"width\":892,\"height\":556},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0bfb7484ae81c8980fc2b11334f803b\",\"name\":\"St\u00e9phane Haby\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g\",\"caption\":\"St\u00e9phane Haby\"},\"description\":\"St\u00e9phane Haby has more than ten years of experience in Microsoft solutions. He is specialized in SQL Server technologies such as installation, migration, best practices, and performance analysis etc. He is also an expert in Microsoft Business Intelligence solutions such as SharePoint, SQL Server and Office. Futhermore, he has many years of .NET development experience in the banking sector and other industries. In France, he was one of the first people to have worked with Microsoft Team System. He has written several technical articles on this subject. St\u00e9phane Haby is Microsoft Most Valuable Professional (MVP) as well as Microsoft Certified Solutions Associate (MCSA) and\u00a0Microsoft Certified Solutions Expert (MCSE) for SQL Server 2012. He is also Microsoft Certified Technology Specialist (MCTS) and Microsoft Certified IT Professional (MCITP) for SQL Server 2008 as well as ITIL Foundation V3 certified. He holds a Engineer diploma in industrial computing and automation from France. His branch-related experience covers Chemicals & Pharmaceuticals, Banking \\\/ Financial Services, and many other industries.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/stephane-haby\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/","og_locale":"en_US","og_type":"article","og_title":"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash","og_description":"How often do I come across this sort of problem when visiting clients? Even more with our customers\u2019 service desk (support) SLAs. We turn up on a Monday morning and there are alerts from the weekend saying [MSSQL] – Instance Dark_Vador-Data(F:): Disk space in GB on server Death_Star is critical Info: NOT OK – Free […]","og_url":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/","og_site_name":"dbi Blog","article_published_time":"2026-07-30T06:30:38+00:00","article_modified_time":"2026-07-30T06:36:37+00:00","og_image":[{"width":892,"height":556,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/07\/autogrowth01.png","type":"image\/png"}],"author":"St\u00e9phane Haby","twitter_card":"summary_large_image","twitter_misc":{"Written by":"St\u00e9phane Haby","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/"},"author":{"name":"St\u00e9phane Haby","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/d0bfb7484ae81c8980fc2b11334f803b"},"headline":"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash","datePublished":"2026-07-30T06:30:38+00:00","dateModified":"2026-07-30T06:36:37+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/"},"wordCount":913,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/07\/autogrowth01.png","keywords":["SQL Server"],"articleSection":["Database Administration & Monitoring","Database management","Development & Performance","Enterprise content management","Non classifi\u00e9(e)","SQL Server"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/","url":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/","name":"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/07\/autogrowth01.png","datePublished":"2026-07-30T06:30:38+00:00","dateModified":"2026-07-30T06:36:37+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/d0bfb7484ae81c8980fc2b11334f803b"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/07\/autogrowth01.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/07\/autogrowth01.png","width":892,"height":556},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/green-sql-server-dba-tips-2-when-logs-and-history-records-cause-your-database-to-growth-and-crash\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Green SQL Server DBA Tips #2 \u2013 When logs and history records cause your database to growth and crash"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/d0bfb7484ae81c8980fc2b11334f803b","name":"St\u00e9phane Haby","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g","caption":"St\u00e9phane Haby"},"description":"St\u00e9phane Haby has more than ten years of experience in Microsoft solutions. He is specialized in SQL Server technologies such as installation, migration, best practices, and performance analysis etc. He is also an expert in Microsoft Business Intelligence solutions such as SharePoint, SQL Server and Office. Futhermore, he has many years of .NET development experience in the banking sector and other industries. In France, he was one of the first people to have worked with Microsoft Team System. He has written several technical articles on this subject. St\u00e9phane Haby is Microsoft Most Valuable Professional (MVP) as well as Microsoft Certified Solutions Associate (MCSA) and\u00a0Microsoft Certified Solutions Expert (MCSE) for SQL Server 2012. He is also Microsoft Certified Technology Specialist (MCTS) and Microsoft Certified IT Professional (MCITP) for SQL Server 2008 as well as ITIL Foundation V3 certified. He holds a Engineer diploma in industrial computing and automation from France. His branch-related experience covers Chemicals & Pharmaceuticals, Banking \/ Financial Services, and many other industries.","url":"https:\/\/www.dbi-services.com\/blog\/author\/stephane-haby\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/46040","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=46040"}],"version-history":[{"count":4,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/46040\/revisions"}],"predecessor-version":[{"id":46048,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/46040\/revisions\/46048"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=46040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=46040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=46040"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=46040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}