Viewing 15 posts - 1 through 15 (of 177 total)
The very last comment in the article caught my eye -
Please remember to shrink the database to make the space available to the Operating System.
If you aren't aware...
December 6, 2013 at 6:15 am
I'm sorry, but I don't have that information any more.
August 28, 2013 at 11:58 am
I've been coding for 25+ years, starting out in COBOL on IBM mainframes. GOTOs when used wisely can provide an invaluable coding construct. It all comes down to the 'style'...
December 22, 2011 at 7:07 am
Ken -
I would say that either method of Shrinking the file (in 1GB increments or all in one go) will have just as negative impact of data fragmentation; as...
December 17, 2011 at 11:04 pm
James,
the quote from Kimberley's blog
In the end, the best amount is to allocate with a value of 8000MB instead of 8GB.
was actually related to the bug in SQL...
December 16, 2011 at 11:25 am
Just want to add a comment on the sizing for Log files. For an 8000MB initial allocation (or growth increment) of the log file, you are going to have 16...
December 16, 2011 at 10:49 am
You can have as many SQL instances on a cluster as you want, up to the limit of available drive letters. Each instance is hosted in a separate Resource Group,...
May 24, 2011 at 11:35 am
sqldba_icon (5/20/2011)
Can someone please tell me where is a CTE stored when declared or used inside a proc? Is it stored in memory or hard disk?
It seems to me the...
May 24, 2011 at 11:07 am
forsqlserver (5/24/2011)
...DAC to a named instance or the default instance if not using TCP/IP port 1433.
...
Just want to correct this - DAC does NOT use port 1433.
2005 - http://msdn.microsoft.com/en-us/library/ms189595(SQL.90).aspx
2008 -...
May 24, 2011 at 10:53 am
One other thing to remember is that Shrink process is single-threaded, and is incredibly slow, especially for a database at 600GB.
Before running a full shrink, you may want to...
February 18, 2011 at 7:02 am
Krasavita (2/7/2011)
...DBCC SHRINKDATABASE(N'virtualDBA', 10, TRUNCATEONLY)
...
The TRUNCATEONLY here means you don't have to rebuild / reorganize your indexes - its doesn't actually move any data around. Unfortunately, it also means that...
February 8, 2011 at 8:52 am
We had a stuck process recently - our problem was an Oracle database had issues and panicked (whatever that means), causing a query on a linked server to hang. In...
February 8, 2011 at 6:35 am
Good point, I had forgotten to check in SSMS 2005.
January 31, 2011 at 8:51 am
Artifacts in the System databases are protected to a large degree - hence the substantially smaller context menus for them. As far as I'm aware, this is by design and...
January 28, 2011 at 9:08 am
Regular SHRINK of a database is a very bad thing - see my article, and the lively discussion that followed: http://www.sqlservercentral.com/articles/SHRINKFILE/71414/ and Paul Randalls blog entry: http://www.sqlskills.com/BLOGS/PAUL/post/A-SQL-Server-DBA-myth-a-day-(930)-data-file-shrink-does-not-affect-performance.aspx.
January 25, 2011 at 9:02 am
Viewing 15 posts - 1 through 15 (of 177 total)