this made your sql services to be stopped.

You need to find out why the services get stopped.

keep digging into application log and system log in event viewer of the system.

If its cluster check the cluster log.

not sure either wives can short the work hours or not but if they succeeded in this then definately your rest of the hours will be extended to either shopping...

can you see the execution plan for this slowness, i.e., where the resources are consuming most.

Also just a suggestion to try, if you have select query in your SP,...

yes, first you need to create the linked server.

Once you created the linked server then

use msdb

go

exec [your linked server name].msdb.dbo.sp_start_job

@job_name...

you can create various role in your application and then tag the users in those roles.

So for example you have one group as AppAdmin who have unrestricted access of...

the account you configuring in security tab, you need to be make sure that account have requried permission...

did you tried with third option, 'be made using the login's current.......'?

Also the account you configured with password, does that user have enough permission to configure the linked server?

if you doing this in sql server 2008 and selecting 'server type' as other data source then this provider will...

any update???

is that resolved your problem???

i am trying to replicate the problem, but till then you can have a look of this article :-

http://support.microsoft.com/default.aspx?scid=kb;en-us;90111&Product=acc97

Also I am assuming, your excel file is not password protected

can you try to create linked server using gui..

Steps are(as mentioned in support.microsoft) :-

In SQL Server Management Studio, expand Server Objects in Object Explorer.

Right-click Linked Servers, and then click New...

excel 8.0 is compatible for excle 2007 and below.....is your excel file meeet this requirement?

you need to create the group in Active Directory. Then that group will be given required permission in sql

follow this article from line 'SQL Server 2005 and SQL Server 2000'

http://support.microsoft.com/kb/224071