Yes, we were running out of memory in the visible region (MemToLeave). In short the amount of space allocated to this region of memory in Win32 is limited (~1.2GB/instance). Having...

It turns out we were running out of memory in the visible region (MemToLeave). In short the amount of space allocated...

Thanks for the response. That is one of the known bugs we checked out right away. With our situtaion DBCC Memory status shows no signs of any memory pressure anywhere.

Thanks again, We have plenty of memory, and agree any risk is very low. I am going to apply the parameter.

OLTP aticvity is short, bursty transactions. Warehouse activity is large scanning, sorting, and aggregation. On the disk level the OLTP will do quick highly randomized lookups and small quick writes. Warehouse...

You need to backup your transaction log periodically to purge old tranasctions. The frequency of the backup depends on the amount of activity in your database. Another option is to...

Products like WanSynch are excellent solution for DR for many environement b/c they are very effective means of replicating databases but also provide addition functionality that help automate site-to-site failover....

This waitstate can be caused by things such as functions and linked servers. You may not have a problem here... These numbers do appear very high at first, but they...

You need to use DOMAIN/USER_NAME. So if your domain is "TestDomain" and your user is SQLAdmin you would enter

TestDomain\SQLAdmin

Hopefully you have already created seperate domain accounts for SQL...

The NET START command (OS) will list started services

As long as there more available memory on your server SQL will choose to consume the memory rather than push data out of memory. SQL will continue to consume memory until...

There is a "compatability level" setting for each databases (master.sysdatabases.cmptlevel, sp_helpdb). This value is set at 80 for databases migrated from 2000 to 2005, and 90 for databases built on 2005....

It sounds like you have installed a local instance rather than a Clustered instance. In SQL Install you need to check the box for "Create a SQL Server failover Cluster"...