Merge heavy on distr cpu

125Gb heavy OLTP publication db w/ Transactional Replication replicating 400
tables to 5 different servers. No problems on remote distributor, cpu hardly
used, sits practically idle most of the day staying under 10%. Ram is used
however not getting taxed.
We added merge replication for 1 table and the cpu's pegged to 90 to 100%
each time the merge agents pick up transactions at pub. Every 20 minutes a
job populated this table w/ 100 to 200 inserts at publisher, the 5 merge
agents kick in immediately (continuously running) and spike cpu bringing
server to a crawl.
Publisher, Distributor, & all Subscribers on LAN w/ 100Mbps connections.
SQL 2000 SP3 on all servers. Distributor is a 6CPU PIII 700Mhz each. New
Distributor hardware not an option. Have to limp along until new budgets kick
in...
Thoughts...?
TIA,
Chris
Chris,
are the 100/200 inserts involving BLOB datatypes? How long does the spike
last? Anyway, I'd change the merge agents from running continuously, in
order to stagger their impact on the publisher.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

merge Agent-login failure

I have 2 servers running on workgroups; merge replication
running SQL Server 2005 on each, snapshot running ok, start merge agent and
get this.
Error messages:
The merge process could not connect to the Publisher 'XXUSSHU18UT:Process'.
Check to ensure that the server is running. (Source: MSSQL_REPL, Error
number: MSSQL_REPL-2147198719)
Get help: http://help/MSSQL_REPL-2147198719
The process could not connect to Publisher 'XXUSSHU18UT'. (Source:
MSSQL_REPL, Error number: MSSQL_REPL20084)
Get help: http://help/MSSQL_REPL20084
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Source: MSSQLServer,
Error number: 18456)
Get help: http://help/18456
The easiest solution if you don't want to investigate the trust issue is to
switch the merge agent to be running under a SQL Server Login.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi,
I had similar problem few years ago when I was new to merge replication on
SQL Server 2000.
Create same windows account on both servers with same user name and same
password, run sql server end sql server agent on it and use this security
option for merge agent:
1. Run under SQL Server Agent service account
2. By impersonating the process account.
"bt7403" wrote:

> I have 2 servers running on workgroups; merge replication
> running SQL Server 2005 on each, snapshot running ok, start merge agent and
> get this.
> Error messages:
> The merge process could not connect to the Publisher 'XXUSSHU18UT:Process'.
> Check to ensure that the server is running. (Source: MSSQL_REPL, Error
> number: MSSQL_REPL-2147198719)
> Get help: http://help/MSSQL_REPL-2147198719
> The process could not connect to Publisher 'XXUSSHU18UT'. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL20084)
> Get help: http://help/MSSQL_REPL20084
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Source: MSSQLServer,
> Error number: 18456)
> Get help: http://help/18456
|||connect to the publisher in SQL Server Management Studio, expand the local
publication folder, expand your publication, right click on the Subscriber
and select properties. In the Security Agent process account section click
on the three ellipses and enter a windows account which has in the dbo role
on the publication database or is in the PAL.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"bt7403" <bt7403@.discussions.microsoft.com> wrote in message
news:717FD769-249F-40EC-9425-116738AA1740@.microsoft.com...
>I have 2 servers running on workgroups; merge replication
> running SQL Server 2005 on each, snapshot running ok, start merge agent
> and
> get this.
> Error messages:
> The merge process could not connect to the Publisher
> 'XXUSSHU18UT:Process'.
> Check to ensure that the server is running. (Source: MSSQL_REPL, Error
> number: MSSQL_REPL-2147198719)
> Get help: http://help/MSSQL_REPL-2147198719
> The process could not connect to Publisher 'XXUSSHU18UT'. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL20084)
> Get help: http://help/MSSQL_REPL20084
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Source:
> MSSQLServer,
> Error number: 18456)
> Get help: http://help/18456
|||Problem solved:
under SQL Security, I had to create a GUEST acct. and map this user to the
PUB db. Under Subscription Properties-Removed use of SQL Server Agent
service acct. and used Windows acct-maintained SQL Server Auth for Subscriber
connection.
Merge ran fine.
A side note:
Snapshot security settings do not require fine-tuning like Merge does.
I run this under SQL Server Agent service acct. and use SQL Server login for
connection to PUB.
thx. for your replies.
"Hilary Cotter" wrote:

> connect to the publisher in SQL Server Management Studio, expand the local
> publication folder, expand your publication, right click on the Subscriber
> and select properties. In the Security Agent process account section click
> on the three ellipses and enter a windows account which has in the dbo role
> on the publication database or is in the PAL.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "bt7403" <bt7403@.discussions.microsoft.com> wrote in message
> news:717FD769-249F-40EC-9425-116738AA1740@.microsoft.com...
>
>
sql

Merge Agent error number 53 for replication

Hi, I am trying to setup replication between 2 SQL Servers across
non-trusted domains(2 different domains). I am able to successfully
registered both SQL servers in either domains. But I still cannot access the
snapshot folder in the Distributor/Publisher domain from the subscriber
domain.
* I've create the same SQL login: SQLAdmin and use this SQL authentication
on both the distributor and subscriber to interact with each other. They can
access each other fine, accept the subscriber cannot access the snapshot
folder on the distributor.
* I've given the Snapshot folder UNC path and Administrative share the
everyone permission.
********
I've read these Microsoft documents already:
Q321822 - Replicate between computers running SQL Server in Non-Trusted
Domains or Across the Internet.
Q240688 - Replication Subscribers Unable to Synchronize with Pull
Subscription.
Objective: I cannot create a pass-through account because the Distributor is
installed upon a Win2k Domain controller (with active directory), but I have
use SQL authentication on both SQL Server, but it still cannot access the
snapshot folder. All I need is for the subscriber to access the snapshot
folder. What do I need to do? Please list the steps, thanks...
****************************************
*****
The schema script
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' could not be propagated to the subscriber.
****************************
The schema script
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----
--
The process could not read file
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' due to OS error 53.
(Source: ECSWEB (Agent); Error number: 0)
----
--
The network path was not found.
(Source: (OS); Error number: 53)
----
--
*************************
The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury
Pub1\20040306225703\snapshot.pre' could not be propagated to the subscriber.
*************************
The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury
Pub1\20040306225703\snapshot.pre' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----
--
The process could not read file '\\MERCURY\G$\Program Files\Microsoft SQL
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury
Pub1\20040306225703\snapshot.pre' due to OS error 53.
(Source: ECSWEB (Agent); Error number: 0)
----
--
The network path was not found.
(Source: (OS); Error number: 53)
----
--notice the unc path is completly wrong.
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_N
orthwind_NorthwindMercuryPub1\200403
11181629\
its the dollar sign which I think is messing you up.
can you run run a net use * \\Mercury\REPLDATA on your subscriber and see if
you can map this drive. Then try to navigate upwards to the snapshot.pre
file?
Also if you could run this on your publisher/distributor and report back
here with what you get it will be helpful
select working_directory from msdb.dbo.MSdistpublishers
"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:#ONwfV3BEHA.576@.TK2MSFTNGP11.phx.gbl...
> Hi, I am trying to setup replication between 2 SQL Servers across
> non-trusted domains(2 different domains). I am able to successfully
> registered both SQL servers in either domains. But I still cannot access
the
> snapshot folder in the Distributor/Publisher domain from the subscriber
> domain.
> * I've create the same SQL login: SQLAdmin and use this SQL authentication
> on both the distributor and subscriber to interact with each other. They
can
> access each other fine, accept the subscriber cannot access the snapshot
> folder on the distributor.
> * I've given the Snapshot folder UNC path and Administrative share the
> everyone permission.
> ********
> I've read these Microsoft documents already:
> Q321822 - Replicate between computers running SQL Server in Non-Trusted
> Domains or Across the Internet.
> Q240688 - Replication Subscribers Unable to Synchronize with Pull
> Subscription.
> Objective: I cannot create a pass-through account because the Distributor
is
> installed upon a Win2k Domain controller (with active directory), but I
have
> use SQL authentication on both SQL Server, but it still cannot access the
> snapshot folder. All I need is for the subscriber to access the snapshot
> folder. What do I need to do? Please list the steps, thanks...
>
> ****************************************
*****
> The schema script
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' could not be propagated to the subscriber.
> ****************************
> The schema script
>[/color]
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----[/color]
--
> --
> The process could not read file
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' due to OS error 53.
> (Source: ECSWEB (Agent); Error number: 0)
> ----[/color]
--
> --
> The network path was not found.
> (Source: (OS); Error number: 53)
> ----
--
> --
> *************************
> The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> Pub1\20040306225703\snapshot.pre' could not be propagated to the[/color]
subscriber.
> *************************
> The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> Pub1\20040306225703\snapshot.pre' could not be propagated to the[/color]
subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----
--
> --
> The process could not read file '\\MERCURY\G$\Program Files\Microsoft SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> Pub1\20040306225703\snapshot.pre' due to OS error 53.
> (Source: ECSWEB (Agent); Error number: 0)
> ----[/color]
--
> --
> The network path was not found.
> (Source: (OS); Error number: 53)
> ----
--
> --
>
>|||Hilary,
I just ran the select working_directory on the Distributor and this
is the results:
working_directory
\\Mercury\REPLDATA
\\Mercury\REPLDATA
\\Mercury\REPLDATA
\\MERCURY\G$\Program Files\Microsoft SQL Server\MSSQL$MERCURY\ReplData
Yes I can net use * \\Mercury \REPLDATA and navigate to the snapshot.pre
file.
Regards
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:uPeVrH#BEHA.2404@.TK2MSFTNGP11.phx.gbl...
> notice the unc path is completly wrong.
>
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_N
orthwind_NorthwindMercuryPub1\200403[col
or=darkred]
> 11181629\
> its the dollar sign which I think is messing you up.
> can you run run a net use * \\Mercury\REPLDATA on your subscriber and see[/color]
if
> you can map this drive. Then try to navigate upwards to the snapshot.pre
> file?
> Also if you could run this on your publisher/distributor and report back
> here with what you get it will be helpful
> select working_directory from msdb.dbo.MSdistpublishers
>
> "Joe Mine" <huytuanattpgdotcomdotau> wrote in message
> news:#ONwfV3BEHA.576@.TK2MSFTNGP11.phx.gbl...
> the
authentication
> can
Distributor
> is
> have
the
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> ----
> --
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> ----
> --
> ----
> --
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> subscriber.
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> subscriber.
> ----
> --
SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> ----
> --
> ----
> --
>[/color]|||Now I even got error no: 1326
The schema script
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----
--
The process could not read file
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' due to OS error 1326.
(Source: ECSWEB (Agent); Error number: 0)
----
--
Logon failure: unknown user name or bad password.
(Source: (OS); Error number: 1326)
----
--
"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:#8btBY#BEHA.3784@.TK2MSFTNGP10.phx.gbl...
> Hilary,
> I just ran the select working_directory on the Distributor and
this
> is the results:
> working_directory
> \\Mercury\REPLDATA
> \\Mercury\REPLDATA
> \\Mercury\REPLDATA
> \\MERCURY\G$\Program Files\Microsoft SQL Server\MSSQL$MERCURY\ReplData
>
> Yes I can net use * \\Mercury \REPLDATA and navigate to the snapshot.pre
> file.
> Regards
>
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:uPeVrH#BEHA.2404@.TK2MSFTNGP11.phx.gbl...
>
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_N
orthwind_NorthwindMercuryPub1\200403[col
or=darkred]
see
> if
access
subscriber
> authentication
They
snapshot
Non-Trusted
> Distributor
I
> the
snapshot
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
number: -2147201001)
> ----
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> ----
> ----
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
number: -2147201001)
> ----
> SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> ----
> ----
>[/color]|||I take it you have moved to using SQL Server Standard security in your
enabled subscriber.
Is this account in the PAL for the publication. Right click on your
publication in the publication database, select publication properties, and
go to Publication Access List. The account you are using must be in the
server administrator role on the subscriber, and in the dbo role on the
publication database. It also must be present in the PAL.
Also verify that the password you are using is correct. To do this, go to
Tools-Replication-Configure Publishers, Distributors, Subscribers, click on
the Subscribers tab, and locate your Subscriber. Then click on the browse
button to the right of your Subscribers, and then in the Use SQL Server
Authentication enter the correct information.
"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:OeNZV$$BEHA.1588@.tk2msftngp13.phx.gbl...
> Now I even got error no: 1326
>
> The schema script
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----[/color]
--
> --
> The process could not read file
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' due to OS error 1326.
> (Source: ECSWEB (Agent); Error number: 0)
> ----[/color]
--
> --
> Logon failure: unknown user name or bad password.
> (Source: (OS); Error number: 1326)
> ----
--
> --
> "Joe Mine" <huytuanattpgdotcomdotau> wrote in message
> news:#8btBY#BEHA.3784@.TK2MSFTNGP10.phx.gbl...
> this
snapshot.pre
>
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_N
orthwind_NorthwindMercuryPub1\200403[col
or=darkred]
> see
snapshot.pre
back
> access
> subscriber
> They
> snapshot
the
> Non-Trusted
but
> I
access
> snapshot
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> number: -2147201001)
> ----
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> ----
> ----
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> number: -2147201001)
> ----
Files\Microsoft
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> ----
> ----
>[/color]

Merge Agent error number 53 for replication

Hi, I am trying to setup replication between 2 SQL Servers across
non-trusted domains(2 different domains). I am able to successfully
registered both SQL servers in either domains. But I still cannot access the
snapshot folder in the Distributor/Publisher domain from the subscriber
domain.
* I've create the same SQL login: SQLAdmin and use this SQL authentication
on both the distributor and subscriber to interact with each other. They can
access each other fine, accept the subscriber cannot access the snapshot
folder on the distributor.
* I've given the Snapshot folder UNC path and Administrative share the
everyone permission.
********
I've read these Microsoft documents already:
Q321822 - Replicate between computers running SQL Server in Non-Trusted
Domains or Across the Internet.
Q240688 - Replication Subscribers Unable to Synchronize with Pull
Subscription.
Objective: I cannot create a pass-through account because the Distributor is
installed upon a Win2k Domain controller (with active directory), but I have
use SQL authentication on both SQL Server, but it still cannot access the
snapshot folder. All I need is for the subscriber to access the snapshot
folder. What do I need to do? Please list the steps, thanks...
****************************************
*****
The schema script
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' could not be propagated to the subscriber.
****************************
The schema script
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----
--
The process could not read file
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' due to OS error 53.
(Source: ECSWEB (Agent); Error number: 0)
----
--
The network path was not found.
(Source: (OS); Error number: 53)
----
--
*************************
The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury
Pub1\20040306225703\snapshot.pre' could not be propagated to the subscriber.
*************************
The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury
Pub1\20040306225703\snapshot.pre' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----
--
The process could not read file '\\MERCURY\G$\Program Files\Microsoft SQL
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury
Pub1\20040306225703\snapshot.pre' due to OS error 53.
(Source: ECSWEB (Agent); Error number: 0)
----
--
The network path was not found.
(Source: (OS); Error number: 53)
----
--OS Error 53 == Network Name not found.
Check for Name resolution problems with either WINS or DNS.
Verify you can get to the server from the client using the "net view
\\servername" command.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||notice the unc path is completly wrong.
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_N
orthwind_NorthwindMercuryPub1\200403
11181629\
its the dollar sign which I think is messing you up.
can you run run a net use * \\Mercury\REPLDATA on your subscriber and see if
you can map this drive. Then try to navigate upwards to the snapshot.pre
file?
Also if you could run this on your publisher/distributor and report back
here with what you get it will be helpful
select working_directory from msdb.dbo.MSdistpublishers
"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:#ONwfV3BEHA.576@.TK2MSFTNGP11.phx.gbl...
> Hi, I am trying to setup replication between 2 SQL Servers across
> non-trusted domains(2 different domains). I am able to successfully
> registered both SQL servers in either domains. But I still cannot access
the
> snapshot folder in the Distributor/Publisher domain from the subscriber
> domain.
> * I've create the same SQL login: SQLAdmin and use this SQL authentication
> on both the distributor and subscriber to interact with each other. They
can
> access each other fine, accept the subscriber cannot access the snapshot
> folder on the distributor.
> * I've given the Snapshot folder UNC path and Administrative share the
> everyone permission.
> ********
> I've read these Microsoft documents already:
> Q321822 - Replicate between computers running SQL Server in Non-Trusted
> Domains or Across the Internet.
> Q240688 - Replication Subscribers Unable to Synchronize with Pull
> Subscription.
> Objective: I cannot create a pass-through account because the Distributor
is
> installed upon a Win2k Domain controller (with active directory), but I
have
> use SQL authentication on both SQL Server, but it still cannot access the
> snapshot folder. All I need is for the subscriber to access the snapshot
> folder. What do I need to do? Please list the steps, thanks...
>
> ****************************************
*****
> The schema script
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' could not be propagated to the subscriber.
> ****************************
> The schema script
>[/color]
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----[/color]
--
> --
> The process could not read file
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' due to OS error 53.
> (Source: ECSWEB (Agent); Error number: 0)
> ----[/color]
--
> --
> The network path was not found.
> (Source: (OS); Error number: 53)
> ----
--
> --
> *************************
> The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> Pub1\20040306225703\snapshot.pre' could not be propagated to the[/color]
subscriber.
> *************************
> The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> Pub1\20040306225703\snapshot.pre' could not be propagated to the[/color]
subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----
--
> --
> The process could not read file '\\MERCURY\G$\Program Files\Microsoft SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> Pub1\20040306225703\snapshot.pre' due to OS error 53.
> (Source: ECSWEB (Agent); Error number: 0)
> ----[/color]
--
> --
> The network path was not found.
> (Source: (OS); Error number: 53)
> ----
--
> --
>
>|||Hilary,
I just ran the select working_directory on the Distributor and this
is the results:
working_directory
\\Mercury\REPLDATA
\\Mercury\REPLDATA
\\Mercury\REPLDATA
\\MERCURY\G$\Program Files\Microsoft SQL Server\MSSQL$MERCURY\ReplData
Yes I can net use * \\Mercury \REPLDATA and navigate to the snapshot.pre
file.
Regards
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:uPeVrH#BEHA.2404@.TK2MSFTNGP11.phx.gbl...
> notice the unc path is completly wrong.
>
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_N
orthwind_NorthwindMercuryPub1\200403[col
or=darkred]
> 11181629\
> its the dollar sign which I think is messing you up.
> can you run run a net use * \\Mercury\REPLDATA on your subscriber and see[/color]
if
> you can map this drive. Then try to navigate upwards to the snapshot.pre
> file?
> Also if you could run this on your publisher/distributor and report back
> here with what you get it will be helpful
> select working_directory from msdb.dbo.MSdistpublishers
>
> "Joe Mine" <huytuanattpgdotcomdotau> wrote in message
> news:#ONwfV3BEHA.576@.TK2MSFTNGP11.phx.gbl...
> the
authentication
> can
Distributor
> is
> have
the
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> ----
> --
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> ----
> --
> ----
> --
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> subscriber.
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> subscriber.
> ----
> --
SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> ----
> --
> ----
> --
>[/color]|||Now I even got error no: 1326
The schema script
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----
--
The process could not read file
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040
311181629\snapshot.pre' due to OS error 1326.
(Source: ECSWEB (Agent); Error number: 0)
----
--
Logon failure: unknown user name or bad password.
(Source: (OS); Error number: 1326)
----
--
"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:#8btBY#BEHA.3784@.TK2MSFTNGP10.phx.gbl...
> Hilary,
> I just ran the select working_directory on the Distributor and
this
> is the results:
> working_directory
> \\Mercury\REPLDATA
> \\Mercury\REPLDATA
> \\Mercury\REPLDATA
> \\MERCURY\G$\Program Files\Microsoft SQL Server\MSSQL$MERCURY\ReplData
>
> Yes I can net use * \\Mercury \REPLDATA and navigate to the snapshot.pre
> file.
> Regards
>
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:uPeVrH#BEHA.2404@.TK2MSFTNGP11.phx.gbl...
>
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_N
orthwind_NorthwindMercuryPub1\200403[col
or=darkred]
see
> if
access
subscriber
> authentication
They
snapshot
Non-Trusted
> Distributor
I
> the
snapshot
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
number: -2147201001)
> ----
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> ----
> ----
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
number: -2147201001)
> ----
> SQL
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> ----
> ----
>[/color]|||I take it you have moved to using SQL Server Standard security in your
enabled subscriber.
Is this account in the PAL for the publication. Right click on your
publication in the publication database, select publication properties, and
go to Publication Access List. The account you are using must be in the
server administrator role on the subscriber, and in the dbo role on the
publication database. It also must be present in the PAL.
Also verify that the password you are using is correct. To do this, go to
Tools-Replication-Configure Publishers, Distributors, Subscribers, click on
the Subscribers tab, and locate your Subscriber. Then click on the browse
button to the right of your Subscribers, and then in the Use SQL Server
Authentication enter the correct information.
"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:OeNZV$$BEHA.1588@.tk2msftngp13.phx.gbl...
> Now I even got error no: 1326
>
> The schema script
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----[/color]
--
> --
> The process could not read file
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> 311181629\snapshot.pre' due to OS error 1326.
> (Source: ECSWEB (Agent); Error number: 0)
> ----[/color]
--
> --
> Logon failure: unknown user name or bad password.
> (Source: (OS); Error number: 1326)
> ----
--
> --
> "Joe Mine" <huytuanattpgdotcomdotau> wrote in message
> news:#8btBY#BEHA.3784@.TK2MSFTNGP10.phx.gbl...
> this
snapshot.pre
>
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_N
orthwind_NorthwindMercuryPub1\200403[col
or=darkred]
> see
snapshot.pre
back
> access
> subscriber
> They
> snapshot
the
> Non-Trusted
but
> I
access
> snapshot
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> number: -2147201001)
> ----
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_
Northwind_NorthwindMercuryPub1\20040[col
or=darkred]
> ----
> ----
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
>[/color]
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> number: -2147201001)
> ----
Files\Microsoft
>
Server\MSSQL$MERCURY\ReplData\unc\MERCUR
Y$MERCURY_Northwind_NorthwindMercury[col
or=darkred]
> ----
> ----
>[/color]|||All I need is for the subscriber to access the snapshot
folder. What do I need to do? Please list the steps, thanks...
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...sql

