Search results for query: *

You should be fine so long as you have everything backed up. For good practice make sure evreything is posted, no batches stuck out waiting for a posting. If you really want to be safe and have plenty of time, I would possibly use a VM environment. The select a small accounting team to do...

In practice we are usually talking kb's or mb's for the entire OLE folder and all the OLE objects. Size/space is not a major concern with the size of most hard drives today.

Your SQL logs would have that info, but it would be a lot of trouble to start tracking that info.

This link below should get you started in the right direction: http://msdn.microsoft.com/en-us/library/cc280701.aspx

RiverGuy, your idea is best. I overlooked the fact he merely needs to run the updates twice a day. DTS is the way to go, good call. I have done cross server triggers with no problems, not relevant in this case. Thanks, John T.

DTS is fine for scheduled processing, but if you want live updates, a trigger is the best way to go. Your update trigger code will be keyed to any change to records in the original db. Hope this helps, there is a wealth of online info outlining code examples for all types of SQL triggers.

Ooops. Meant copies/updates record in the 2nd db. Of course, you may want to delete records from the 2nd db when deleted from the original.

Why not write a trigger than copies/replaces each record in the 2nd database each time an original Customer record is updated or added? Hope this helps.

What type of report is this, I assume you are talking about the owner of the SRS job as scheduled thru SQL Agent? Thanks, John

Make sure to include the domain name in the recipient address; jsmith@mydomain.com Also, are you running in a clustered environment?

You can turn on the profiler and limit it to just updates and deletes, but only for future activity.

Narrow down the specific modules that your users are having performance issues with, you may want to run checklinks for these modules if you have not done so.

I had the same problem and did it out of desperation, when I lost power, I was offered the startup options and took safe just to check things out. After finding nothing wrong in Safe Mode, I rebooted normally and everything worked. I am assuming some Windows OS process involving SQL was...

Restart the server in safe mode and let it boot completely up. Then check your event logs. The error should have stopped, reboot and start normally.

Apply the service pack for SQL Express. Check your event logs, make sure nothing odd happened the upgrade. I would also create a complete maint plan and do all the index rebuilds, repairs, etc. Good luck!

Does it only happen when using a roaming profile? Is anything getting written to your event logs on the server when this occurs?

Try saving it as sql script and then view using query tool. Just a thought.

Check this link: http://www.devnewsgroups.net/group/microsoft.public.sqlserver.xml/topic52999.aspx

What domain rights do you have as the user running RDP, admin? (I hope) I assume you are running the profile trace as SA? Also, have you restricted all the applications, users, etc. that you are tracing? Ideally I would only want to trace the app getting the deadlocks and also eliminate...

Before we go any further, have you checked out this link? http://support.microsoft.com/kb/919399