Viewing 15 posts - 1 through 15 (of 17 total)
Also check the properties of the Db's file and give full control to the domain user on the database files.
March 20, 2011 at 2:25 am
Just give more detail about your backup process:smooooth:
January 31, 2011 at 11:55 pm
REINSTALL is the only Option You have:smooooth:
January 31, 2011 at 11:52 pm
The machine which tried connecting to your sql server:smooooth:
January 31, 2011 at 11:50 pm
Anything You Are Able To Find In The Error Logs?
January 26, 2011 at 12:50 am
Yes
So if one of my log file is missing then the database goes into the suspect mode.
So what other reasons can cause the database to go into the suspect...
January 25, 2011 at 11:03 pm
Check out this link might help
http://www.sqlskills.com/resources/Whitepapers/SQL%20Server%20DBA%20Guide%20to%2
0SQLCLR.htm
January 25, 2011 at 5:27 am
Hi If all Users are only reading the data then just create a Snapshot of ur Db that will help you in a bigway
January 25, 2011 at 5:24 am
If huge transactions are happening and if the large insertions and deletions is a daily process then he don't have any other method.
January 25, 2011 at 5:14 am
Create a Job which daily shrinks your log files when the database is not in use.
January 25, 2011 at 4:48 am
Hi Satnam
alter table tablename
alter column columnname numeric(21,10)
by this command my data won't be lost as you know its a 130GB table and if anything happens to this...
January 25, 2011 at 4:40 am
Viewing 15 posts - 1 through 15 (of 17 total)