I wouldn't be surprised if your backup is being made by "others".

To figure that out, you could set up a trace to capture backup details.

You could even get a first...

How about some Powershell love to help with this: Export top n SQLPlans

it depends:

A scalar value function (SVF ) is called like

Select SVFSchema.SVF( value_to_be_used )

A table value function (TVF ) is called like

Select x.col1, ...

from TVFSchema.TVF( value_to_be_used )...

old thread !

but anyway, here's a fix for it: http://blog.armgasys.com/?p=259

Corrective Action

Disconnected all clients from the Principal database

Forced the Principal database...

What has been the goal of you dropping the windows login from these instances ?

You may want to change the job-owner for these jobs to sa and/or execute their steps...

can you double check these windows logins aren't having login auth via granted windows groups?

I would suggest to setup a bcp batch job using SQLAgent, providing the jobstep proxy account only with the needed authorisation to read the source data and write to the...

cls

$Path = 'c:\temp\'

$RefTs = ([datetime](Get-Date -Format 'yyyy-MM-dd')).AddHours(20) # 8PM

$RefTs

# select and delete files having last write time before RefTs

get-childitem -Path $Path -Filter '*.txt' -Recurse | Where-Object { $_.PSIsContainer...

- do you need to just copy the data once ?

you could use bcp.exe to do that.

- are you sure you really want to make both sqlserver...

how a simply clever trick just blows your mind.

I wonder how many people only read this Spackle once and really got it.

I just copied it to ssms and walked it...

I haven't used the builtin maintenance plan since early sql2000.

I use sql server backup devices. http://technet.microsoft.com/en-us/library/aa173665(v=SQL.80).aspx

Maybe that's a path you may want to investigate to overcome this issue.

some may consider the extra space a security feature :crazy:

Simplest way is to modify the job step command and remove the space.

If you cannot rename the database (which may need...

it depends on the SLA for "high available".

Of course, mirroring can be configured to be synchronous, but is depricated for future versions, because Always On is the "new" kid in...

did you try:

select c.*, u.*

FROM Company c

INNER JOIN SAMINC.dbo.ARCUS y

on y.IDCUST = c.comp_companyid

inner JOIN SAMINC.dbo.ARSAP z

on z.CODESLSP = y.CODESLSP1

inner...

start it all running the Upgrade Advisor for SQL2008R2!

This free tool will notify for potential issues.

have a look at Using Upgrade Advisor to Prepare for Upgrades