Home Page › Forums › BizTalk 2004 – BizTalk 2010 › BizTalk / SQL Server Issue
- This topic has 1 reply, 1 voice, and was last updated 9 years, 6 months ago by
community-content.
-
AuthorPosts
-
-
December 11, 2006 at 7:19 AM #16830
This is my first BizTalk experience and I have no SQL Server experience. We have noticed a couple of issues with SQL Server when BizTalk is processing. Since SQL Server is installed and configured as part of the BizTalk install, I expected few if any issues with SQL Server since it is just there to support BizTalk internal processes.
When BizTalk runs for a while, SQL Server grabs more and more memory. On our 2 GB Windows 2003 Server machine, SQL Server frequenty shows it has grabbed 1.5 GB and more. Even when BizTalk processing ends for the day, the next morning SQL Server still has allocated the 1.5 GB or memory. It does not seem to release memory when it no longer needs it.
This seems to be either a memory leak issue or SQL Server does not play well in a multi-process OS. Only by stopping and starting SQL Server can this memory be released.
The second issue, may be tied to the memory issue since I beleive we only see it when SQL Server grabs huge amounts of memory. BizTalk processing will stop and when I check the event viewer I see….
Reading error. Exception information: TDDS failed to read from source database. SQL Server:xxxxx, Database: BizTalkMsgBoxDb. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
In the last instance, 8 minutes and 3 seconds later I get…
Reading error. Recovered from previous error. SQLServer:xxxxxx, Database: BizTalkMsgBoxDb
I do not beleive the group that installed BizTalk/SQL Server did anything strange. Is the above a known issue? I would appreciate any suggestions anyone may have.
-
December 12, 2006 at 2:11 AM #16847
You are right, SQL Server does play well with others. It is reluctant to release memory once allocated.
There are options in SQL Server where you can limit the maximum memory it will use. By default this is all the memory in the system.
You could try to limit SQL to 1GB of memory. This may slow SQL somewhat (smaller cache = more disk hits) but may speed up the machine as a whole by allowing other processes more memory and reducing page faults.
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.