.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Distributed shared memory and sql server?

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :


Not sure this is the right forum but, I'll give it a shot anyway;

Recently I've been into discusions about distributed shared memory to hold a synchronised copy of database in memory in order to remove load from dB.

There're a lot of opensource / solution about this mainly for the linux world as I can see it. (http://en.wikipedia.org/wiki/Distributed_shared_memory)

Just curious to know what the microsoft approch to this architecture is.



View Complete Post

More Related Resource Links

[Microsoft][SQL Server Native Client 10.0]Shared Memory Provider: Timeout error [258]


Hello All,

I am using MS SQL SERVER 2008. Im making an application which queries trillion of records. Im using PHP as scripting language. For those functions , which query database and 200 (approximately) rows of DB are returned, everything works fine. But if I query database and a large recordset should be returned, the following error is thrown:

Array ( [0] => Array ( [0] => 08S01 [SQLSTATE] => 08S01 [1] => 258

=> 258 [2] => [Microsoft][SQL Server Native Client 10.0]Shared Memory Provider: Timeout error [258]. [message] => [Microsoft][SQL Server Native Client 10.0]Shared Memory Provider: Timeout error [258]. ) [1] => Array ( [0] => 08S01 [SQLSTATE] => 08S01 [1] => 258
=> 258 [2] => [Microsoft][SQL Server Native Client 10.0]Communication link failure [message] => [Microsoft][SQL Server Native Client 10.0]Communication link failure ) [2] => Array ( [0] => 08S01 [SQLSTATE] => 08S01 [1] => -2147467259
=> -2147467259 [2] => [Microsoft][SQL Server Native Client 10.0]Communication link failure [message] => [Microsoft][SQL Server Native Client 10.0]Communication link failure ) )

If I see the error log it shows:

2010-10-17 12:32:38.88 Logon       Error: 18456, Severity: 14, State: 8.

2010-10-17 12

SQL Server and DMO: Distributed Management Objects Enable Easy Task Automation


SQL Server can be administered programmatically using system stored procedures, but Distributed Management Objects (DMO) offer a more modern, object-oriented alternative. This article introduces SQL-DMO in SQL Server 7.0 and SQL Server 2000 and describes the SQL-DMO object model, then focuses primarily on the Databases tree and the JobServer tree of the object model. The sample code and the article show how to use various objects such as the Registry object, the Configuration object, and the Database object to automate common administration tasks such as programmatically retrieving configuration settings, creating new databases, applying T-SQL scripts, and creating and scheduling backups.

Francesco Balena

MSDN Magazine May 2001

Distributed Transactions fail on Linked server

We get the below error while performing a distributed transaction on linked server. We have several linked servers configured in the source server and all of them succeed with the distributed transaction except on one.   We did all the basic troubleshooting and moreover the distributed transactions work fine if we use a remote server instead.   Need your expert guidance in resolving this issue     Error:   OLE DB provider "SQLNCLI10" for linked server "SERVERNAME.REDMOND.CORP.MICROSOFT.COM" returned message "No transaction is active.". Msg 7391, Level 16, State 2, Line 3 The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "SERVERNAME.REDMOND.CORP.MICROSOFT.COM" was unable to begin a distributed transaction.     Test code:   begin distributed transaction   select top 10 * from [SERVERNAME.REDMOND.CORP.MICROSOFT.COM].master.sys.objects   ROLLBACK     Source server :      Microsoft SQL Server 2008 (RTM) - 10.0.1779.0 (X64)        Nov 12 2008 12:10:04        Copyright (c) 1988-2008 Microsoft Corporation        Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1) (VM)     Target server :     Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)        Jul  9 2008 14:43:34        Copyright (c) 1988-2008 Microsoft Corporation        Enterprise Edition

WmiPrvSE.exe causes a huge memory leak in SQL server 2008 R2, why?

My OS is windows server 2008 r2 data center 64 bit and my SQL server is server 2008 R2. The problem is when I open sql server, the WmiPrvSE.exe process consumes 20 - 60kbs every second. Several hours later, it eats up at least 200mbs memorry and this process seems like it will never stop. Can any experts give me some ideas to fit this mess? PS: My mainboard is Asus striker II formular, cpu is intel quad-core. Also, all my software are updated to latest version.

SQL server memory / speed configuration

