We have a client using our software with MSSQL and we are trying to solve a problem for them. We work more with MySQL so pardon my ignorance in the ways of MSSQL Server.
They have 3 volumes on that physical server: C:\; D:\; and L:\ The D:\ volume holds the SQL DBs, the L:\ volume holds the transaction logs.
The L:\ volume filled up due to some really awful preparation and management and before contacting us, they stopped SQL, moved the SQL transaction logs off to the D:\ where there was space, proceeded to make a new L:\ raid with larger physical disks, then moved the transaction logs back and restarted SQL services.
Since this point, they have been unable to login to SQL Management Studio or access the databases.
I was able to get in, but all the databases are flagged as (Suspect). I am unable to retrieve any properties on the databases at all.
Some Googling turned up some suggested queries to run against the databases to fix this problem, but I am reluctant to run them. Looks like part of it is a DBCC Check against the databases, but i'm not familiar with the rest.
Anyone have any advice on fixing this issue or know what may have occurred?
Thanks in advance for you assistance,