April 7, 2011 at 1:29 am
[font="Verdana"]Actually for test environment we have set up SQL Server on a VM.
Memory is proved to be a problem! Otherwise low I/O extensive queries/processes are much efficient than the previous infrastructure.
1. How to make memory extensive operations more smooth or even able to function. (Only single Fixed HD is installed on server).
2. Physical De-fragmentation reported by OS on Data Base drive! How much DISK De-fragmentation and DB performance are correlated.
3. Default OS option for fixed disks "Allow indexing service to index this disk for fast file searching." impacts performance?
Thank you!
[/font]
April 11, 2011 at 12:19 am
[font="Verdana"]Some sign of relief @
http://scottf.wordpress.com/2007/02/09/sql-server-on-vmware-server/
[/font]
April 11, 2011 at 11:14 am
Abrar Ahmad_ (4/11/2011)
[font="Verdana"]Some sign of relief @http://scottf.wordpress.com/2007/02/09/sql-server-on-vmware-server/
[/font]
That link covers VMWare Server which although very good is not a patch on it's big brother ESX server. The two are vastly different as ESX server does not have the overhead of a full blown OS to contend with.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 11, 2011 at 10:11 pm
Perry Whittle (4/11/2011)
Abrar Ahmad_ (4/11/2011)
[font="Verdana"]Some sign of relief @http://scottf.wordpress.com/2007/02/09/sql-server-on-vmware-server/
[/font]
That link covers VMWare Server which although very good is not a patch on it's big brother ESX server. The two are vastly different as ESX server does not have the overhead of a full blown OS to contend with.
[font="Verdana"]
But if any special work around of actual problem, in smart? that was I/O intensive operations on Rich Memory (RAM) and Processors Cores Virtual Machines!
:doze:
[/font]
April 11, 2011 at 10:53 pm
Abrar Ahmad_ (4/11/2011)
Perry Whittle (4/11/2011)
That link covers VMWare Server which although very good is not a patch on it's big brother ESX server. The two are vastly different as ESX server does not have the overhead of a full blown OS to contend with.
[font="Verdana"]
But if any special work around of actual problem, in smart? that was I/O intensive operations on Rich Memory (RAM) and Processors Cores Virtual Machines!
:doze:
[/font]
[font="Verdana"]
If also interested in the following information "sys.dm_os_sys_info"
cpu_ticks180323062759541
ms_ticks67646342
cpu_count4
hyperthread_ratio1
physical_memory_in_bytes8588349440
virtual_memory_in_bytes2147352576
bpool_committed204776
bpool_commit_target204776
bpool_visible204776
stack_size_in_bytes520192
os_quantum4
os_error_mode5
os_priority_class32
max_workers_count256
scheduler_count4
scheduler_total_count7
deadlock_monitor_serial_number13517
sqlserver_start_time_ms_ticks55640
sqlserver_start_time2011-04-11 14:50:29.030
[/font]
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply