Skip to main content
deleted 284 characters in body
Source Link
DoubleVu
  • 305
  • 1
  • 8

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

UPDATE

I might have found the problem. I'm performing a DBCC CHECKTABLE on each table and it's stuck on one of the table's with only 4 records (I looked on the other server) and has used over 200 GB of tempdb space while continuing to check it. This table has 1 clustered index and 2 nonclustered indexes on it.

I can select from theThe table, even though that didn't pass DBCC CHECKTABLE gets hung on, I recreated its indexes and will see if it verifies faster.

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

UPDATE

I might have found the problem. I'm performing a DBCC CHECKTABLE on each table and it's stuck on one of the table's with only 4 records (I looked on the other server) and has used over 200 GB of tempdb space while continuing to check it. This table has 1 clustered index and 2 nonclustered indexes on it.

I can select from the table, even though DBCC CHECKTABLE gets hung on it.

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

UPDATE

The table that didn't pass DBCC CHECKTABLE, I recreated its indexes and will see if it verifies faster.

added 79 characters in body
Source Link
DoubleVu
  • 305
  • 1
  • 8

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

UPDATE

I might have found the problem. I'm performing a DBCC CHECKTABLE on each table and it's stuck on one of the table's with only 4 records (I looked on the other server) and has used over 200 GB of tempdb space while continuing to check it. This table has 1 clustered index and 2 nonclustered indexes on it.

I can select from the table, even though DBCC CHECKTABLE gets hung on it.

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

UPDATE

I might have found the problem. I'm performing a DBCC CHECKTABLE on each table and it's stuck on one of the table's with only 4 records (I looked on the other server) and has used over 200 GB of tempdb space while continuing to check it. This table has 1 clustered index and 2 nonclustered indexes on it.

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

UPDATE

I might have found the problem. I'm performing a DBCC CHECKTABLE on each table and it's stuck on one of the table's with only 4 records (I looked on the other server) and has used over 200 GB of tempdb space while continuing to check it. This table has 1 clustered index and 2 nonclustered indexes on it.

I can select from the table, even though DBCC CHECKTABLE gets hung on it.

added 328 characters in body
Source Link
DoubleVu
  • 305
  • 1
  • 8

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

UPDATE

I might have found the problem. I'm performing a DBCC CHECKTABLE on each table and it's stuck on one of the table's with only 4 records (I looked on the other server) and has used over 200 GB of tempdb space while continuing to check it. This table has 1 clustered index and 2 nonclustered indexes on it.

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

I have a database that's size is 100GB. When I run CHECKDB on it, it fails to due a lack of space for tempdb, which has over 1TB of space. I can restart my SQL Server, flush out tempdb, the drive has 1TB of available space, and run it again, and it will use everything and fail due to a lack of space.

I suspect the database is corrupt because this seems like odd behavior, but is there a scenario where a 100GB database would use more than 1TB for running CHECKDB?

UPDATE

I might have found the problem. I'm performing a DBCC CHECKTABLE on each table and it's stuck on one of the table's with only 4 records (I looked on the other server) and has used over 200 GB of tempdb space while continuing to check it. This table has 1 clustered index and 2 nonclustered indexes on it.

Source Link
DoubleVu
  • 305
  • 1
  • 8
Loading