Memory Recommendations For Cluster Sql Server
Jun 20, 2006We have a win2003 cluster with sql 2000 with 16 gig of memory. Should you leave more memory for the OS versus if this was a stand-alone server
View 3 RepliesWe have a win2003 cluster with sql 2000 with 16 gig of memory. Should you leave more memory for the OS versus if this was a stand-alone server
View 3 RepliesI want to build a SQL testing environment in an active/active setup. Any recommendations on what I could use if I want to set up the most bare-bones system. I want to do it as cheaply as possible.
Thanks
On first Node A: The server has 16 GB of physical RAM.
On second Node B: The server has 10 GB of physical RAM.
Now, this being Active Active, Node A can be clustered on failure onto Node B..Now reporting server is configured under these two nodes, with defined MAX and MIN server memory of 12 as MAX and 0 is min IN GB.Now with this setting on SQL whenever the cluster moves, such config make OS goes low on node for 10 GB.I am only left with option of switching this MAX and MIN to a default setting or is there any other alternative such as script which can change this setting accordingly when cluster moves to respective server.
I have the following SQL FCI configuration:
NODE1 -256GB
INST1 - 64GB min/64GB max
INST2 - 64GB min/64GB max
NODE2 - 256GB
INST3- 64GB min/64GB max
INST4- 64GB min/64GB max
With this configuration and if all instances are running on the same node there will be enough memory for them to run. Knowing that normally i ll have only 2 instances in each node wouldnt it be better the following config?
NODE1 -256GB
INST1 - 64GB min/128GB max
INST2 - 64GB min/128GB max
NODE2 - 256GB
INST3- 64GB min/128GB max
INST4- 64GB min/128GB max
With this configuration and in case all the instances (due to a failure) start running on only 1 node, SQL will adjust all instances to just use Min memory specified?
I have Two Dell dual Itanium 64 with 16 Gb of Ram each Running a default and a named instance of SQL. The Issue is that I have a bottleneck somewhere and noticed that the memory usage for sqlservr.exe is never over 120000k. I have adjusted till I'm blue in the face to get this memory to expand. My question is does this sound reasonable? Or I should look at other possible bottlenecks?
View 1 Replies View RelatedI have an Active/Active/Passive cluster with 64GB RAM on each node running SQL 2000 EE, AWE is enabled as well as the PAE switch, all is dandy with that.
Question:
Should I configure each SQL Instance to have only a max mem usage of 32GB in the event both failover to the same node ? or will the memory allocation be handled without any issue if each node is configured to use 64GB ?
Thanks.
So I'm in the middle of building SQL Server 2005 on my new cluster hardware. I've got all the goodies this time around -4x PowerEdge 68004x dual core x64 procs in each box32GB ram in each boxWindows Server 2k3 R2 Enterprise x64 SP2SQL 2005 Enterprise x64 SP2Active Active Active Passive cluster (4 boxes, 3 instances)dedicated data, log, and tempDB 4Gb 15k fiber channel SAN Volumes for each instanceNow, this is the first x64 box I've configured, so I'm looking for some optimization tips for a couple things.First one's memory. On our 32bit systems, I always added the /PAE switch to the boot.ini file and enable AWE in SQL Server. From what I'm reading, that's no longer needed with the enhanced memory addressing. Is that the case? Is there an MS best practices KB doc in regards to configuration? I can't find one.Also, should I set anything special pagefile-wise? I know the old mantra is 1.5x system memory, but that would create a 48GB page file. Our current cluster has 6GB of ram dedicated to each instance (2k) and Perfmon tells me it's barely touching the pagefile. I'm thinking of just leaving it default, but I want to know if there is a best practice that I'm missing. Again, I can't find an MS doc that addresses this particular scenario.
View 14 Replies View RelatedDear all,i am planing to implement a Windows 2003 Cluster with MS SQl 2000Enterprise Edition. I have 2 Nodes (4 * XEON MP Processors) with 8 GBRAM per Node.I have the need for 6 SQL instances and would like to implement aactive-active cluster. What do you think it the best way to configurethe memory for the Servers ?I would like to run 3 instanced per Node but can i allocate 7 GB perNode for SQL (and 1 for the Operating System) ?What is happening then i one server fails ?Should i plan to allocate only 3 GB per Server for SQL to make surethat one server can handle the load for all instances if one serverfails ?Should i use the /AWE switch only in the boot.ini to allow more than 4GB Memory ?or should i use the /3 GB switch as well ?Maybe somebody can give me a hint.Best regards,Walter
View 1 Replies View RelatedWe recently did an in-place upgrade of our cluster from SQL 2000 Enterprise to 2005 Enterprise. We are seeing memory utilization on the server that is not expected and wanted to get an idea from others if this is normal. Here is our setup:
32-bit Windows Server 2003 SP1
SQL 2005 SP2, 2-node cluster
16 GB memory on each node
/3GB /PAE switches in the boot.ini file
AWE Enabled, min memory=0, max memory=14000
The strange bit is that in the Task Manager the SQL service is showing as only using 205 MB of memory and the pagefile usage is at 13 GB. This is troublesome since it looks like SQL is using virtual memory instead of physical memory. We recently upgraded the memory from 4 GB to 16 GB, the sql cluster service account was added to the Lock Pages in Memory policy, the boot.ini switches were set and the AWE enabled/max_server_memory script was run before upgrading to 2005. Can anyone confirm either 1) this is normal or 2) how to correct the memory usage?
I have also questioned using the /3GB switch; would it be better to remove that and set the max memory for SQL to 12000?
Any help would be greatly appreciated. If I left off any information that would be helpful, please let me know.
Chris
We are running with a 2 node windows cluster having three SQL instances on it.
OS: Windows server 2008R2 SP1
SQL : SQL server 2008R2 (10.50.6529)
Currently both nodes have 256 GB or memory and we are having multiple auto failover for resources. What will be the best practice for OS memory reservation (OS+tools) so that we can set SQL max memory settings accordingly?
I am looking for some recommendations for memory sizing and options for a SQL 2000 Cluster. This is a two node cluster built on Windows 2003 ENT SP1 (x86). Both the nodes have the following hardware:
- 4 x Dual Core AMD Processors
- 16 GB Memory
- EMC Shared Disk
We are running six SQL 2000 instances and don't expect each of these instances to use more than 1.7 GB of memory. All these instances are going to support BizTalk 2004 Databases. I already have /PAE enabled on the nodes. I am looking for the following answers:
- Do I need to enable AWE on all the instances even if the instances ? Currently, we don't have that enabled and we have seen some issues regarding excessive paging even when there is physical memory available. The DBAs think that we don't need to enable AWE. I am bit confused on this one.
- We normally run 3 instances on each node and would like size the cluster in such a way that it can take six instances in case of a node failure
Any input will be highly appreciated.
Could someone give me an ideal of what it takes to upgrade the memory in my cluster. Is it as easy has upgrading the passive node, switching the nodes, then upgrading the other server. And do I need to re-configure the windows cluster. And will both server need to be down at the same time at any point.
Or is their more to the process? Thanks for any assistance.
btw, I currently have 16mb of RAM in each node.
I'm on the IS team of a medium-sized non-profit with internationalreach. We're trying to make some decisions regarding our Web serverand database server as we expand our web site to have more dynamiccontent. Currently the database server houses all data pertinent tothe organization (membership data, events, products, etc) in onedatabase (~2.2 GB) as well as the web site content in a separatedatabase (~40 MB). The web site pulls from both databases but hits thecontent database more often.In a nutshell, our database server appears to be struggling duringperformance testing of the new Web site. We are trying to determinewhether we simply need new hardware, or if there are things we can doto help MS SQL make better use of the resources we have. The hardwareis a COMPAQ ML370, 1266mhz Pentium III, 1gb RAM, RAID 5 with 3 HD(10,000rpm) and a COMPAQ Smart Array 5i SCSI controller. The OS isWindows 2000 (standard) running Microsoft SQL 2000, SP 3a. The Webserver is a 2.8ghz Pentium IV with 2.5gb RAM, RAID 5 with 3 HD (15,000rpm) running Windows 2000 standard and IIS 5.0. While stress testingour web site under a moderate load (simulating approximately 20simultaneous users), the database server processor tends to max outand stay that way for the duration of the test. Memory and disk accessappear to remain fairly stable -- there isn't a lot of paging goingon, and the disk queue doesn't escalate much if any. The Web servershows spikes in processor use, but appears to be coping well. However,under a heavy load, a sql-heavy page can take as long as 90 seconds toload! We've been assuming that the network is not the issue, as theservers are communicating over a gigibit backbone and while we'veidentified aspects of the ASP code that we can optimize, the databaseserver seems to be a large part of the problem.We've reviewed our SQL configuration settings, and they appear toalign with the best practices, which in our case are the defaultsettings for SQL 2000. We have rebuilt our indexes, and havedefragmented the hard disks on both the database and Web servers.This, along with changes to the structure of the Web pages themselves,has led to improvements, but the processor on the database serverseems to be groaning under the strain, and pages are still taking anunacceptable amount of time to load.What else should we be looking at? Are there steps we could take tominimize the load generated by client/server and Web-related traffic,or specific performance counters that would help us to identify theproblem? Do we just need to look at getting some new hardware? If newhardware is unavoidable, is there anyone running a similar environmentwho could suggest what minimum requirements we should be looking for?Any suggestions would be much appreciated!
View 5 Replies View RelatedWe're planning to migrate our db to new and more disk drives, fasterRAID levels and more dedicated disk usage(e.g. placing the translog ondedicated disks). The db server runs on Win2003.Right now we're thinking about what file system to use on the newdrives. We opt for performance, but expect reliability as well.(Goeswithout saying, IMHO ;-))
Quote:
We're having issues with Microsoft's 64 bit Oracle OLE-DB driver... when we escalated to Microsoft PSS they recommended that we go with Oracle's OLE-DB driver since Microsoft's hasn't been modified in a few years.
I've seen a lot of differing opinions on this topic (almost everyone says do not use Oracle's driver) and am wondering if there's a definitive answer here.
Larry
We have an NT 4.0 sp4 server with Sql 6.5, sp4 and its server name needs to be changed. This server will also be upgraded to Sql 7.0 sp1 too.
Is changing the server name easier/more efficient etc in 65 or 70?
Does anyone have any recommendations and or tips to follow in avoiding pitfalls, headaches etc?
Additional info: Replication is not involved here. If we upgrade to 70 first, it will be a "One-computer upgrade" process followed. BOL for 70 doesn't mention anything about a Server Name change. BOL for 65 does have "How to change to the current server name in the 6.x master database..." I was hoping to find specific details on the 'how to...' but was surprised that 70 doesn't cover this.
I have also seen a Jan 15 '99 posting by Sharon Dooley under "Machine Rename" which raises concerns that MS missed the boat on Server Name changes.
Any help would be appreciated.
Thank you,
TW
Hi
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
Thanks
Priyanka
What up-to-date books on this topic can people here recommend? Thanks.- Bob
View 1 Replies View RelatedHi
I did a load testing and found the following observations:
1. The Memory:Pages/sec was crossing the limit beyond 20.
2. The Target Server Memory was always greater than Total Server Memory
Seeing the above data it seems to be memory pressure. But I found that AvailableMemory was always above 200 MB. Also Buffer Cache HitRatio was close to 99.99. What could be the reason for the above behavior?
I´ve been reading that SQL Server 2012 Always On is dependent on having a Windows Failover Cluster setup. Is that correct ?
View 6 Replies View Related
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Thoughts?
Friends -
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
Please advise me and correct my steps.
Cheers
VSH
sql server 2000 is running on windows server 2003 ... 4gb of memory on server .... 2003 was allocated 2.3gb nd sql server was allocated (and using all of it) 1.6gb for total of approx 4gb based on idera monitor software ... all memory allocated betweeen the OS and sql server .... then 4 more gb of memory added for total now of 8g ... now idera monitor shows 1.7gb for OS and 1.0 gb for sql server ..... 'system' info shows 8gb memory with PAE ... so I assume that the full 8gb can now be addressed .... why are less resources being used now with more total memory .... especially sql server ..... i thought about specifying a minimum memmry for sql server but i amnot convinced that would even work since it seems that this 1gb limit is artificial .... it it used 1.6 gb before why would it not use at least that much now ??
thank you
I am trying to upgrade a SQL Server 6.5(Cluster) to SQL Serevr 7.0 (Cluster)..I already have an intsllation of 7.0(On a Cluster),so this means that 6.5 and sql 7 are on seperate cluster's ,if i try to upgrade from 6.5 Cluster to 7.0 Cluster is asks me to uncluster 6.5 and 7.0 is this correct ,assume i cannot break the cluster then what???.. what is the best way i can achieve this functinality.....
thanks in advance
Jack
Friends -
Could any one of you provide steps for upgrading SQL Server 2000 cluster to SQL server 2005 cluster.
My environment is Windows 2003 server.
Appreciate your support.
Cheers
VSH
Hi
I've got a SQL database running on Windows NT 4 Server (P400, 256 Ram, 8Gb IDE & 18Gb SCSI HDD) and quite a few of the queries are taking a long time to run, and are also using a lot of the processor time. This affects other users who are also trying to query the db. Has anyone got any recommendations for upgrading the hardware spec to improve the overall performance? I presume just add more RAM, and get a dual processor system?
Thanks
Ben
I am a PHP programmer for a small startup. We are storing person records and our MS SQL Server 2000 database has grown to the point where we wish to paginate the data before returning it to my PHP scripts.
I was wondering if anyone has any recommendations on an optimal way to manage this given the following requirements.
- Data must return only X number of rows at a time (user configurable).
- Must be able to search by several diffent criteria (name, date, birthday, location, ...)
Also, I was wondering if it is possible to return the total number of existant rows of data as the first row of a MSSQL procedure.
I have a SQL 2005 database containing the location of graphics files. I want to start learning how to write a C# application that will get a path from the DB and display the file. Any recommendations on sites where I can start learning how to do this?
Thanks
Ok, let me start by saying that I already checked the FAQ. There was one link, but it just seemed to go to a review page with 5 books, with pretty specific themes. So I'm surprised that such a basic topic as book recommendations for SQL newbies wasn't covered.
In my case, I'm not a total newbie. I learned to write SQL queries for work on both Oracle and SQL Server, and I've gotten pretty good at all the basics. So I've got "SQL for Dummies" down cold, so to speak. Now I'm looking to take my query writing ability to the next level, which I guess would be the intermediate level. I'm also looking for books that are specific to just SQL Server, rather than the books about general querying on any DBMS. Speaking of which, just so you all know, "SAMS Teach Yourself SQL in 21 Days" is an Oracle book, no matter what it says on the cover.
It looks like the book "Inside Microsoft SQL Server 2005: T-SQL Querying" comes highly recommended, but I flipped through it on the shelf at a bookstore the other day, and I think it's over my head. It might be a good reference to have around, but I think I'd be totally lost trying to read it from cover to cover.
So does anyone have recommendations for books that go beyond "This is how to do a SELECT, and here's how to do a JOIN", but won't make my head explode?
Thanks in advance,
--Fromper
I do software support for software that works with both Oracle and SQLServer, so I mostly just write queries to look at the data related tothe software. When I first started, I bought a couple of books to learnthe basics, intentionally going with generic books that would help withboth types of databases. I've got the basics down, and now I'm lookingfor a really detailed reference book that goes really indepth intoquerying for SQL Server specifically. Currently, we only work with the2000 version, but we'll be going to 2005 soon, so I think I'd rather gowith a book on 2005, although if you know one that covers thedifferences between them, that would be great. Any recommendations?Besides just writing queries, I'd also like to learn more about SQLServer in general. DBA software support, so I'd like to head mycareer in that direction. I was looking at Microsoft's newcertification path for SQL 2005. Given that my company won't pay tosend me for training, and I really don't want to have to put down$2200+ to pay for a class, I was thinking that I might be able to learnenough on my own to pass the first test and get the MCTS title. Iordered the Training Kit from Microsoft Press for that, which comeswith a 180 day trial of SQL Server 2005 to play with, along with a hugebook. Does anyone have any other recommendations for resources to helplearn this stuff?--Richard
View 4 Replies View RelatedHello -Anyone have any thoughts on which API to use - ADO or ODBC?I have a fat client written in C++ using MFC ODBC classes to access a Jetdatabase.The app is going to be modified to write to a SQL Server central databasewith multiple users accessing their local copies of the database ( usingreplication technology on the clients side).Most of the performance benchmarks give an edge to ODBC over ADO whenwriting to an Access database. Anyone know of any benchmarks for a c/senvironment?I've seen references that ADO has some client side cursor features forfilters and sorting which are a benefit over ODBC. I'd also like to usethe asynchronous fetch that OLE DB provides and am not sure if this isimplemented in ODBC.Thanks for the help.Bruce
View 1 Replies View RelatedHi all,
I've recently been tasked with doing some SQL 7.0 administration and was wondering if anyone could recommend a good book to get started. The bulk of my IT experience is in SMS, IIS and messaging so my database fundamentals are pretty weak.
As I see it, it's probably a three-step process to get me at least halfway comfortable - a first book to get some solid general database / SQL-language exposure, a second book that takes the knowledge to a more advanced level and finally a MS-specific book that covers the Microsoft implementation of a SQL server.
Any comments / suggestions would be much appreciated!
Cheers,
RM
I've searched quite a bit, and have found several leads on schema, stored procedure, and database contents comparison scripts and tools.
I'm now looking for recommendations on which ones are best, easiest:
ObjCompare.exe
sb_ABCompareDb.sql
sp_db_comp.sql
There's a mythical script from Andrew Z <mumble> that Mike Hotek talks about...
There's a DBCompare on the Back Office Resource Kit 2 CD, which of course is not in the umpteen MSDN CDs :-(
There's some *other* command line dbcompare, or maybe db_compare.
There's a DBA Compare.
I need to be able to compare divergent schemas from two developers to integrate their changes, so need schema and stored procedures compared only, and would also like to have something to compare staging servers and production servers.
Leads on other choices also welcome. I'd be happy to summarize and post, if warranted.