Let me preface this by saying I'm aware of SQL server memory architecture, i.e it takes as much as it can get it's hand's on ...I've read through all the post's on here and they have been very helpful ... However if someone could take a look at these these configuration values ... I'm trying to get a new server dialed in, I'm still having some user end speed issues, and application hangup's that seem sql related ... I'm by no means a dba so if someone who's knowledgeable could point me in the right direction I would appreciate it ... I feel like something is not configured properly ... The box has Microsoft SQL Server 2008 (RTM) 64-bit on Windows NT 6.0 <X64> Service Pack 2 Dell Power Edge R10 16 Logical CPU, 8 Hyperthread 12gig of memory (Right now SQL has 10/12 gig allocated in the task manager ( I know this is not accurate ) I'm adding another 12 gig tomorrow ... So the machine will be running 24 gig) There's two 9 gig databases running on the machine with several 4-6 million row tables .... Server is SQL Dedicated Configuration Values   Page Life Expectancy 18,038 under moderate load, tho I've seen it as low as 1,200 under heavy load .... Buffer Pool Usage CACHESTORE_SQLCP 2778616 OBJECTSTORE_LOCK_MANAGER 38816 MEMORYCLERK_SOSNODE 20936 CACHESTORE_OBJCP 18992 CACHESTORE_PHDR 16472 USERSTORE_SCHEMAMGR 12184 USERSTORE_DBMETADATA 8264 USE

SQL Server Management Studio - Invalid access to memory location

In SQL Server Management Studio (for SQL Server 2008), when I try to open a new query window, or create a new database, I get a popup error box saying the following: "Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (mscorlib)" This just started happening in the last few days, and I have no idea why.  I even uninstalled SQL Server 2008, and then installed SQL Server 2008 R2, and continued to get the exact same error, in the exact same scenarios. Please let me know if you have seen this before, and what I might try to correct it. Thanks, Robert  

Installing Microsoft.ACE.OLEDB.12.0 on a shared server--supported or not?

Here's the scenario: we have a Web application that needs to open an Excel 2007 file, read the sheet names and pass the sheet selected by a user to a SSIS package for processing on the DB server. During development, we discovered that the Microsoft Access Database engine (Microsoft.ACE.OLEDB.12.0) is required for our application to perform these tasks when running on a 64-bit server. Details: ASP.NET 4/VS 2010/SSIS on SQL 2008 R2; 32-bit environments have no issues; 64-bit requires installation of the provider. We followed this link to get the components: http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en We have installed the components and everything works great in our development and test environments. However, we must deploy to a 64-bit environment that is controlled by our customer's IT group, not by us. They are balking at installing the components because of the following statements that appear on the download page in the "Additional Information" section: "The Office System Drivers are only supported under certain scenarios, including: " Desktop applications which read from and write to various files formats including Microsoft Office Access, Microsoft Office Excel and text files. To transfer data between supported file formats and a database repository such as SQL Server; in the

online shared hosting sql server problem

 hi all             how to solve the problem in online sql server. A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)thank u

Max Server Memory Alteration..

I am running SQL Server 2005 Enterprise on Win Server 2003 SP1 32 bit with 16 GB RAM. I have both /3BG and /PAE enabled. AWE is enabled for SQL Server. I have set the Max Server Memory to 12 GB. When I check the perfmon counters, The Available MBytes is about 2.3 GB. This means that I am not using this 2.3 GB of my 16 GB memory. What I am thinking is that instead of keeping the /3GB switch, I will remove it and make the Max Server Memory to 13 GB. Will this be euqivalent to my prevoius configuration? Will my SQL Server get the same RAM as before? Anyways, what's the advice to achieve optimum utilization of RAM?

how to choose between Shared Memory, Named Pipes, TCP/IP, VIA?

What protocol to choose? Or, Why are they so many? I am mostly interested in contexts: 1)  development on local machine 2) development from remote machine (having SQL Server on another machine)  3) Production 4) what else should I bother/know about? I am developer, mostly using Developer Ed. mostly locally on Windows XP Pro SP3, and really had never bothered which protocol was used as far as connection was being successful. And I had never had any troubles to bother looking and choosing between protocols Why and when should I bother to choose between protocols for development?

SQL Server not releasing memory back!

