January 8, 2010 at 2:45 pm
You should look for how much memory the server has..and if you are facing severe memory issues then it would confirm that you have insufficient memory.
select * from master.dbo.sysperfinfo where counter_name like '%server memory%'
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 8, 2010 at 2:49 pm
Krasavita (1/8/2010)
How to check if I have enough memory on a instanse
It is a process. You need to monitor the servers. Check out this Blog - it should prove useful.
http://blogs.msdn.com/slavao/archive/2005/02/19/376714.aspx
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 8, 2010 at 5:23 pm
Krasavita (1/8/2010)
counter_nameinstance_namecntr_valueTarget Server Memory (KB) 819200
Total Server Memory (KB) 444160 this is one of my instance
If Target Server Memory is consistently larger than Total Server Memory, then SQL wants more memory but can't obtain it. General memory monitoring has to be done per instance of SQL Server.
You need to look at things like Buffer Hit Cache Ratio ( > 90% Data Warehouse or > 95% OLTP), Page Life Expectancy (>300 seconds), Free Pages/sec ( > 600), Lazy Writes/sec ( < 2), Free List Stalls ( should be 0 but occasionally < 2 can be ok). Of course if you have low memory, your disk IO system takes a big hit of the workload because pages constantly have to be flushed and read from disk because the caches aren't large enough to meet the demand.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 8, 2010 at 5:25 pm
The_SQL_DBA (1/8/2010)
type services.msc in start-->run and locate the service name for the instance you want to stop. It should be something like devsvr\sql01, devsvr\sql02.Thanks..
As a matter of practice this method should be retired because it leads people to thinking that they can manage the SQL Services like any other service. The SQL Server Configuation Manager is the best tool for managing the SQL Services, and if someone is in the habit of managing SQL Services through this tool, it isn't likely that they will do something like change the service account through the Services Snap-in which won't setup the appropriate permissions to allow the services to run.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 8, 2010 at 5:28 pm
Krasavita (1/8/2010)
We installed 1 more processor,but it is not showing that we have 2 now,what do we need to do Thank you
Is this a Virtual Machine? I don't know anyone that just has extra RAM and processors just sitting around, so I'd have to guess that this is a VM, which raises a whole other set of problems for running multiple instances. I have run multiple instances on a VM and it is not something I would recommend to even my worst enemy unless you really know what you are doing when you configure the VM as well as configure SQL.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 8, 2010 at 5:37 pm
Why did you have 10 instances ? Is there a business requirement for separate Instances ?
How many instances are active now ?
Can you combine databases onto the same instance so you have less instances ?
So instead of:
Instance_1
DatabaseA
DatabaseB
DatabaseC
Instance_2
Database1
Database2
Database3
You make:
Instance_1
DatabaseA
DatabaseB
DatabaseC
Database1
Database2
Database3
January 12, 2010 at 11:22 am
counter_nameinstance_namecntr_value
Target Server Memory (KB) 819200
Total Server Memory (KB) 819200
Target and Server are equal is this consider ok
Buffer CountsBuffers
Committed102400
Target102400
Hashed43268
Stolen Potential53512
External Reservation0
Min Free32
Visible102400
Available Paging File304972
January 12, 2010 at 12:10 pm
Buffer CountsBuffers
Committed102400
Target102400
Hashed43268
Stolen Potential53512
External Reservation0
Min Free32
Visible102400
Available Paging File304972
January 12, 2010 at 12:49 pm
Krasavita (1/12/2010)
counter_nameinstance_namecntr_valueTarget Server Memory (KB) 819200
Total Server Memory (KB) 819200
Target and Server are equal is this consider ok
It is a general sign that memory utilization is stable at the moment for the instance, but it doesn't mean that the instance isn't in memory pressure. You'd have to look at all the other memory counters I mentioned to know that for certain.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 13, 2010 at 9:43 am
Thank you, we are still having problems and I need your help please
with this instanse
counter_nameinstance_namecntr_value
Target Server Memory (KB) 1024000
Total Server Memory (KB) 819200
Buffer CountsBuffers
Committed102400
Target128000
Hashed70359
Stolen Potential116210
External Reservation0
Min Free32
Visible128000
Available Paging File302036
January 13, 2010 at 9:58 am
my AWE is not check, in my case should I check it to true?
Viewing 11 posts - 46 through 55 (of 55 total)
You must be logged in to reply to this topic. Login to reply