I have SQL 2005 Enterprise 64bit SP2 on windows 2003 EE 64bit SP2 w/24gig memory. My problem is that it wont use more than 110mb of memory according to task manager processes and performance. I've tried messing with the min and max and rebooting each time I make the change and sill nothing. Currently Ive changed it back to default. The server shows up as 24gig so it is seeing the memory. Any ideas? I thought 64bit was supposed to be better about this kind of thing.
Also, AWE has always been unchecked as this is a 64bit box.
I've been researching AWE to determine if we should enable this for our environment.
Currently we have a quad core box with 4 gb of RAM (VMware). OS: Windows 2003 std, SQL Server 2005 std. 3GB is not set but will be as soon as we can perform maintenance on the server.
I have read mixed feedback on AWE, either it works great or grinds you to a hault. I would assume that the grinding to a hault is due to not setting the min/max values correctly or not enabling the lock page in memory setting.
We only have one instance of SQL on the server and this box won't be used for anything else aside from hosting SQL services. We do plan on running SSRS off of this server as well.
1. Will running SSRS and enabling AWE cause me problems? Will I have to reduce the max setting by the SSRS memory usage or will it share and play nice?
2. How do I go about setting the Max value? Should it be less than the physical RAM in the box? Right now its set to the default of 214748364, even if I don't enable AWE should this default value be changed?
3. It seems that even at idle the SQL server holds a lot of memory and the page file grows. If I restart the process in the morning, memory usage in taskmon is at 600mb or so. By the end of the day, its up around 2gb. How can I track down whats causing this, should this even concern me?
4. The lock Page in memory setting worries me. Everything I've read on this seems to give a warning about serious OS and other program support degradation. In some cases to the point where they have to restore the settings on the server before they can bring it back up. What are your thoughts on this.
I have found that orig tested 64 bit on our 64bit windows 2003server...about 1 year ago...and company decided to use sql 32 bit on the64bit osmy question and any information is very welcomeis there any things in need to know about awe withmemory above 4g ...whilst using 32 bit sql on a 64bit osi want to increase the memory on the server buti really don't know what im up against since this ismixed system 32 bit sql and 64 bit osthanksmike
The upgrade works fine if the instance starts on SP2. But the instance has the hotpatch applied and is running build 3200. When I try the upgrade against the 3200 version it errors out with the following message:
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]The certificate cannot be dropped because one or more entities are either signed or encrypted using it.. To continue, correct the problem, and then run SQL Server Setup again.
My question is: if I upgrade from standard to enterprise on Version: 9.00.3042 it upgrade perfectly well but if I try to upgrade from Version: 9.00.3200 version, it gives the error message.
let me know if anyone can solve the issue at cqldba@gmail.com
I 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 ?
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.
Hello, I understand that we should use SSMS -> Server Properties -> Memory to put a cap on the SQL server memory usage, therefore it gives some space memory for OS, this is based on the fact if the max memory is not specified, SQL will use whatever available memory and eventually crash the system.
My question is that when a server has SSIS and SSAS services installed along with the SQL service. Would the max memory setting covers the SSIS and SSAS memory usage, or the SSIS and SSAS has to shared the memory with OS?
We have SQL Server 2005 Entp 32-bit on Windows Server 2003 Entp.Edtion 64-bit. ( Total memory = 16 Gb)
1) So, in this case , do i need to enable AWE Configuration from SQL Server Side ( 32-bit).
And what settings( AWE, /PAE) i should enable on OS (i.e.) on Windows Server 2003 (64-bit) in boot.ini file. Because right now, i dont see any switches in boot.ini file.
2) And with 16 GB of RAM, what should be the ideal setting for memory ( Min & Max).
We have a new set up on VM to run an application running 24*7 (migrated from SQL server 2008R2) with below configs:
1. OS- Windows server 2012 Standard 64 bit hosted on Virtual Machine
2. Memory 16 GB and Cores =4 with 2.4GhZ processor
3. SQL server 2012 SP2 , 64 bit Standard edition.
4. Total size of databases as of now 15 GB with biggest being 5 GB.
How should i go around in setting the MAX and MIN server memory settings. I have this set up for many of SQL 2005 and 2008R2 servers, but for 2012 i heard that things has slightly changed.Â
How should i start analyzing and setting the right value of this MAX and MIN?
I'm having trouble finding the optimum memory settings for SQL Server 2005. I have 4 instances running on a macine with 8 dual-core processors and 18GB of RAM. I have tried the following memory settings so far:
No maximum - one instance used about 12GB of RAM so then the others struggled Maximum of 4GB each (2GB left for Windows) - meant that 3 instances could be using 1GB each and then another at 4GB and needing more whilst 9GB sat unused. Minimum of 2GB each - one instance would use up 10GB and then never give any back to the other instances.
I also find that setting a maximum then just causes a high amount of paging. What I would like to do is have each instance use a minimum amount, say 1GB, and then have each instance use a maximum of 13GB (3GB for other 3 instances running at a minimum level and 2GB for Windows). This 13GB should then be released and allocated to another instance when necessary, assuming it is no longer all being used. I do not want paging to occur if an instance reaches 13GB.
How do I go about configuring SQL Server to behave like this? Is it possible?
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.
We have a 64bit installation of SQL Server (SSIS, SSAS) running and working fine. There is a requirement to install 64bit SSRS on this existing setup. The problem is: While running the SQL Server Setup wizard, the Reporting Services checkbox remains greyed out. In other words, there isnt an option to select SSRS for installation. So the question is: Is it even possible to install 64bit SSRS on an existing 64bit SQL server installation - given that SSRS wasnt installed during the first pass. PS: The SQL Server is SP2 on a Windows Server 2003 configured as an App Server.
I just installed the 64bit Vista and than wanted to install the 64bit SQL 2005 Std. Server on it.
Note: I downloaded my license from https://licensing.microsoft.com/eLicense/L1033/ProductDetail.Asp?SKU=228-05338.
Installing from SQLSTDSEL.ISO file results in the warning that for the REPORT- Server the .NET version has to be 32bit.
Stopping the installation at this point and try to install from SW CD SQL Svr Standard Edtn 2005 64Bit X64 English #1 x64 MLF.x11-57664 + SW CD SQL Svr Standard Edtn 2005 64Bit X64 English #2 x64 MLF.x11-57665 does not give the above error but on the other hand installs no server at all since somehow the installation routine is not working at all.
Installing now - after at least analysis server and reports server are 64bit and installed - from the first mentioned ISO results in the installation of the DB- Server.... but as a 32bit installation.
Now I wonder what did not work out - so maybe someone here has an idea if and how this problem is solveable.
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
Hello. I have received the follwoing error upon an attempt to Browse the Cube. All other tabs are functional, including the Calculations tab. We are running Windows Server 2003 SP2 and SQL Server 2005 SP2. Any suggestions would be greatly appreciated!
**EDIT** - Have confirmed SP1 for VS2005 is installed both locally and on server, also.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Microsoft Visual Studio)
------------------------------ Program Location:
at Microsoft.Office.Interop.Owc11.PivotView.get_FieldSets() at Microsoft.AnalysisServices.Controls.PivotTableFontAdjustor.TransformFonts(Font font) at Microsoft.AnalysisServices.Browse.CubeBrowser.UpdatePivotTable(Boolean translate) at Microsoft.AnalysisServices.Browse.CubeBrowser.UpdateAll(Boolean translate) at Microsoft.AnalysisServices.Browse.CubeBrowser.InitialUpdate() at Microsoft.AnalysisServices.Browse.CubeBrowser.SupportFunctionWhichCanFail(FunctionWhichCanFail function)
I have a Windows sever 2012 with sql server 2012 enterprise. Ram size is 22GB. Sometimes SQL sever takes 95% memory.My question, How to reduce memory size without killing any process because it's production server.So there are many background process is running. And,Is there any guides to learn why Memory is raise d so high and how to reduce it.
Hello, I understand that we should use SSMS -> Server Properties -> Memory to put a cap on the SQL server memory usage, therefore it gives some space memory for OS, this is based on the fact if the max memory is not specified, SQL will use whatever available memory and eventually crash the system.
My question is that when a server has SSIS and SSAS services installed along with the SQL service. Would the max memory setting covers the SSIS and SSAS memory usage, or the SSIS and SSAS has to shared the memory with OS?
I am running Visual Studio 2005. I have an SSIS Package which is consuming a huge amount of memory. During the execution of the package the memory keeps increasing. Until finally i get an Out of Memory exception. I have run this package using dtexec, and in the BIDS. No difference. I do have some script components and have added some code to get the assemblies in the current appdomain. I do see that one particular assembly is increasing on every loop. VBAssembly every time it hits the script component is increasing by 6, and along with it the memory is climbing. What is this VBAssembly being used for is there an update to SQL Server Integration Services that I need?
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 ??
I've a database with a memory optimized filegroup on it. How can I remove it?I have removed the memory optimized table I had on it, but when I try to remove the filegroup I receive an error.
I have an SQL2005 db residing on a 64bit server.I can load and run my App, provided it is installed on the server.However when I try to run from a Client's PC I get timeout errors.
Initially the error was Remote connections not allowed,but I have overcome this by ensuring SQLbrowser was running and that AllClient and Server Prodtocols were enabled.
I now keep getting a message the timeout has expired.
please tell me what is 32 bit and what is 64 bit databases in sql server? is that based on versions line 7.0 , sql server 2000, yukon and katmai like that or based on creation? please explain me
thank you very much
Vinod Even you learn 1%, Learn it with 100% confidence.
I run SQL Server 2005 on a Windows 2003 64-bit server. I have created a package where I run an execute t-sql statement task. In the t-sql I have the following:
select * from OpenDataSource('Microsoft.Jet.OLEDB.4.0','Data Source="c: est.mdb";User ID=Admin;Password=').pubs.dbo.data
and I get the following error:
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
We have an ASP 2.0 application built using SQL Server 2005, on a 32 bit system. We are going to bring in a much faster server and move the applicatioin to the new server. Since we are moving to a faster server, we are also considering putting a 64bit version of SQL on the new machine and running as 64 bit.
Now the rookie questions: 1) If we do this do we need to do anthing special with our procs/functions, i.e. do we need to recompile everything? 2) From an asp perspective, do we need to do anything to our pages/code? 3) what other issues do we need to be cognizant of?
Hey guy's I am trying to develop something on a 64bit Vista machine. However, the SQL server 2005 import wizard is having a tough time importing my data because this machine does not have IIS.
I tried to install the regular version and it would not let me based on my system.
