Viewing 15 posts - 4,816 through 4,830 (of 7,168 total)
TheSQLGuru (3/23/2012)
opc.three (3/22/2012)
March 23, 2012 at 4:13 pm
So I just ran a bunch of queries to warm up the buffer pool and got the committed memory up to 2.44GB with "AWE on, 3GB off"
physical mem, VAS, buffer...
March 23, 2012 at 3:27 pm
For the server now using "AWE on, 3GB on" I never tested "AWE on, 3GB off" but I just found a good dev-server that is a candidate for this treatment....
March 23, 2012 at 3:15 pm
george sibbald (3/23/2012)
March 23, 2012 at 2:30 pm
Mhlewis (3/23/2012)
March 23, 2012 at 2:22 pm
Jeffrey Williams 3188 (3/23/2012)
March 23, 2012 at 1:12 pm
Jeffrey Williams 3188 (3/23/2012)
opc.three (3/23/2012)
March 23, 2012 at 1:07 pm
Mhlewis (3/23/2012)
March 23, 2012 at 12:50 pm
Your readings are completely normal. SQL Server will claim as much memory as you allow it provided it thinks its needs it to efficiently serve data to clients. 1.6GB is...
March 23, 2012 at 12:36 pm
Lynn Pettis (3/23/2012)
March 23, 2012 at 12:25 pm
Lynn Pettis (3/23/2012)
opc.three (3/23/2012)
March 23, 2012 at 12:14 pm
Is xp_CmdShell enabled on your instance? If so, then you can issue a DOS DIR command on your backup directory and capture the results to a table, and then pick...
March 23, 2012 at 12:00 pm
What I often see are separate databases on the same instance, where the staging database is in simple recovery mode and the data warehouse is in full recovery mode. Procs...
March 23, 2012 at 11:53 am
Anytime! While I could not provide an easy path or complete solution, I am happy to assist 🙂
If you do not mind, if you decide to implement something, whether it...
March 23, 2012 at 11:43 am
March 23, 2012 at 11:14 am
Viewing 15 posts - 4,816 through 4,830 (of 7,168 total)