3
votes
2answers
86 views

Disk space full but logical space available in database

We have a fairly big MS SQL 2008R2 database that resides on a SSD drive. The drive itself only has ~110Gb of space, and the database files are the only files on the drive. The database is in "Simple" ...
2
votes
2answers
68 views

View Disc Usage

Is this statement correct? Behind the scenes SQL Server actually stores the data in the view as a physical table which must be updated if any of the data behind the view changes I did some ...
2
votes
0answers
160 views

How much disk space needed for 100GB of DBs?

Hard to explain in the title, but I'm planning a migration from SQL Server 2000 databases to SQL Server 2008 R2. The databases are under 100GB total space, but this is only with the Simple recovery ...
4
votes
1answer
237 views

Safe way to truncate SQL Server Error Log

We are running out of space. What is the safe way to clear the error log?
1
vote
3answers
1k views

T-SQL query to report disk space allocation and used space for auto-grow SAN databases

We are using 6 databases in total for an application, and we can only share 4TB of space for all 6 databases (via SAN storage). I'd like to write a query (report) for a single database indicating the ...
1
vote
2answers
110 views

Does an analysis/optimization tool like SqlYog exist for SQL Server 2005 (and later)?

I'm curious about effective space allocation of my tables, so: does something like SqlYog exist for SQL Server 2005 (and later)? Of course I know SSMS, but I was looking for something more precise ...
3
votes
2answers
209 views

SQL Server 2005: Full-text search space requirements

Is there a way to calculate the physical drive space required for a full-text search catalog? Space is cheap, but I'd like to know what I'm getting into. I'm looking at a table of about 200 articles ...
1
vote
1answer
444 views

SQL-Server: sp_spaceused gives zero rows but big dataSize for cleaned table

After cleaning my table with DELETE FROM MyTable (and executing DBCC shrinkdatabase('MyDB') should that matter) I run the statement EXEC sp_spaceused MyTable. The results confuse me: tableName ...
4
votes
1answer
177 views

Is there some drawback to define SPARSE columns?

I have a table which has a lot of NULL values in columns. But some columns don't contain NULLs at all (although nullable). Is there some drawback to declare all of these columns as SPARSE?