Memtoleave and -g-switch

hi out there
On our Windows 2003 servers w. sp1 and running MS SQL Server 2000 w. sp4 we
see from time to time that we get this error "cannot allocate 64k
continous memory" or "SQL Server could not spawn process_loginread thread"
which could be caused by nothing left in the "Memtoleave" pool - I have now
search for advice on how to determine the values for the -g-switch - but
without much success - and if I just go for the "try&error" concept my
sql-server just allocates less and less ? - ehh - in which units are the
parameters for the -g option specified - bytes, kilobytes, mbytes - 4k block
? Any suggestions for measuring the actual running value of this pool -
memtoleave ?

best regards /ti

The units for -g are MB. The default is 256.

Is this a 32 or 64 bit system?

How much memory is on the system?

Are you running SQL Server with AWE enabled?

|||

Could you run the following query (when you are having this problem) and gives us the results.

Code Snippet

SELECTtype, multi_pages_kb FROMsys.dm_os_memory_clerksWHERE multi_pages_kb > 0

ORDERBY multi_pages_kb DESC

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||

SQL 2000 does not have DMVs. There's no easy way to profile memory usage in SQL 2000. See http://msdn2.microsoft.com/en-US/library/aa175282(sql.80).aspx for more information

Thanks, Ron D.

|||Oops, I missed the 2000 part :-)

Memtoleave and -g-switch

hi out there
On our Windows 2003 servers w. sp1 and running MS SQL Server 2000 w. sp4 we
see from time to time that we get this error "cannot allocate 64k
continous memory" or "SQL Server could not spawn process_loginread thread"
which could be caused by nothing left in the "Memtoleave" pool - I have now
search for advice on how to determine the values for the -g-switch - but
without much success - and if I just go for the "try&error" concept my
sql-server just allocates less and less ? - ehh - in which units are the
parameters for the -g option specified - bytes, kilobytes, mbytes - 4k block
? Any suggestions for measuring the actual running value of this pool -
memtoleave ?

best regards /ti

The units for -g are MB. The default is 256.

Is this a 32 or 64 bit system?

How much memory is on the system?

Are you running SQL Server with AWE enabled?

|||

Could you run the following query (when you are having this problem) and gives us the results.

Code Snippet

SELECT type, multi_pages_kb FROM sys.dm_os_memory_clerks WHERE multi_pages_kb > 0

ORDER BY multi_pages_kb DESC

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||

SQL 2000 does not have DMVs. There's no easy way to profile memory usage in SQL 2000. See http://msdn2.microsoft.com/en-US/library/aa175282(sql.80).aspx for more information

