Viewing 15 posts - 256 through 270 (of 433 total)
There are so many links for interview questions.
blog.sqlauthority.com/2007/04/21/sql-server-interview-questions-and-answers-complete-list-download
http://www.dotnetquestion.info/dot_net/sql_server.php
http://www.techinterviews.com/
All the Best 🙂
December 4, 2007 at 11:52 pm
Yes that sound good, Please go ahead and open a case with MS. Update us also .
December 3, 2007 at 7:15 am
The problem is you have a composite Primary key in the master table
( emp)--right ?
Emp table : Primary Key is
empno , empname , emp_city --> composite primary key
Again the...
December 3, 2007 at 7:12 am
Check that you have enough permission to run the debugger and in my case I applied the SP4 and it worked.
November 30, 2007 at 6:21 am
Remove a named instance of SQL Server
=====================================
Beautifully described in the following KB : 🙂
November 30, 2007 at 6:16 am
May be a new bug..not sure better contact support.
November 30, 2007 at 6:08 am
To bring the database to emergency mode
Exec sp_configure 'allow updates',1 reconfigure with override
update sysdatabases set status = 32768 where name ='dbname'
Please check BOL for more info.
Rememeber 823...
November 30, 2007 at 3:28 am
[SQLSTATE 42000] (Error 22029) is a generic error
Please try to run this command and you will find the exact error message
select * from msdb.dbo.sysdbmaintplan_history
post that error message !!
November 30, 2007 at 1:05 am
I think you have manupulated the mdf file. This should be done in any case that is the reason for DB to be in suspect.
Is there any recent full DB...
November 30, 2007 at 12:12 am
Try this ..
Select * from sysdatabases .
The Compatibility level cmptlevel is different for 2000(80) and 2005 (90) sysdatadases.
🙂
November 29, 2007 at 10:46 pm
Purnell is right follow that. Is it possible to resetup the Log shipping once again. That might help.
November 29, 2007 at 10:39 pm
It is good you got back ur data. It may happes so the data are commited to the mdf file after chaging the recovery model you were able to run...
November 29, 2007 at 6:28 am
Similar bug is there in SQL Server 2000 for SQLMaint.exe.
Check this link :
November 29, 2007 at 5:01 am
I think .. the agent does not have sufficient privileges.. check that
November 29, 2007 at 4:47 am
Viewing 15 posts - 256 through 270 (of 433 total)