It has come to my attention that some of our MSDB databases are getting what I would consider large for a system database. Some of our MSDB databases are over 2 GB which is a little perplexing because I know we do not create any user defined objects in that database. Can you give me some insight into the issue? I know we have this issue with both SQL Server 2000 and 2005 instances.
2008-04-14
4,246 reads
This article helps the DBA find and fix issues quickly by creating a DBA Morning Checklist.
2017-02-02 (first published: 2008-04-14)
59,265 reads
2008-04-11
5,076 reads
2008-05-27 (first published: 2008-04-10)
1,739 reads
Delete files on a fileshare leaving behind files not older than n-days.
2011-09-13 (first published: 2008-04-02)
10,042 reads
2008-03-21
4,412 reads
Creates a resultset that expresses the last time a successful CHECKDB was performed on every database in the instance.
Does not work on SQL 2000.
2011-09-28 (first published: 2008-03-19)
5,055 reads
A brief introduction into the world of scalability, presenting at a high-level the various options
2008-03-19
2,087 reads
2008-03-17
7,696 reads
2012-01-06 (first published: 2008-02-15)
7,308 reads
By Steve Jones
AI is a big deal in 2026, and at Redgate, we’re experimenting with how...
By Steve Jones
Another of our values: The facing page has this quote: “We admire people who...
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
Comments posted to this topic are about the item No Defaults Passwords Ever
Hi, We have low latency high volume system. I have a table having 3...
Comments posted to this topic are about the item The Long Name
I run this code to create a table:
When I check the length, I get these results:
A table name is limited to 128 characters. How does this work?