Thanks, Ron D.

|||Oops, I missed the 2000 part :-)

Memory usage 98% is it a bad thing?

I am using Spotlight to monitor my servers.
I see that memory is pegged, and the display shows a memory alert (yellow
color instead of green). Actual ram shows usage as 5.67 gig of 5.75 gig.
Virtual shows 2gig free.
All other process look low.
This server is a manufacturing system that takes job requests from the web.
We are a check printing house so we crunch allot of postscript as a "job"
that gets sent to one of our big Xerox printers.
Is this something to be concerned with? System has been up for weeks with
out a reboot and I like it that way.
Stephen Russell wrote:
> I am using Spotlight to monitor my servers.
> I see that memory is pegged, and the display shows a memory alert
> (yellow color instead of green). Actual ram shows usage as 5.67 gig
> of 5.75 gig. Virtual shows 2gig free.
> All other process look low.
> This server is a manufacturing system that takes job requests from
> the web. We are a check printing house so we crunch allot of
> postscript as a "job" that gets sent to one of our big Xerox printers.
> Is this something to be concerned with? System has been up for weeks
> with out a reboot and I like it that way.
If you are using the AWE ENabled option with SQL Server, you need to
specify the "Max Server Memory" for SQL Server to prevent it from using
all available RAM on the server. Make sure you leave enough RAM for the
OS and any other services running on the server.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> If you are using the AWE ENabled option with SQL Server, you need to
> specify the "Max Server Memory" for SQL Server to prevent it from using
> all available RAM on the server. Make sure you leave enough RAM for the
OS
> and any other services running on the server.
Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
machine. My event log has allot of messages for paging errors. I can
restart the server tomorrow before start of business day. I have to give
my
b2b client 12 hrs notice, and that has been delivered.
|||If you really are using AWE then that is still not enough left for the OS.
SQL Server MemToLeave needs up to 384MB by default and that is on top of the
MAX memory setting which is only for the memory pool. Then you need memory
for the OS and any other apps that may be running on the machine. If you
have 6GB total then I would not set the Max memory any higher than 5.0GB.
Maybe even less if there are other apps on the server.
Andrew J. Kelly SQL MVP
"Stephen Russell" <srussell@.lotmate.com> wrote in message
news:%235FY6OpoFHA.3984@.TK2MSFTNGP10.phx.gbl...
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> OS
> Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
> machine. My event log has allot of messages for paging errors. I can
> restart the server tomorrow before start of business day. I have to give
> my
> b2b client 12 hrs notice, and that has been delivered.
>
>
|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23mwUbdpoFHA.420@.TK2MSFTNGP09.phx.gbl...
> If you really are using AWE then that is still not enough left for the OS.
> SQL Server MemToLeave needs up to 384MB by default and that is on top of
> the MAX memory setting which is only for the memory pool. Then you need
> memory for the OS and any other apps that may be running on the machine.
> If you have 6GB total then I would not set the Max memory any higher than
> 5.0GB. Maybe even less if there are other apps on the server.
Thanks. I have the max memory usage set to 5 gig. This server is only a
SQL Server box, with nothing else on it.

Memory usage 98% is it a bad thing?

I am using Spotlight to monitor my servers.
I see that memory is pegged, and the display shows a memory alert (yellow
color instead of green). Actual ram shows usage as 5.67 gig of 5.75 gig.
Virtual shows 2gig free.
All other process look low.
This server is a manufacturing system that takes job requests from the web.
We are a check printing house so we crunch allot of postscript as a "job"
that gets sent to one of our big Xerox printers.
Is this something to be concerned with? System has been up for weeks with
out a reboot and I like it that way. Stephen Russell wrote:
> I am using Spotlight to monitor my servers.
> I see that memory is pegged, and the display shows a memory alert
> (yellow color instead of green). Actual ram shows usage as 5.67 gig
> of 5.75 gig. Virtual shows 2gig free.
> All other process look low.
> This server is a manufacturing system that takes job requests from
> the web. We are a check printing house so we crunch allot of
> postscript as a "job" that gets sent to one of our big Xerox printers.
> Is this something to be concerned with? System has been up for weeks
> with out a reboot and I like it that way.
If you are using the AWE ENabled option with SQL Server, you need to
specify the "Max Server Memory" for SQL Server to prevent it from using
all available RAM on the server. Make sure you leave enough RAM for the
OS and any other services running on the server.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> If you are using the AWE ENabled option with SQL Server, you need to
> specify the "Max Server Memory" for SQL Server to prevent it from using
> all available RAM on the server. Make sure you leave enough RAM for the
OS
> and any other services running on the server.
Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
machine. My event log has allot of messages for paging errors. I can
restart the server tomorrow before start of business day. I have to give
my
b2b client 12 hrs notice, and that has been delivered.|||If you really are using AWE then that is still not enough left for the OS.
SQL Server MemToLeave needs up to 384MB by default and that is on top of the
MAX memory setting which is only for the memory pool. Then you need memory
for the OS and any other apps that may be running on the machine. If you
have 6GB total then I would not set the Max memory any higher than 5.0GB.
Maybe even less if there are other apps on the server.
Andrew J. Kelly SQL MVP
"Stephen Russell" <srussell@.lotmate.com> wrote in message
news:%235FY6OpoFHA.3984@.TK2MSFTNGP10.phx.gbl...
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> OS
> Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
> machine. My event log has allot of messages for paging errors. I can
> restart the server tomorrow before start of business day. I have to give
> my
> b2b client 12 hrs notice, and that has been delivered.
>
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23mwUbdpoFHA.420@.TK2MSFTNGP09.phx.gbl...
> If you really are using AWE then that is still not enough left for the OS.
> SQL Server MemToLeave needs up to 384MB by default and that is on top of
> the MAX memory setting which is only for the memory pool. Then you need
> memory for the OS and any other apps that may be running on the machine.
> If you have 6GB total then I would not set the Max memory any higher than
> 5.0GB. Maybe even less if there are other apps on the server.
Thanks. I have the max memory usage set to 5 gig. This server is only a
SQL Server box, with nothing else on it.

Memory usage 98% is it a bad thing?