Hi Guys,   I have done enough research on this topic and understood that SQL Server loves to cache as much memory as it can get hold of , but did not find a straight forward answer to my problem.   To explain things in detail, We are currently using SQL Server 2005 (64 Bit) on Windows 2003 (64 Bit) with 32 GB of RAM. This morning when I checked, it was showing the memory as 1GB RAM.  As soon as I stopped and restarted SQL Sever, I got back all 31GB of it! This is a live mirrored server, and the data is exposed through a .NET Win Application. Also, this is a dedicated SQL Server.   The min and max memory of the SQL Server is set at 16 and 2147483647 respectively.   My questions: 1. What can be done to make SQL Server release the memory back once the process is complete?   2. If this involves setting a limit to the max memory of the SQL Server, what can it be set to? And does setting the max memory low affect the performance of server?   3. I have other servers that are not dedicated SQL Servers which are showing the same 'memory' related problems, what should be the max memory setting on these ?   Any help in this regard is deeply appreciated.   Little_Birdie.

Not Releasing memory in sql server 2008 R2

HI I have a server with 8 Gb Ram I installed Sql server 2008 R2 Enterprise Edition on 64 bit platform Enterprise edition,in that for Sql server I allocated 6 GB of Ram I enable the AWE oprtion as well but in processing time it taking above 6 Gb ram like 7.gb or more after query completing its not release the memory how can I resolve this issue. Actually when we running quries it taking the memory and memory increasing gradually after executing the query its not releasing the memory per example I set maximum 6 GB per Sql server then I run the query memory will increase gradually like 3.4 gb,3.7 gb, 4.5gb,and so on it will reach 7.56gb then after it steadily over there not come to down I am using X64 bit windows server 2008 sql server 2008 R2. My system configuration is sql server 2008R2(10.0.3798) windows server 2008 X64 Ram is 8GB

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end of th

Hello,Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work.  I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week.  I opened the Management Studio this morning, just like every other morning and got this error:TITLE: Connect to Server------------------------------ Cannot connect to (local). ------------------------------ADDITIONAL INFORMATION: A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233) Of course the help page says no help is available.  I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix?  I am using XP Pro SP2...any help would be greatly appreciated!Thanks!Steph

Can anyone explain how SQL Server performance scales with CPUs/Cores, memory, disk drives, etc?

I have experienced the situation where our application running on an expensive system with two 4 core CPUs ran slower than on a cheap machine with one dual core CPU. Both machines had similar memory capacity. In each case, the same query was being run by only one user. It would be nice to find a way to increase performance, but if adding cores doesn't help, what can a poor developer do? Customers get annoyed when they spend a truckload of money on a new server and nothing changes... Another potential problem is when customers have an expensive SAN system Sometimes the performance is much slower then on a system with conventional storage. Can anyone explain the relationship between SQL Server perfomance and hardware ?

How to dedicate CPUs to SQL Server only such that it won't be shared with OS

Hi, On our SQL Server hardware, we have two quad core CPUs (8 CPUs from SQL server perspective) I understand that I can limit SQL Server to take only 1 core (4 CPUs) out of 8 CPUS, but my understanding is it might be shared with OS depends of the load of other applications running on the server. Is there any way to configure the server (OS+SQL Server) that dedicate 1 core (4 CPUs) to SQL server and allocate the rest of CPUs for OS and the rest of running applications including Integration Services? My understanding is dedicated CPUs to SQL Server doesn’t include SSIS. Is that right? Thank you, Max

COM Server process compiled with /clr option doesn't unload itself from memory when last COM client

I created Visual C++ ATL project in VS2010, exe type, imlemented COM object, then added /clr option to project. Project uses other C# dlls (WCF service). When last COM client disconnects and last COM object instance destroys, WCF service stopped, my COM server process doesn't unload itself from memory. All managed threads in C# dll are background, COM object doesn't create threads. How can I unload server process? Thank you in advance. 

Does SQL Server 2008 R2 Express Reporting Service support Shared Datasets?

I have spent a few hours trying to get this to work. I am using Report Builder 3.0 (locally), with SQL Server 2008 R2 Express Edition on a remote web server. I am running Report Builder as an Admin under Win7 64bit. All is OK until I attempt a Save of a newly created shared dataset. The error message is: Failed to save dataset "mydataset.rsd" The feature "Shared dataset" is not supported in this edition of Reporting Services. Details: The feature: "Shared dataset" is not supported in this edition of Reporting Services. ---> Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Shared dataset" is not supported in this edition of Reporting Services. I have researched the web, and the list of features for Express Edition does not list this feature as not being supported, although it does list "Shared component library" as being missing. Could anyone please confirm the situation please. If it is  a bug, is there any fix or workaround?  John Walton  
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend