Well it happened again. Did some more digging into the specific services that were failing and I'm sure it'a a low memory condition causing such havoc.

I've confirmed with Imceda that...

It backups locally then Robocopies to a network drive. The frustrating part is that the backup step slowed down 17 minutes and the robocopy step slowed down 16 minutes. SO...

Other than the exception log I couldn't find any dump files. I looked at all files modified yesterday.

I'm getting a battery needs reconditioning on a controller but that was the...

Raj,

We deploy the same scenario you are considering.

Use LiteSpeed to backup, robocopy to "backup array" (staging area) then write to tape via Veritas.

It's the best solution we've found so far...

I had the same request last fall so what I did was setup a new instance with only the payroll user (it's a SQL account not NT, I'm sure not...

Thanks so much

K

We've been throwing around ideas of how best to integrate with Source Safe. I like your idea and I think it would solve some other issue we have. But my question...

We're on SQL 2000 sp 3, server is on Advanced Server but workstations are XP or 2000 Pro.

I script them out to Unicode txt file when I restore our dev...

I know I've had to take db.execute SQL statements and turn them into queries with higher timeout settings to get them to run.

You may be looking at the same...

Sounds like you're using a query, open it in design view click the Properties button (make sure it says Query Properties not field properties) and set the ODBC Timeout to something...

We'll try that.

Control is passed back to the app and it appears to be successful. But not all statements in the procedure were ran.

In trying to track this down we...

Yes you are correct, didn't read close enough on the version chart.

It is no longer a supported option.

There's no way I can give him sysadmin due to some of the other data on the server so I'll just have to ensure the developers use use dbo....

That does work and I canimplement this as part of our standards.

But I still don't understand why it creates them as dbo for my NT account but no others.

I have the same issue, changing to bulk-logged was the only way around it. I think it's better to have the job take longer than it is to run out...