I am using Spotlight to monitor my servers.
I see that memory is pegged, and the display shows a memory alert (yellow
color instead of green). Actual ram shows usage as 5.67 gig of 5.75 gig.
Virtual shows 2gig free.
All other process look low.
This server is a manufacturing system that takes job requests from the web.
We are a check printing house so we crunch allot of postscript as a "job"
that gets sent to one of our big Xerox printers.
Is this something to be concerned with? System has been up for weeks with
out a reboot and I like it that way. :)Stephen Russell wrote:
> I am using Spotlight to monitor my servers.
> I see that memory is pegged, and the display shows a memory alert
> (yellow color instead of green). Actual ram shows usage as 5.67 gig
> of 5.75 gig. Virtual shows 2gig free.
> All other process look low.
> This server is a manufacturing system that takes job requests from
> the web. We are a check printing house so we crunch allot of
> postscript as a "job" that gets sent to one of our big Xerox printers.
> Is this something to be concerned with? System has been up for weeks
> with out a reboot and I like it that way. :)
If you are using the AWE ENabled option with SQL Server, you need to
specify the "Max Server Memory" for SQL Server to prevent it from using
all available RAM on the server. Make sure you leave enough RAM for the
OS and any other services running on the server.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> If you are using the AWE ENabled option with SQL Server, you need to
> specify the "Max Server Memory" for SQL Server to prevent it from using
> all available RAM on the server. Make sure you leave enough RAM for the
OS
> and any other services running on the server.
Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
machine. My event log has allot of messages for paging errors. I can
restart the server tomorrow before start of business day. I have to give
my
b2b client 12 hrs notice, and that has been delivered.|||If you really are using AWE then that is still not enough left for the OS.
SQL Server MemToLeave needs up to 384MB by default and that is on top of the
MAX memory setting which is only for the memory pool. Then you need memory
for the OS and any other apps that may be running on the machine. If you
have 6GB total then I would not set the Max memory any higher than 5.0GB.
Maybe even less if there are other apps on the server.
--
Andrew J. Kelly SQL MVP
"Stephen Russell" <srussell@.lotmate.com> wrote in message
news:%235FY6OpoFHA.3984@.TK2MSFTNGP10.phx.gbl...
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
>> If you are using the AWE ENabled option with SQL Server, you need to
>> specify the "Max Server Memory" for SQL Server to prevent it from using
>> all available RAM on the server. Make sure you leave enough RAM for the
> OS
>> and any other services running on the server.
> Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
> machine. My event log has allot of messages for paging errors. I can
> restart the server tomorrow before start of business day. I have to give
> my
> b2b client 12 hrs notice, and that has been delivered.
>
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23mwUbdpoFHA.420@.TK2MSFTNGP09.phx.gbl...
> If you really are using AWE then that is still not enough left for the OS.
> SQL Server MemToLeave needs up to 384MB by default and that is on top of
> the MAX memory setting which is only for the memory pool. Then you need
> memory for the OS and any other apps that may be running on the machine.
> If you have 6GB total then I would not set the Max memory any higher than
> 5.0GB. Maybe even less if there are other apps on the server.
Thanks. I have the max memory usage set to 5 gig. This server is only a
SQL Server box, with nothing else on it.

Memory usage

We have about 40 SQL Servers in our environment, and none of them use 2 GB o
f
RAM - in fact they all use between 1.6 and 1.7 GB.
Our configuration option is set to dynamically use memory - and our
databases are as large as 100GB.
Any ideas?How much physical RAM is in the machines?
Himanshu wrote:
> We have about 40 SQL Servers in our environment, and none of them use 2 GB
of
> RAM - in fact they all use between 1.6 and 1.7 GB.
> Our configuration option is set to dynamically use memory - and our
> databases are as large as 100GB.
> Any ideas?|||All our machines have either 3GB or 4GB of physical RAM
"davconts@.gmail.com" wrote:

> How much physical RAM is in the machines?
>
> Himanshu wrote:
>|||How are you measuring the memory allocation?
And have you used the /3gb start up parameter on the boxes with 4GB?
What you are reading is about right for the 3GB boxes -2Gb for SQL, 1GB for
the OS. The /3GB option will give SQL Server 3GB on the boxes with 4GB
memory.
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Himanshu" <Himanshu@.discussions.microsoft.com> wrote in message
news:BC386A30-D58F-4D9B-923F-29EBD5884477@.microsoft.com...[vbcol=seagreen]
> All our machines have either 3GB or 4GB of physical RAM
> "davconts@.gmail.com" wrote:
>|||Himanshu wrote:
> We have about 40 SQL Servers in our environment, and none of them use 2 GB
of
> RAM - in fact they all use between 1.6 and 1.7 GB.
> Our configuration option is set to dynamically use memory - and our
> databases are as large as 100GB.
> Any ideas?
>
What version of SQL server and Windows are you running? Standard SQL
server 2000 is limited to 2GB and in real life it's normally using max
~1,8 GB.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||SQL Server will always reserve up to 384MB of memory at start up for the
MemToLeave portion of memory. So if you are using Task Manager to view
memory usage it looks like SQL Server only uses about 1.7GB and this is
normal.
http://msdn.microsoft.com/library/d...ev_01262004.asp
--
Andrew J. Kelly SQL MVP
"Himanshu" <Himanshu@.discussions.microsoft.com> wrote in message
news:1ECD2B49-A3C1-4466-A752-56BF9515502A@.microsoft.com...
> We have about 40 SQL Servers in our environment, and none of them use 2 GB
> of
> RAM - in fact they all use between 1.6 and 1.7 GB.
> Our configuration option is set to dynamically use memory - and our
> databases are as large as 100GB.
> Any ideas?|||Thank you all for your responses. We have SQL 2000 Standard running on
Windows 2000 Server.
It is possible configure SQL 2000 Standard to use 3 GB?
"Himanshu" wrote:

> We have about 40 SQL Servers in our environment, and none of them use 2 GB
of
> RAM - in fact they all use between 1.6 and 1.7 GB.
> Our configuration option is set to dynamically use memory - and our
> databases are as large as 100GB.
> Any ideas?|||No, that configuration is limited to 2 GB.
See:
http://www.sql-server-performance.c...nfiguration.asp
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Himanshu" <Himanshu@.discussions.microsoft.com> wrote in message
news:A7CCDE8F-1B2E-4C7A-867A-86891BF39F6C@.microsoft.com...[vbcol=seagreen]
> Thank you all for your responses. We have SQL 2000 Standard running on
> Windows 2000 Server.
> It is possible configure SQL 2000 Standard to use 3 GB?
>
> "Himanshu" wrote:
>

