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 RepliesOk Here is the story with hopefully all the details.
I had a single node cluster Itanium server running W2k3 IA 64 Ent. SP2 with 2 x sql2000 ent sp4 and 1 sql2005 sp1 instances installed and a clustered file share.
All is well with them.
I attempted to add an additional node to my cluster which started out fine but when I tried to run the sql2000 setup to add this node, there are no warning or errors. Its a silent failure.
I tried many different scenarios but the results are the same. I evicted the node and then tried to run the setup on the evicted node. The setup ran without error. I tried to run setup on my single node cluster and it fails in the same manner. I read and read and from the sqlstp.log this is what I find. Does anyone have a clue what is wrong? i have check all my permissions but I can't put my finger on what it could be.Help Help.
1
<Func Name='InitDataFolder'
<EndFunc Name='InitDataFolder' Return='0' GetLastError='18'>
<Func Name='DetectComputers'>
1
<Func Name='DetectVersionOnMachine'>
NYCTDB04 D:SQL Server ENT 2000 - 64 BitSetupIA64inn 1
<Func Name='InsertVersionRecord'>
NYCTDB04 MSSQLSERVER 0 8.00.760 1033 0 3 1804890536 Enterprise Edition (64-bit) 2099209 1 NYCTDB41 0 1
<EndFunc Name='InsertVersionRecord' Return='0' GetLastError='183'>
<Func Name='InsertVersionRecord'>
NYCTDB04 BIZTALK 1 9.00.2047.00 1033 0 -1 -1 (64-bit) 133124 0 0 1
<EndFunc Name='InsertVersionRecord' Return='0' GetLastError='183'>
<Func Name='InsertVersionRecord'>
NYCTDB04 MYOFFICE 2 8.00.760 1033 0 3 1804890536 Enterprise Edition (64-bit) 2230280 1 NYCTDB42 0 1
<EndFunc Name='InsertVersionRecord' Return='0' GetLastError='183'>
<Func Name='InsertVersionRecord'>
NYCTDB04 SHARED_TEMP 3 8.00.760 1033 0 3 1804890536 Enterprise Edition (64-bit) 2230276 0 0 1
<EndFunc Name='InsertVersionRecord' Return='0' GetLastError='183'>
<EndFunc Name='DetectVersionOnMachine' Return='0' GetLastError='183'>
<Func Name='InsertComputerNameRecord'>
NYCTDB04 0 50010 539101189
<EndFunc Name='InsertComputerNameRecord' Return='0' GetLastError='183'>
<EndFunc Name='DetectComputers' Return='0' GetLastError='0'>
<Func Name='DetectIpResources'>
<Func Name='InsertIpResourceRecord'>
_sql$IpResources 0 144.210.119.64 255.255.255.224 Public
<EndFunc Name='InsertIpResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='DetectIpResources' Return='0' GetLastError='183'>
<Func Name='DetectGroupResources'>
<Func Name='EnumerateGroupResources'>
SQL 2000 Shared Group(NYCTDB41) NYCTDB04 Disk Q: 0
<Func Name='GetDiskResourceLetters'>
SQL 2000 Shared Group(NYCTDB41) Disk V 0
<Func Name='InsertDiskResourceRecord'>
Disk V 0 V SQL 2000 Shared Group(NYCTDB41)
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='GetDiskResourceLetters'>
SQL 2000 Shared Group(NYCTDB41) Disk W 1
<Func Name='InsertDiskResourceRecord'>
Disk W 1 W SQL 2000 Shared Group(NYCTDB41)
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='GetVSInfo'>
SQL 2000 Shared Group(NYCTDB41) NYCTDB04 0
<Func Name='EnumVSIPResources'>
NYCTDB41
<Func Name='InsertIpResourceRecord'>
NYCTDB41 0 144.210.119.88 255.255.255.224 Public
<EndFunc Name='InsertIpResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumVSIPResources' Return='0' GetLastError='183'>
<Func Name='EnumVSResourceOwners'>
NYCTDB41
<Func Name='InsertVSNodeInfoRecord'>
NYCTDB41 NYCTDB04
<EndFunc Name='InsertVSNodeInfoRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumVSResourceOwners' Return='0' GetLastError='183'>
<Func Name='InsertVSInfoRecord'>
SQL 2000 Shared Group(NYCTDB41) 0 NYCTDB41 MSSQLSERVER 1 D:Program FilesMicrosoft SQL Server V:Program FilesMicrosoft SQL Server ipgnasharedsql.service ipgnasharedsql.service
<EndFunc Name='InsertVSInfoRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetVSInfo' Return='0' GetLastError='183'>
<Func Name='InsertGroupResourceRecord'>
SQL 2000 Shared Group(NYCTDB41) 0 0 NYCTDB04
<EndFunc Name='InsertGroupResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumerateGroupResources' Return='0' GetLastError='183'>
<Func Name='EnumerateGroupResources'>
Cluster Group NYCTDB04 Disk Q: 1
<Func Name='GetDiskResourceLetters'>
Cluster Group Disk Q: 0
<Func Name='InsertDiskResourceRecord'>
Disk Q: 0 Q Cluster Group
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='InsertGroupResourceRecord'>
Cluster Group 1 1 NYCTDB04
<EndFunc Name='InsertGroupResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumerateGroupResources' Return='0' GetLastError='183'>
<Func Name='EnumerateGroupResources'>
SQL 2005 Biztalk Group(NYCTDB40) NYCTDB04 Disk Q: 2
<Func Name='GetDiskResourceLetters'>
SQL 2005 Biztalk Group(NYCTDB40) Disk T 0
<Func Name='InsertDiskResourceRecord'>
Disk T 0 T SQL 2005 Biztalk Group(NYCTDB40)
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='GetDiskResourceLetters'>
SQL 2005 Biztalk Group(NYCTDB40) Disk U 1
<Func Name='InsertDiskResourceRecord'>
Disk U 1 U SQL 2005 Biztalk Group(NYCTDB40)
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='GetVSInfo'>
SQL 2005 Biztalk Group(NYCTDB40) NYCTDB04 2
<Func Name='EnumVSIPResources'>
NYCTDB40
<Func Name='InsertIpResourceRecord'>
NYCTDB40 0 144.210.119.90 255.255.255.224 Public
<EndFunc Name='InsertIpResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumVSIPResources' Return='0' GetLastError='183'>
<Func Name='EnumVSResourceOwners'>
NYCTDB40
<Func Name='InsertVSNodeInfoRecord'>
NYCTDB40 NYCTDB04
<EndFunc Name='InsertVSNodeInfoRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumVSResourceOwners' Return='0' GetLastError='183'>
<EndFunc Name='GetVSInfo' Return='1168' GetLastError='203'>
<EndFunc Name='EnumerateGroupResources' Return='1168' GetLastError='183'>
<EndFunc Name='DetectGroupResources' Return='1168' GetLastError='183'>
<EndFunc Name='PerformDetections' Return='1168' GetLastError='0'>
We 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 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.
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.
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.
My Desktop OS is Windows XP Prof. Edition with SP2.
Which executable(X84 / X64 / IA64 ) is compatible with XP Pro SP2 ?
I have a 32 bit development/playbox SQL 2005 SSIS that can see and run 32 bit OLE DB drivers from Teradata. Granted I have the same issues as others where a table or a view would work and not a query or a variable query. The alternative is to use Linked Server and OPENQUERY.
But our real development box is a 64 bit IA 64 using 64 bit SQL 2005. Non of the Teradata.com drivers would work/show up in the dropdown box of the Connection Manager since they are 32 bit. One option is to use the 64 bit Teradata ODBC drivers and then use the .Net ODBC connection instead. Linked server doesn't work either because the SQL 2005 is 64 bit and it is looking for 64 bit drivers.
Has anyone have any experience with 64 bit SQL 2005 and Teradata?
Looked at other 3rd party vendors such as ETI but their documentation excludes IA 64 (Itanium).
Planning to try again using the 64 bit ODBC and .Net Adapter but I'm interested to hear if someone (MSFT & NCR) would have a real solution for 64 bit.
Thanks
Anatole
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?
Dear all
I am running Itanium server 64Bit on cluster Mode with Sql Server 2000 Sp4 64 BIT ia version ported.
the itanimum has a 8gb of ram and 4 Processors.
it has one instance and 3 databases.
users connected about 200 Users.
But the processor load is going about 100% in itanium where in xeon about 30% only on the same databses
The database i copied from Xeon based server and ported on the itaminum server.
In normal Xeon server takes 2 Minutes for indexing . In itanimum it is taking more than 4 Hours for the same table.
Is any one can help with what sort of SP_configure script is advisible and best practices for itanumum server.
Plesae give me some best practices
thanks in advances
regards
Tamilvel
tamilve
IT head
Hi, I have the option of buying MS SQL Server 2005 Standard Edition IA64 with 5 CLT part number 228-04025, however will it work on the following spec server;
2.8Ghz P4
1Gb Ram
120Gbide hard drive
running Windows 2003 standard edition
If it helps you can call me on +44 (0) 1285 644091 or simon@310k.co.uk
Thanks
Simon
We've run into an issue running against the SQL Native Client ODBC driver (version 2005.90.2047.0) on Windows 2003 Server (Itanium). The "INFO: ODBC 64-Bit API Changes in MDAC 2.7" article (http://support.microsoft.com/kb/298678) doesn't say that the returned value for SQL_ATTR_CONCURRENCY changed to a 64-bit value, but if you request this attribute from the SQL Native Client driver, a 64-bit value is returned. The ODBC spec still indicates that SQL_ATTR_CONCURRENCY is a SQLUINTEGER value, which is 32-bit, even on a 64-bit platform.
This is easy to see by using the ODBC Test utility in the Windows SDK for ia64, "C:Program FilesMicrosoft SDKBinWin64ia64odbcte32.exe". If you connect to the SQL Server driver and then simply call SQLGetStmtAttr(SQL_ATTR_CONCURRENCY), you'll see that the *StringLengthPtr argument returns 8 bytes, when it should only return 4.
Note that we've also seen the same behavior with SQL_ATTR_ROW_BIND_TYPE as well as other statement attributes defined to return SQLUINTEGER values.
Has anyone else run into this?
Thanks,
Chris
Just an FYI for those scheduling SSIS packages on 64bit Itaniums.
This came to light when using a 32 bit OLEDB driver on a 64bit Itanium.
When manually executing the package on the server through SQL Management
Studio, we got the expected results. However, when we scheduled the
package as a job, it failed every time. The error was:
"The AcquireConnection method call to the connection manager 'ConnectionName' failed with error code 0xC0202009€?.
We tried everything to fix this, but nothing worked. Finally we found
that when manually running the package, SQL Management Studio was calling the
32bit version of dtexec.exe, while the Agent calls the 64bit version of
dtexec.exe. The fix is to not use the "SQL Server Integration
Services Package" type in the job step, but use "Operating system
(CmdExec)" type. Then in the command box, call the 32bit (x86)
version of dtexec.exe.
Example:
C:Program Files (x86)Microsoft SQL Server90DTSBinnDTExec.exe /DTS
"File SystemSSIS Packages[PackageName]" /SERVER [SQLSERVERNAME]
/DECRYPT [password] /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/REPORTING V
Hi,
I want to install SQL server 2005 trial version from Microsoft, How do I know which excecutable to tale from these below?
Self-extracting executables:
X86 Executable
X64 Executable
IA64 Executable
Thanks
Dear,
I have application create by MsAccess
and connect with Sql Server 2000 in x86
and now we transfer system to
HP rx3600 Intel Itanium
- Install Windows 2003 Server Enterprise (for Itanium)
- Install Sql Server 2005 Standard Edition (IA64)
and now we try to create ODBC connection
from client for testing.
But we can't not done it.
Anybody can tell us
how to create connection to sqlserver 2005 (ia64)
Regards,
Tee+
Hi, pls can anyone help me out with this? I'm installing SQL2005 SP2 over an Itanium machine with W2003 SP2 but it keeps on failing on those features. Client components got installed with no problems. I've installed SQL2005-SP2 over x86 and x64 (not Itanium) machines many times before successfuly. I've been investigating this issue for several days with no luck so I'm a bit clueless at the moment. As I'm using Administrator account I think it is not file permission related.
Summary says "Unable to install Windows Installer MSP file".
let me know if further info is nedeed.
Many thanks.
During the installation of Adding node to a SQL Server failover cluster(On passive node) getting error like.. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.We  run the below commands but didn’t get any resolution & got the same above error .
Â
1<sup>st</sup> Method…
1. Open console command (Run->CMD with administrator privileges).Â
2. net stop winmgmtÂ
3. Rename folder %windir%System32WbemRepository to other one, for backup purposes (for example _Repository).Â
4. net start winmgmt
2<sup>nd</sup>Â Method..
1. Disable and stop the WMI service.
a) Command : - sc config winmgmt start= disabled
b. Command : - Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â net stop winmgmt
2. Run the following commands.
a). Command: Winmgmt /salvagerepository %windir%System32wbem
b). Command: Â Winmgmt /resetrepository %windir%System32wbem
3. Re-enable the WMI service
Command:Â Â Â Â Â Â Â Â Â sc config winmgmt start= autoÂ
Last command to run after above steps
4. Command:Â Â Â Â mofcomp "%programfiles(x86)%Microsoft SQL Server100Sharedsqlmgmproviderxpsp2up.mof"
File not found Error for above command.
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2
Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid.
Msg 3156, Level 16, State 50, Line 2
File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file.
Msg 3119, Level 16, State 1, Line 2
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
I ran the Advanced cluster preparation for a new sql instance on an existing cluster.
Slq Server 2012.
After is completed, it was successful, I realized I specified the wrong Instance Root directory.
Is it possible to remove what the preparation installed? Or is it possible to change the root directory?
Can I build a cluster by adding the cluster service, then the SQL instances, then add the other nodes and their passive SQL instances?I would lean to building the cluster first, the add the SQL instances.
View 4 Replies View RelatedI am looking to test this feature - and the "Transaction Performance Collector" has recommended me a table to port to In-Memory OLTP.Â
I have now tried the "Table Memory Optimization Advisor" tool.
After a couple of tweaks to the table design - the tool is now passing validation but the tool is not allowing to progress to the next step:
Could it be down to not having enough memory? But would this not show in the advisor?
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 RelatedI have following script which i am planning to run to drop all non-clustered primary keys on a database and then created as clustered. I am using someone else's script so don't know how to modify this. Some of primary key columns are used in references in other tables.
is there anyway i can drop the existing primary keys and using their original script then create again as clustered including restoring all foreign and reference keys and unique or no unique.
DECLARE @table NVARCHAR(512), @tablename NVARCHAR(512),
@sql NVARCHAR(MAX), @sql2 NVARCHAR(MAX), @sql3 NVARCHAR(MAX),
@column NVARCHAR(MAX);
DECLARE @indexname NVARCHAR(512);
SELECT name As 'Table'
[Code] ....
can we join a node in a windows cluster which is already in a different cluster?
We have this requirement as we need to setup readable secondary ( always on AG) on the third node.
We are planning to change all IPs of PRODUCTION Failover Cluster Setup. In my cluster setup ... we have 2 Physical Nodes with windows-2008, Roles are MSDTC and SQL-2008R2.
IP change for:
1. Both Nodes(Physical)
2. MSDTC
3. SQL ServerÂ
4. windows ClusterÂ
So Almost... All IPs are going to change.
Im DBA here, I need to take care of SQL cluster and MSDTC. But I haven't performed this activity before.So I'm worrying about Impacts and consequences of this change. steps how should I perform this activity.
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'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 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.
View 10 Replies View Related