[font="Verdana"]Hi,

Since you are SQL 2005, you can use "Transfer Jobs Task" in SSIS, this will copy the jobs to another server.[/font]

[font="Verdana"]It looks like know bug with VDI, try the below hotfix to solve this problem

http://support.microsoft.com/kb/934396[/font]

[font="Verdana"]Hi,

Add a log file to the job and then try executing it, if it fails then analyze the log file, you will get some information.

You can also try the alternative...

[font="Verdana"]Try the below article.

Moving SQL2005 db to SQL2000 db[/font]

[font="Verdana"]Hi,

Apply SP2 for the default instance and then try connecting to it.

What is the error message you are getting while connecting to the default instance?[/font]

[font="Verdana"]Go for linked server, create linked server and make use of this linked server to issue select statement..[/font]

[font="Verdana"]Hi,

Database mirroring is supported from SP1, hence you need to apply SP2.

If not you need to enable trace flag 1400 in startup.[/font]

[font="Verdana"]Hi,

In SQL 2005 when you run a trace in background, a new trace will be created and the permission for this trace file is set only to SQL Service account...

[font="Verdana"]Hi,

You can try the article below to recover sa login!

http://blogs.msdn.com/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx

[/font]

[font="Verdana"]Why you are again going for SQL 2000 Enterprise, since the official support for SQL 2000 is already closed by MS. Better go for SQL 2005.[/font]

[font="Verdana"]Hi,

XP_Readerrorlog is an extended stored procedure.

SP_readerrorlog is a SP which will call xp_readerrorlog inside it. You can use sp_readerrorlog for many things, refer the link below.

The undocumented nature of...

[font="Verdana"]I hope both are not dependent hence you can install both the things![/font]

[font="Verdana"]Can you check in SQL Server configuration manager whether the below service exists?

SQL Server (MSSQLSERVER)

I think both the instances in on same port, create alias receptively and then try working...

[font="Verdana"]Hi Bill,

Can you provide the trigger code here?[/font]

[font="Verdana"]Hi,

I was not clear.. Do you need the list of logins exists in windows user panel or do you need to windows user name connected to SQL Server?[/font]