Memory usage

We have about 40 SQL Servers in our environment, and none of them use 2 GB of
RAM - in fact they all use between 1.6 and 1.7 GB.
Our configuration option is set to dynamically use memory - and our
databases are as large as 100GB.
Any ideas?How much physical RAM is in the machines?
Himanshu wrote:
> We have about 40 SQL Servers in our environment, and none of them use 2 GB of
> RAM - in fact they all use between 1.6 and 1.7 GB.
> Our configuration option is set to dynamically use memory - and our
> databases are as large as 100GB.
> Any ideas?|||All our machines have either 3GB or 4GB of physical RAM
"davconts@.gmail.com" wrote:
> How much physical RAM is in the machines?
>
> Himanshu wrote:
> > We have about 40 SQL Servers in our environment, and none of them use 2 GB of
> > RAM - in fact they all use between 1.6 and 1.7 GB.
> >
> > Our configuration option is set to dynamically use memory - and our
> > databases are as large as 100GB.
> >
> > Any ideas?
>|||How are you measuring the memory allocation?
And have you used the /3gb start up parameter on the boxes with 4GB?
What you are reading is about right for the 3GB boxes -2Gb for SQL, 1GB for
the OS. The /3GB option will give SQL Server 3GB on the boxes with 4GB
memory.
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Himanshu" <Himanshu@.discussions.microsoft.com> wrote in message
news:BC386A30-D58F-4D9B-923F-29EBD5884477@.microsoft.com...
> All our machines have either 3GB or 4GB of physical RAM
> "davconts@.gmail.com" wrote:
>> How much physical RAM is in the machines?
>>
>> Himanshu wrote:
>> > We have about 40 SQL Servers in our environment, and none of them use 2
>> > GB of
>> > RAM - in fact they all use between 1.6 and 1.7 GB.
>> >
>> > Our configuration option is set to dynamically use memory - and our
>> > databases are as large as 100GB.
>> >
>> > Any ideas?
>>|||This is a multi-part message in MIME format.
--000104030503020007090500
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Himanshu wrote:
> We have about 40 SQL Servers in our environment, and none of them use 2 GB of
> RAM - in fact they all use between 1.6 and 1.7 GB.
> Our configuration option is set to dynamically use memory - and our
> databases are as large as 100GB.
> Any ideas?
>
What version of SQL server and Windows are you running? Standard SQL
server 2000 is limited to 2GB and in real life it's normally using max
~1,8 GB.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--000104030503020007090500
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Himanshu wrote:
<blockquote cite="mid1ECD2B49-A3C1-4466-A752-56BF9515502A@.microsoft.com"
type="cite">
<pre wrap="">We have about 40 SQL Servers in our environment, and none of them use 2 GB of
RAM - in fact they all use between 1.6 and 1.7 GB.
Our configuration option is set to dynamically use memory - and our
databases are as large as 100GB.
Any ideas?
</pre>
</blockquote>
<font size="-1"><font face="Arial">What version of SQL server and
Windows are you running? Standard SQL server 2000 is limited to 2GB and
in real life it's normally using max ~1,8 GB.<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--000104030503020007090500--|||SQL Server will always reserve up to 384MB of memory at start up for the
MemToLeave portion of memory. So if you are using Task Manager to view
memory usage it looks like SQL Server only uses about 1.7GB and this is
normal.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqldev/html/sqldev_01262004.asp
--
Andrew J. Kelly SQL MVP
"Himanshu" <Himanshu@.discussions.microsoft.com> wrote in message
news:1ECD2B49-A3C1-4466-A752-56BF9515502A@.microsoft.com...
> We have about 40 SQL Servers in our environment, and none of them use 2 GB
> of
> RAM - in fact they all use between 1.6 and 1.7 GB.
> Our configuration option is set to dynamically use memory - and our
> databases are as large as 100GB.
> Any ideas?|||Thank you all for your responses. We have SQL 2000 Standard running on
Windows 2000 Server.
It is possible configure SQL 2000 Standard to use 3 GB?
"Himanshu" wrote:
> We have about 40 SQL Servers in our environment, and none of them use 2 GB of
> RAM - in fact they all use between 1.6 and 1.7 GB.
> Our configuration option is set to dynamically use memory - and our
> databases are as large as 100GB.
> Any ideas?|||No, that configuration is limited to 2 GB.
See:
http://www.sql-server-performance.com/jc_system_storage_configuration.asp
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Himanshu" <Himanshu@.discussions.microsoft.com> wrote in message
news:A7CCDE8F-1B2E-4C7A-867A-86891BF39F6C@.microsoft.com...
> Thank you all for your responses. We have SQL 2000 Standard running on
> Windows 2000 Server.
> It is possible configure SQL 2000 Standard to use 3 GB?
>
> "Himanshu" wrote:
>> We have about 40 SQL Servers in our environment, and none of them use 2
>> GB of
>> RAM - in fact they all use between 1.6 and 1.7 GB.
>> Our configuration option is set to dynamically use memory - and our
>> databases are as large as 100GB.
>> Any ideas?

Memory question

Hi,
I just started at a new company and have been tasked with reviewing the
configurations on some troubled servers. One thing I noticed that seems odd
in the sp_configure output is that the min memory per query (1024 MB) is
actutally higher than the max server memory (344 MB). Which setting has
priority or are they unrelated? Is this okay?
As a background note, this is a server with two instances. The primary
instance has it's max server memory set to 1024.
Thanks for your input.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200604/1Hi Michael
The min memory per query value is normally in kilobytes and the default is
1024KB do you have the correct value?
John
"michaelg via SQLMonster.com" wrote:
> Hi,
> I just started at a new company and have been tasked with reviewing the
> configurations on some troubled servers. One thing I noticed that seems odd
> in the sp_configure output is that the min memory per query (1024 MB) is
> actutally higher than the max server memory (344 MB). Which setting has
> priority or are they unrelated? Is this okay?
> As a background note, this is a server with two instances. The primary
> instance has it's max server memory set to 1024.
> Thanks for your input.
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200604/1
>|||Hi John,
Yes, I see where I missed the MB vs KB in the output.
Thanks for the assistance.
Michael
John Bell wrote:
>Hi Michael
>The min memory per query value is normally in kilobytes and the default is
>1024KB do you have the correct value?
>John
>> Hi,
>[quoted text clipped - 8 lines]
>> Thanks for your input.
--
Message posted via http://www.sqlmonster.com

