Hi Sasidhar,

I was not able to reproduce that issue. Can you please post the code and the job step details?

It is possible through VB Script as well. In addition to the Powershell link which I posted earlier, this has an even bigger repository.

http://gallery.technet.microsoft.com/scriptcenter/en-us/site/search?f%5B0%5D.Type=RootCategory&f%5B0%5D.Value=activedirectory&f%5B0%5D.Text=Active%20Directory

afaik you can only read information from Active Directory through SQL Server. SSMS does not have an option to "manage active directory".

You can make use of Powershell. More details here

'xp_restore_verifyonly' in turn makes use of RESTORE VERIFYONLY command. VERIFYONLY will verify that the backup set is valid. More details here.

The time it takes to verify the backup is always...

You can make use of a script similar to the one below.

CREATE LOGIN [computername$] FROM WINDOWS;

To add to the list, one more with screenshots.

http://www.db-staff.com/index.php/microsoft-sql-server/87-upgrade-sql-2005-cluster-to-sp3

Check the System/Application Event log and SQL Server Error Log when the system boots up. These logs would have some information as to why SQL Server service is not starting...

Please check if there is another instance of sqlservr.exe running in Task Manager.

On which OS are you installing SQL Server 2005? If it is Vista or Windows Server 2008 you may find this KB article useful.

Cross post. All replies at http://www.sqlservercentral.com/Forums/Topic1033318-146-1.aspx

This is applicable when the System Name is in Lower case. In that case the error message will...

Have a look at Redgate's SQL Monitor

If Default Trace is running, then a query similar to the one below can be used.

SELECT

LoginName,max(StartTime)AS LoginTIme

FROM ::fn_trace_gettable('C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\log_493.trc',0)

where LoginName='loginname'

GROUP BY LoginName

This information...

Add db_name() in the select list of the query that Lowell had given.

Please check the logs located under C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG folder for the possible reason for this error.