Showing posts with label happening. Show all posts
Showing posts with label happening. Show all posts

Wednesday, March 28, 2012

merge client failing

Hi

We have sql2005 merge replication happening - it is using replisapi.dll over the net.

One of the clients has been working fine, until yesterday afternoon - we are running sql2005 sp1 at subscriber and distributer

The message is as follows....


Please help !

Error messages:

The process could not read the request message due to OS error 10054. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147014842)
Get help: http://help/MSSQL_REPL-2147014842

The format of a message during Web synchronization was invalid. Ensure that replication components are properly configured at the Web server. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199374)
Get help: http://help/MSSQL_REPL-2147199374

The subscription to publication 'yarraman main' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019)
Get help: http://help/MSSQL_REPL-2147201019

OS error 10054 is "An existing connection was forcibly closed by the remote host.", which could mean security or network issue. Could this be the case?

Wednesday, March 7, 2012

Memory problem related to DBCC CHECKDB

I have been monitoring my SQL server and noticing abrupt drops in Available
Memory -- happening about once a week.
I could not figure out what was causing this until I discovered that the low
memory condition corresponded to the exact time that I run a weekly DBCC CH
ECKDB command on a database.
Scenario:
1. Available Memory starts at about 1000MB (this is normal)
2. Run DBCC CHECKDB on a particular database (only occurs on this one).
3. Available Memory suddently drops to less than 200MB free!
4. The Memory is never freed up until I re-start SQL Server.
Has anyone ever seen this problem before?
Thanks,
DanIt is by Design.
SQL Server will not relinquish memory once allocated, unless there is a requ
est from the OS
--
HTH
Satish Balusa
Corillian Corp.
"Dan Carollo" <dan.carollo@.verizon.net> wrote in message news:uw$X%23mS5DHA.
2764@.TK2MSFTNGP09.phx.gbl...
I have been monitoring my SQL server and noticing abrupt drops in Available
Memory -- happening about once a week.
I could not figure out what was causing this until I discovered that the low
memory condition corresponded to the exact time that I run a weekly DBCC CH
ECKDB command on a database.
Scenario:
1. Available Memory starts at about 1000MB (this is normal)
2. Run DBCC CHECKDB on a particular database (only occurs on this one).
3. Available Memory suddently drops to less than 200MB free!
4. The Memory is never freed up until I re-start SQL Server.
Has anyone ever seen this problem before?
Thanks,
Dan|||Dan,
What is wrong with this?
If you still have available memory ... your performance is not hurting.
Most of this memory is most likely in buffer cache.
-Lars
"Dan Carollo" <dan.carollo@.verizon.net> wrote in message news:uw$X%23mS5DHA.
2764@.TK2MSFTNGP09.phx.gbl...
I have been monitoring my SQL server and noticing abrupt drops in Available
Memory -- happening about once a week.
I could not figure out what was causing this until I discovered that the low
memory condition corresponded to the exact time that I run a weekly DBCC CH
ECKDB command on a database.
Scenario:
1. Available Memory starts at about 1000MB (this is normal)
2. Run DBCC CHECKDB on a particular database (only occurs on this one).
3. Available Memory suddently drops to less than 200MB free!
4. The Memory is never freed up until I re-start SQL Server.
Has anyone ever seen this problem before?
Thanks,
Dan|||Further to what other replies have said, it is buffer pool memory. DBCC CHEC
KDB reads every allocated page in the database using parallel threads and si
gnificant readahead and so the buffer pool grows to accomodate this.
As long as you're not short of memory, there's no big deal.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan Carollo" <dan.carollo@.verizon.net> wrote in message news:uw$X#mS5DHA.27
64@.TK2MSFTNGP09.phx.gbl...
I have been monitoring my SQL server and noticing abrupt drops in Available
Memory -- happening about once a week.
I could not figure out what was causing this until I discovered that the low
memory condition corresponded to the exact time that I run a weekly DBCC CH
ECKDB command on a database.
Scenario:
1. Available Memory starts at about 1000MB (this is normal)
2. Run DBCC CHECKDB on a particular database (only occurs on this one).
3. Available Memory suddently drops to less than 200MB free!
4. The Memory is never freed up until I re-start SQL Server.
Has anyone ever seen this problem before?
Thanks,
Dan