Run...

Fair enough.

You shoould be aware though that having a logfile shrink, grow, shrik, grow like this will eventually see it fragmented all over your disk leading to long io's.

You can also try this one, quite uesful for SQL accounts as copies out the sid and the hashed password.

Doesnt do server roles though.

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

You need the specific oracle version driver to setup an odbc source on your SQL server.

We have 10g and i found that the only connector that would work was the...

abemby (4/13/2010)

---

Example database name: 'Cheerios'

Cheerios_log: this is the physical file name of the log file

Basic idea

change the db recovery mode to simple

clear log

...

Ivanna Noh (4/12/2010)

---

I've posted about this before, but it's relevant to this discussion too...

We have a mirrored database in production which is reindexed once a week - the reindexing causes...

Thanks Lynn,

We sit 4 feet from each other. Just playin silly-buggers 😉

dallas13 (4/9/2010)

---

Hello,

I have SQL Server and Agent running fine since years on sql 2005 X64 bit. all my jobs delivers emails once the job completes successfully. All...

Sorry, what do you mean?

Well you would look at what queries are going on while or just before the log grows and then you would just have to analys those queries (there cant be...

Your welcome. Hope its clearer now.

Track down in Resources when the log grew (using point-in-time) and then using the point-in-time, go to sessions and look at what was running.

If by chain you mean actual tape backups, thats down to your retention policies. As far as SQL is concerned, once you go through a db and log backup cycle,...

Though i would imagine that wouldnt be desirable if you used mirroring, like we do.

Idera has a really great tool for tracking this stuff. Its called Diagnostic Manager:

http://www.idera.com/Products/SQL-Server/SQL-diagnostic-manager/