Still wants a mapped drive.

Been there, done that, got the t-shirt. Run into a number of apps that "think" they need sa. Every time, we've managed to cut their permissions to db_owner at most...

Steve (8/11/2009)

---

...well I guess it depends as to whether a server restart is required. If SQL already grabbed the "max" memory it's not going to release it. I...

Issuing a RECONFIGURE will make the memory settings take effect.

This takes one table in master, two stored procedures, and one job that is set to execute on startup and calls the first stored procedure ([master].[dbo].[auto_MemoryReconfigure]). I set the...

If anybody's interested, I figured out how to rebalance the memory on a cluster. I can use almost all the memory on each node, and still handle a failover. I've...

Steve (7/23/2009)

---

Is this a two node cluster? Just to understand, you're running 4 instances, two per node. If that's the case then you probably would have each server...

We're running 2 instances on each node in a cluster (and I wish we weren't). Between trying to balance the disk space (no SAN either) and the memory, its...

Yes, you can add another virtual disk. I had to build it "outside" the cluster group that SQL was in, then add it in as a cluster group resource. Once...

Ok, here's the recovery procedure we use. It does make use of some custom scripts to restore. Some of the scripts are run during the every day backup and maintenance...

We've got a full document that starts from the point of a loss of the cluster. I'll have to see if it can be posted. Basically, the document starts from...

TheSQLGuru (5/12/2008)

---

>>Direct attached storage isn't an option, as it's a clustered server. Also corporate policy states all servers will use SAN storage. <<

The first statement is a wive's tale. ...

HOLY CRAP! :w00t::w00t::w00t::w00t: I rewrote the query based on Jeff's Running Total post, and it went from 8 hours to 6 seconds! Jeff, I bow down before you! THANKS!!!!!!!

--===== Build...

rbarryyoung (4/30/2008)

---

Also, this bit here:

...

SELECT @@fetch_status

WHILE @@fetch_status = 0

BEGIN

IF @ChkItem <> @CumItem

BEGIN

Set @ChkItem = @CumItem

Set @mCid...

Ok, my bad. I was in a hurry last night, and didn't get everything in the shape it should have been. Here's a full script end to end that will...