A rasta hat with dreadlocks. Wearing it is my signal to my coworkers that I am working on something that needs my full attention and I do not...

Thanks for responding, Perry.

Well, the developers didn't bother creating a backout script :ermm:

Why? It's not relevant at this point.

In my current job I went from a 90%/10% fix/mantain ratio to 5%/95%

I consider myself good at troubleshooting and tuning, those are the parts of my job that I enjoy...

This nice trick saved my butt in the past. Thanks for writing it down for us in SSC 😉

I bet that single line will make you reach your goal 😉

Great article Geoff!

I have used a trace-based approach in previous jobs to accomplish several monitoring tasks. It is basically as follows:

1.- Create a trace to capture whatever information you want...

:blink:

Geez.... believe it or not, Z's suggestion works. I have SSRS 9.0.4053

I'd love to post a better reply but I just can't get the words "what the heck?" out of...

I train tae kwon do 3 times a week. I've found that kicking other people and being kicked by them in a controlled environment relieves all the stress 😀

Oh, and...

I second Roland's comment.

I was involved in a similar situation before and since we were working with sql server 2005 I had the developer pass a xml value to the...

The funny thing here is that the database is configured for snapshot replication, not for transactional replication. And the db is in simple recovery model.

Unfortunately, I'm stuck with another problem...

Nope, I don't. Here's the result:

Transaction information for database 'XXXXX'.

Replicated Transaction Information:

Oldest distributed LSN : (0:0:0)

...

I'm having the same issue in a SQL Server 2000 database that is published for snapshot replication. If replication is messing the active portion of the transaction log, I don't...

Déjà vu...I did add this article to my briefcase last year...

Anyway...nice article, David.

Hahahah we all are SQL Server geeks =D

Happy holidays everyone!

I couldn't backup since the transaction log was full and there was no free space in the disk. I decided to take my chances since it wasn't a production environment....