Viewing 15 posts - 14,236 through 14,250 (of 49,552 total)
No, nothing to do with virtual servers at all. How SQL allocates and what Task Manager doesn't show
Best way - target and total server memory
February 16, 2013 at 1:04 pm
Don't use Task Manager to check SQL Server's memory usage. It will often display completely incorrect values.
February 16, 2013 at 11:36 am
Run the following, post the full, complete and unedited output
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
February 16, 2013 at 3:32 am
There's no corruption there, so no errors that need fixing.
Service packs are not fixes for database corruption, not that you have any anymore.
February 16, 2013 at 1:12 am
A. A. (2/15/2013)
February 15, 2013 at 3:10 pm
Fragmentation, probably not. Low page density (a side effect of fragmentation), hell yes. Having half of your expensive SSD going to waste because of low page density isn't the greatest...
February 15, 2013 at 2:50 pm
A. A. (2/15/2013)
February 15, 2013 at 2:35 pm
sql-lover (2/15/2013)
GilaMonster (2/15/2013)
It's used for the cluster's IsAlive check. It takes minimal resources. It wasn't there on SQL 2008 or below because it was only introduced in SQL 2012.
Thanks for...
February 15, 2013 at 2:29 pm
Aurelio Alvarez (2/15/2013)
Now to squeeze more money from you, just the OS restricts you to force you to upgrade.
Been that way well before the 32 bit/64 bit changes.
The same...
February 15, 2013 at 2:18 pm
The OS wasn't the limitation in 32-bit days. The addressable memory by a 32-bit process was.
February 15, 2013 at 2:07 pm
It's used for the cluster's IsAlive check. It takes minimal resources. It wasn't there on SQL 2008 or below because it was only introduced in SQL 2012.
February 15, 2013 at 1:58 pm
Nope. To get around 'artificial' memory limitations on Windows Standard edition, upgrade to Enterprise.
p.s. New questions in a new thread in future please.
February 15, 2013 at 1:56 pm
If the repair ran and completed, then the corruption's gone. If you have more problems, some detailed descriptions would be useful.
February 15, 2013 at 11:48 am
tony28 (2/15/2013)
BACKUP LOG and when I wrote command dbcc shrinkdatabase ('Your-Data-Base-Name', TRUNCATEONLY)...
February 15, 2013 at 11:03 am
Why do you want to shrink (make smaller) a log that is complaining it's full (not large enough)? Seems rather counter-productive to try and reduce the size of something that's...
February 15, 2013 at 10:18 am
Viewing 15 posts - 14,236 through 14,250 (of 49,552 total)