Not so much MSMQ, but Service Broker sure. Question is, are you willing to put up with the massive increase in complexity and increased administrative overhead (and it is high)...

Just sys.columns

Those are far from the same query and will execute very differently

Look up SET ROWCOUNT in SQL Books Online

That's insane. So every time things...

Never mind the bold one, the other three are an extremely bad idea. Shrinking the log just means it'll grow again, slowing things down as it does. Truncating the log...

Sure, those two articles that i posted the links to are just that.

As for the long running one,...

DropCleanBuffers drops everything from one of SQL's memory areas - the data cache. If you just run that you leave the procedure cache intact, the system caches intact, few other...

The max memory controls the buffer pool. There's always a little memory more that SQL uses - thread stacks, backup buffers, CLR, some other stuff. It's not usually big. If...

For a good introduction to triggers in SQL, please read this: http://www.sqlservercentral.com/articles/Triggers/64214/

craighenderson (11/25/2009)

---

My SQL Server 2005 has 38Gb allocated to it and its currently using 42Gb, problem is it never frees up any of this memory for other processes and the...

You need to investigate where the slow down is. Why are you returning thousands of rows to query analyser anyway? Who's reading those thousands of rows?

For an intro to performance...

Why? What are you trying to achieve?

craighenderson (11/26/2009)

---

This is what I was worried about, I currently have 25Gb in my buffer pool for my live DB and I was wondering if clearing this would make my...

Andrew Gothard-467944 (11/26/2009)

---

What it does is clear down your procedure cache - if you run against live you're going to see your box hammered until your most commonly used queries...