Memory question

Hi,
I just started at a new company and have been tasked with reviewing the
configurations on some troubled servers. One thing I noticed that seems odd
in the sp_configure output is that the min memory per query (1024 MB) is
actutally higher than the max server memory (344 MB). Which setting has
priority or are they unrelated? Is this okay?
As a background note, this is a server with two instances. The primary
instance has it's max server memory set to 1024.
Thanks for your input.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200604/1Hi Michael
The min memory per query value is normally in kilobytes and the default is
1024KB do you have the correct value?
John
"michaelg via droptable.com" wrote:

> Hi,
> I just started at a new company and have been tasked with reviewing the
> configurations on some troubled servers. One thing I noticed that seems od
d
> in the sp_configure output is that the min memory per query (1024 MB) is
> actutally higher than the max server memory (344 MB). Which setting has
> priority or are they unrelated? Is this okay?
> As a background note, this is a server with two instances. The primary
> instance has it's max server memory set to 1024.
> Thanks for your input.
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200604/1
>|||Hi John,
Yes, I see where I missed the MB vs KB in the output.
Thanks for the assistance.
Michael
John Bell wrote:[vbcol=seagreen]
>Hi Michael
>The min memory per query value is normally in kilobytes and the default is
>1024KB do you have the correct value?
>John
>
>[quoted text clipped - 8 lines]
Message posted via http://www.droptable.com

memory on server

I have an application that is used 85 % of the time by 25 % of the people in
the organization.
we have three servers, all having 2000 server and sql 2000 server the main
one is on SP2 and the two terminal servers have sp4
main server has 2048 meg of ram and ts1 has 3840 meg and ts2 has 2048 meg of
ram in it.
the main server utilization runs anywhere from 20% to 100%. I am purposing
adding another 2048 in the main server, is that enough?
Kevin
kevins (kevins@.discussions.microsoft.com) writes:
> I have an application that is used 85 % of the time by 25 % of the
> people in the organization.
> we have three servers, all having 2000 server and sql 2000 server the
> main one is on SP2 and the two terminal servers have sp4 main server has
> 2048 meg of ram and ts1 has 3840 meg and ts2 has 2048 meg of ram in it.
> the main server utilization runs anywhere from 20% to 100%. I am
> purposing adding another 2048 in the main server, is that enough?
When it comes to memory for SQL Server, too much is not enough! :-)
Here is the deal: SQL Server loves cache. The more data it can hold in
cache, the less often it has to read from disk. Thus, once SQL Server
has maxed out on memory, it will stay there (unless there is pressure
from other applications.)
Thus, if you get another 2 GB of memory, you may see that SQL Server
till maxes out. This all depends on your databasees and your application.
If you have a 100 GB database of which all data is accessed at some
point during the day, you will have to access disk accesses. On the
other hand, if your only database is 2GB, those extra 2GB will not have
that much effect, as you already have the database in memory.
Note also that you need Enterprise Edition to be able to make use from
more than 2GB memory. There are also switches in Windows you need to set,
to able to use this memory.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

memory on server

I have an application that is used 85 % of the time by 25 % of the people in
the organization.
we have three servers, all having 2000 server and sql 2000 server the main
one is on SP2 and the two terminal servers have sp4
main server has 2048 meg of ram and ts1 has 3840 meg and ts2 has 2048 meg of
ram in it.
the main server utilization runs anywhere from 20% to 100%. I am purposing
adding another 2048 in the main server, is that enough?
Kevinkevins (kevins@.discussions.microsoft.com) writes:
> I have an application that is used 85 % of the time by 25 % of the
> people in the organization.
> we have three servers, all having 2000 server and sql 2000 server the
> main one is on SP2 and the two terminal servers have sp4 main server has
> 2048 meg of ram and ts1 has 3840 meg and ts2 has 2048 meg of ram in it.
> the main server utilization runs anywhere from 20% to 100%. I am
> purposing adding another 2048 in the main server, is that enough?
When it comes to memory for SQL Server, too much is not enough! :-)
Here is the deal: SQL Server loves cache. The more data it can hold in
cache, the less often it has to read from disk. Thus, once SQL Server
has maxed out on memory, it will stay there (unless there is pressure
from other applications.)
Thus, if you get another 2 GB of memory, you may see that SQL Server
till maxes out. This all depends on your databasees and your application.
If you have a 100 GB database of which all data is accessed at some
point during the day, you will have to access disk accesses. On the
other hand, if your only database is 2GB, those extra 2GB will not have
that much effect, as you already have the database in memory.
Note also that you need Enterprise Edition to be able to make use from
more than 2GB memory. There are also switches in Windows you need to set,
to able to use this memory.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

memory on server

I have an application that is used 85 % of the time by 25 % of the people in
the organization.
we have three servers, all having 2000 server and sql 2000 server the main
one is on SP2 and the two terminal servers have sp4
main server has 2048 meg of ram and ts1 has 3840 meg and ts2 has 2048 meg of
ram in it.
the main server utilization runs anywhere from 20% to 100%. I am purposing
adding another 2048 in the main server, is that enough?
Kevinkevins (kevins@.discussions.microsoft.com) writes:
> I have an application that is used 85 % of the time by 25 % of the
> people in the organization.
> we have three servers, all having 2000 server and sql 2000 server the
> main one is on SP2 and the two terminal servers have sp4 main server has
> 2048 meg of ram and ts1 has 3840 meg and ts2 has 2048 meg of ram in it.
> the main server utilization runs anywhere from 20% to 100%. I am
> purposing adding another 2048 in the main server, is that enough?
When it comes to memory for SQL Server, too much is not enough! :-)
Here is the deal: SQL Server loves cache. The more data it can hold in
cache, the less often it has to read from disk. Thus, once SQL Server
has maxed out on memory, it will stay there (unless there is pressure
from other applications.)
Thus, if you get another 2 GB of memory, you may see that SQL Server
till maxes out. This all depends on your databasees and your application.
If you have a 100 GB database of which all data is accessed at some
point during the day, you will have to access disk accesses. On the
other hand, if your only database is 2GB, those extra 2GB will not have
that much effect, as you already have the database in memory.
Note also that you need Enterprise Edition to be able to make use from
more than 2GB memory. There are also switches in Windows you need to set,
to able to use this memory.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp