New answers tagged sql-server-express
It sounds like the database is corrupt. Before you do anything further, make a copy of the files, and only work with copies. You might try the following, in case the problem is isolated to the log: CREATE DATABASE [GRMStemp] ON (FILENAME = 'c:\wherever\MDF_File.mdf') FOR ATTACH_REBUILD_LOG; If that fails, there is a forum post on MSDN by Paul Randal ...
Error 601 means When scanning with the NOLOCK locking hint or with the transaction isolation level set to READ UNCOMMITTED, it is possible for the page at the current position of the scan to be deleted. When this happens, Microsoft® SQL Server™ is not able to continue the scan. You may want to try this: SET TRANSACTION ISOLATION LEVEL READ ...
Here is a good script I shamelessly ripped from here: use [Insert DB Name] select a.FILEID, [FILE_SIZE_MB] = convert(decimal(12,2),round(a.size/128.000,2)), [SPACE_USED_MB] = convert(decimal(12,2),round(fileproperty(a.name,''SpaceUsed'')/128.000,2)), [FREE_SPACE_MB] = convert(decimal(12,2),round((a.size-fileproperty(a.name,''SpaceUsed''))/128.000,2)) , ...
The size of the database is the size of the file. Look at the actual size of the data file (the transaction log doesn't count). Yes indexes count. If you are running out of space consider an upgrade to SQL 2012 Express as that increases the size limit to 10 Gigs.
Top 50 recent answers are included