SQL Server 2000 SP4
How can I get "Transactions per second" and "write transactions percent"
values for a production database ?. I tried to find in the profiler but did
not see an event that would give me this info.
Thanks for any help.Those come from Perfmon not profiler.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:1456F10A-B293-48C1-9AFF-BB3FB5906F76@.microsoft.com...
> SQL Server 2000 SP4
> How can I get "Transactions per second" and "write transactions percent"
> values for a production database ?. I tried to find in the profiler but
> did
> not see an event that would give me this info.
> Thanks for any help.
>|||Thanks Andrew............ What do I need to choose in Performance
Monitoring ?
"Andrew J. Kelly" wrote:
> Those come from Perfmon not profiler.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "DXC" <DXC@.discussions.microsoft.com> wrote in message
> news:1456F10A-B293-48C1-9AFF-BB3FB5906F76@.microsoft.com...
> > SQL Server 2000 SP4
> >
> > How can I get "Transactions per second" and "write transactions percent"
> > values for a production database ?. I tried to find in the profiler but
> > did
> > not see an event that would give me this info.
> >
> > Thanks for any help.
> >
>|||Well the databases counters will have Transactions Per Second for each
database but I don't know what you mean by the other. If you want to see the
difference between requests and things that actually begin a transaction you
can monitor Batch Requests Per Second and Trans Per Second.
Some of these may be of interest:
http://www.sql-server-performance.com/sql_server_performance_audit10.asp
Performance Audit
http://www.microsoft.com/technet/prodtechnol/sql/2005/library/operations.mspx
Performance WP's
http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
http://www.sql-server-performance.com/sql_server_performance_audit.asp
Hardware Performance CheckList
http://www.sql-server-performance.com/best_sql_server_performance_tips.asp
SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=224587 Troubleshooting App
Performance
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_24u1.asp
Disk Monitoring
http://sqldev.net/misc/WaitTypes.htm
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:8515ED62-75BF-4B44-AF03-6112174664A7@.microsoft.com...
> Thanks Andrew............ What do I need to choose in Performance
> Monitoring ?
>
> "Andrew J. Kelly" wrote:
>> Those come from Perfmon not profiler.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "DXC" <DXC@.discussions.microsoft.com> wrote in message
>> news:1456F10A-B293-48C1-9AFF-BB3FB5906F76@.microsoft.com...
>> > SQL Server 2000 SP4
>> >
>> > How can I get "Transactions per second" and "write transactions
>> > percent"
>> > values for a production database ?. I tried to find in the profiler but
>> > did
>> > not see an event that would give me this info.
>> >
>> > Thanks for any help.
>> >
>>|||Thanks.................
"Andrew J. Kelly" wrote:
> Well the databases counters will have Transactions Per Second for each
> database but I don't know what you mean by the other. If you want to see the
> difference between requests and things that actually begin a transaction you
> can monitor Batch Requests Per Second and Trans Per Second.
> Some of these may be of interest:
> http://www.sql-server-performance.com/sql_server_performance_audit10.asp
> Performance Audit
> http://www.microsoft.com/technet/prodtechnol/sql/2005/library/operations.mspx
> Performance WP's
> http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
> http://www.sql-server-performance.com/sql_server_performance_audit.asp
> Hardware Performance CheckList
> http://www.sql-server-performance.com/best_sql_server_performance_tips.asp
> SQL 2000 Performance tuning tips
> http://www.support.microsoft.com/?id=224587 Troubleshooting App
> Performance
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_24u1.asp
> Disk Monitoring
> http://sqldev.net/misc/WaitTypes.htm
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "DXC" <DXC@.discussions.microsoft.com> wrote in message
> news:8515ED62-75BF-4B44-AF03-6112174664A7@.microsoft.com...
> > Thanks Andrew............ What do I need to choose in Performance
> > Monitoring ?
> >
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Those come from Perfmon not profiler.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
> >>
> >> "DXC" <DXC@.discussions.microsoft.com> wrote in message
> >> news:1456F10A-B293-48C1-9AFF-BB3FB5906F76@.microsoft.com...
> >> > SQL Server 2000 SP4
> >> >
> >> > How can I get "Transactions per second" and "write transactions
> >> > percent"
> >> > values for a production database ?. I tried to find in the profiler but
> >> > did
> >> > not see an event that would give me this info.
> >> >
> >> > Thanks for any help.
> >> >
> >>
> >>
>
Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts
Friday, March 23, 2012
Monday, March 12, 2012
Processing cubes in Analysis Services 2000
I need to write an application to process Analysis Services 2000 cubes but I can't use DSO because there isn't a 64 bit version available of this library.
Can I use AMO (Analysis Management Objects) for administering Analysis Services 2000? Is there another solution?
Thanks in advance
Daniele
Your only option is to find a 32-bit workstation and run your DSO application from there. This is a restriction of AS2K. Sorry.
_-_-_ Dave
Processing cubes in Analysis Services 2000
I'm working with Analysis Services 2000 (SP4) on a 64 bit Windows Server 2003 where I have installed the framework 2.0.
I need to write an application to process Analysis Services 2000 cubes but I can't use DSO because there isn't a 64 bit version available of this library.
Can I use AMO (Analysis Management Objects) for administering Analysis Services 2000? Is there another solution?
Thanks in advance
DanieleUnfortunately you cannot use AMO against Analysis Services 2000.
You can use DSO to remotely process Analysis Services object from another 32bit machine.
By the way you can use separate Redistributable component to install DSO
http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en
Look for
"Microsoft SQL Server 2005 Backward Compatibility Components "
This posting is provided "AS IS" with no warranties, and confers no rights.
I need to write an application to process Analysis Services 2000 cubes but I can't use DSO because there isn't a 64 bit version available of this library.
Can I use AMO (Analysis Management Objects) for administering Analysis Services 2000? Is there another solution?
Thanks in advance
DanieleUnfortunately you cannot use AMO against Analysis Services 2000.
You can use DSO to remotely process Analysis Services object from another 32bit machine.
By the way you can use separate Redistributable component to install DSO
http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en
Look for
"Microsoft SQL Server 2005 Backward Compatibility Components "
Edward Melomed (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
ProcessId remains in memory?
Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
Server 2003 and notice that applications that have been running during the
day, have more and more ProcessID's for the same application. The
applications sometimes is closed by the user, sometimes crash, but usually
they will (after a refresh of EM) not show. I see the Host name in the list
of items in Process Info, and now see that each machine has multiple entries
for the same application. It seems that the process Info remains fixed in
server memory.
Anyone know why this should have just started to happed. As far as I can
tell, only the clients would have any updates (MS Updates and fixes) the
client application has not changed apart from cosmetically. The connection
is through ADODB MDAC 2.8
Thanks for the time. Hope this is clear.
The only times I have seen behavior like what I think you are
describing it was always a problem with the application. Rather than
using the connection it already had open, it kept opening a new
connection with each command. It was easy to see when monitoring
using Performance Monitor, watching the number of connections
climbing.
Which is not to say that your problem is the same, but it sure sounds
familiar.
Roy Harvey
Beacon Falls, CT
On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
<hughessatmdnationwide.co.uk> wrote:
>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
>Server 2003 and notice that applications that have been running during the
>day, have more and more ProcessID's for the same application. The
>applications sometimes is closed by the user, sometimes crash, but usually
>they will (after a refresh of EM) not show. I see the Host name in the list
>of items in Process Info, and now see that each machine has multiple entries
>for the same application. It seems that the process Info remains fixed in
>server memory.
>Anyone know why this should have just started to happed. As far as I can
>tell, only the clients would have any updates (MS Updates and fixes) the
>client application has not changed apart from cosmetically. The connection
>is through ADODB MDAC 2.8
>Thanks for the time. Hope this is clear.
|||Thanks, I believe that you are right, one of our developers did m ake a
change to the application, and did not free a query after use. This I think
has kept the connections open. I thought that SQL Server would release
unused connections after a period of inactivity but I guess that is not the
case. Oh well back to the drawing board
thanks for the input.
regards
steve
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:6jpp02dg831g66klbjtrt1isq4c2jquldk@.4ax.com... [vbcol=seagreen]
> The only times I have seen behavior like what I think you are
> describing it was always a problem with the application. Rather than
> using the connection it already had open, it kept opening a new
> connection with each command. It was easy to see when monitoring
> using Performance Monitor, watching the number of connections
> climbing.
> Which is not to say that your problem is the same, but it sure sounds
> familiar.
> Roy Harvey
> Beacon Falls, CT
>
> On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
> <hughessatmdnationwide.co.uk> wrote:
Server 2003 and notice that applications that have been running during the
day, have more and more ProcessID's for the same application. The
applications sometimes is closed by the user, sometimes crash, but usually
they will (after a refresh of EM) not show. I see the Host name in the list
of items in Process Info, and now see that each machine has multiple entries
for the same application. It seems that the process Info remains fixed in
server memory.
Anyone know why this should have just started to happed. As far as I can
tell, only the clients would have any updates (MS Updates and fixes) the
client application has not changed apart from cosmetically. The connection
is through ADODB MDAC 2.8
Thanks for the time. Hope this is clear.
The only times I have seen behavior like what I think you are
describing it was always a problem with the application. Rather than
using the connection it already had open, it kept opening a new
connection with each command. It was easy to see when monitoring
using Performance Monitor, watching the number of connections
climbing.
Which is not to say that your problem is the same, but it sure sounds
familiar.
Roy Harvey
Beacon Falls, CT
On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
<hughessatmdnationwide.co.uk> wrote:
>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
>Server 2003 and notice that applications that have been running during the
>day, have more and more ProcessID's for the same application. The
>applications sometimes is closed by the user, sometimes crash, but usually
>they will (after a refresh of EM) not show. I see the Host name in the list
>of items in Process Info, and now see that each machine has multiple entries
>for the same application. It seems that the process Info remains fixed in
>server memory.
>Anyone know why this should have just started to happed. As far as I can
>tell, only the clients would have any updates (MS Updates and fixes) the
>client application has not changed apart from cosmetically. The connection
>is through ADODB MDAC 2.8
>Thanks for the time. Hope this is clear.
|||Thanks, I believe that you are right, one of our developers did m ake a
change to the application, and did not free a query after use. This I think
has kept the connections open. I thought that SQL Server would release
unused connections after a period of inactivity but I guess that is not the
case. Oh well back to the drawing board
thanks for the input.
regards
steve
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:6jpp02dg831g66klbjtrt1isq4c2jquldk@.4ax.com... [vbcol=seagreen]
> The only times I have seen behavior like what I think you are
> describing it was always a problem with the application. Rather than
> using the connection it already had open, it kept opening a new
> connection with each command. It was easy to see when monitoring
> using Performance Monitor, watching the number of connections
> climbing.
> Which is not to say that your problem is the same, but it sure sounds
> familiar.
> Roy Harvey
> Beacon Falls, CT
>
> On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
> <hughessatmdnationwide.co.uk> wrote:
ProcessId remains in memory?
Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
Server 2003 and notice that applications that have been running during the
day, have more and more ProcessID's for the same application. The
applications sometimes is closed by the user, sometimes crash, but usually
they will (after a refresh of EM) not show. I see the Host name in the list
of items in Process Info, and now see that each machine has multiple entries
for the same application. It seems that the process Info remains fixed in
server memory.
Anyone know why this should have just started to happed. As far as I can
tell, only the clients would have any updates (MS Updates and fixes) the
client application has not changed apart from cosmetically. The connection
is through ADODB MDAC 2.8
Thanks for the time. Hope this is clear.The only times I have seen behavior like what I think you are
describing it was always a problem with the application. Rather than
using the connection it already had open, it kept opening a new
connection with each command. It was easy to see when monitoring
using Performance Monitor, watching the number of connections
climbing.
Which is not to say that your problem is the same, but it sure sounds
familiar.
Roy Harvey
Beacon Falls, CT
On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
<hughessatmdnationwide.co.uk> wrote:
>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
>Server 2003 and notice that applications that have been running during the
>day, have more and more ProcessID's for the same application. The
>applications sometimes is closed by the user, sometimes crash, but usually
>they will (after a refresh of EM) not show. I see the Host name in the list
>of items in Process Info, and now see that each machine has multiple entries
>for the same application. It seems that the process Info remains fixed in
>server memory.
>Anyone know why this should have just started to happed. As far as I can
>tell, only the clients would have any updates (MS Updates and fixes) the
>client application has not changed apart from cosmetically. The connection
>is through ADODB MDAC 2.8
>Thanks for the time. Hope this is clear.|||Thanks, I believe that you are right, one of our developers did m ake a
change to the application, and did not free a query after use. This I think
has kept the connections open. I thought that SQL Server would release
unused connections after a period of inactivity but I guess that is not the
case. Oh well back to the drawing board
thanks for the input.
regards
steve
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:6jpp02dg831g66klbjtrt1isq4c2jquldk@.4ax.com...
> The only times I have seen behavior like what I think you are
> describing it was always a problem with the application. Rather than
> using the connection it already had open, it kept opening a new
> connection with each command. It was easy to see when monitoring
> using Performance Monitor, watching the number of connections
> climbing.
> Which is not to say that your problem is the same, but it sure sounds
> familiar.
> Roy Harvey
> Beacon Falls, CT
>
> On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
> <hughessatmdnationwide.co.uk> wrote:
>>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on
>>Windows
>>Server 2003 and notice that applications that have been running during the
>>day, have more and more ProcessID's for the same application. The
>>applications sometimes is closed by the user, sometimes crash, but usually
>>they will (after a refresh of EM) not show. I see the Host name in the
>>list
>>of items in Process Info, and now see that each machine has multiple
>>entries
>>for the same application. It seems that the process Info remains fixed in
>>server memory.
>>Anyone know why this should have just started to happed. As far as I can
>>tell, only the clients would have any updates (MS Updates and fixes) the
>>client application has not changed apart from cosmetically. The connection
>>is through ADODB MDAC 2.8
>>Thanks for the time. Hope this is clear.
Server 2003 and notice that applications that have been running during the
day, have more and more ProcessID's for the same application. The
applications sometimes is closed by the user, sometimes crash, but usually
they will (after a refresh of EM) not show. I see the Host name in the list
of items in Process Info, and now see that each machine has multiple entries
for the same application. It seems that the process Info remains fixed in
server memory.
Anyone know why this should have just started to happed. As far as I can
tell, only the clients would have any updates (MS Updates and fixes) the
client application has not changed apart from cosmetically. The connection
is through ADODB MDAC 2.8
Thanks for the time. Hope this is clear.The only times I have seen behavior like what I think you are
describing it was always a problem with the application. Rather than
using the connection it already had open, it kept opening a new
connection with each command. It was easy to see when monitoring
using Performance Monitor, watching the number of connections
climbing.
Which is not to say that your problem is the same, but it sure sounds
familiar.
Roy Harvey
Beacon Falls, CT
On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
<hughessatmdnationwide.co.uk> wrote:
>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
>Server 2003 and notice that applications that have been running during the
>day, have more and more ProcessID's for the same application. The
>applications sometimes is closed by the user, sometimes crash, but usually
>they will (after a refresh of EM) not show. I see the Host name in the list
>of items in Process Info, and now see that each machine has multiple entries
>for the same application. It seems that the process Info remains fixed in
>server memory.
>Anyone know why this should have just started to happed. As far as I can
>tell, only the clients would have any updates (MS Updates and fixes) the
>client application has not changed apart from cosmetically. The connection
>is through ADODB MDAC 2.8
>Thanks for the time. Hope this is clear.|||Thanks, I believe that you are right, one of our developers did m ake a
change to the application, and did not free a query after use. This I think
has kept the connections open. I thought that SQL Server would release
unused connections after a period of inactivity but I guess that is not the
case. Oh well back to the drawing board
thanks for the input.
regards
steve
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:6jpp02dg831g66klbjtrt1isq4c2jquldk@.4ax.com...
> The only times I have seen behavior like what I think you are
> describing it was always a problem with the application. Rather than
> using the connection it already had open, it kept opening a new
> connection with each command. It was easy to see when monitoring
> using Performance Monitor, watching the number of connections
> climbing.
> Which is not to say that your problem is the same, but it sure sounds
> familiar.
> Roy Harvey
> Beacon Falls, CT
>
> On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
> <hughessatmdnationwide.co.uk> wrote:
>>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on
>>Windows
>>Server 2003 and notice that applications that have been running during the
>>day, have more and more ProcessID's for the same application. The
>>applications sometimes is closed by the user, sometimes crash, but usually
>>they will (after a refresh of EM) not show. I see the Host name in the
>>list
>>of items in Process Info, and now see that each machine has multiple
>>entries
>>for the same application. It seems that the process Info remains fixed in
>>server memory.
>>Anyone know why this should have just started to happed. As far as I can
>>tell, only the clients would have any updates (MS Updates and fixes) the
>>client application has not changed apart from cosmetically. The connection
>>is through ADODB MDAC 2.8
>>Thanks for the time. Hope this is clear.
ProcessId remains in memory?
Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
Server 2003 and notice that applications that have been running during the
day, have more and more ProcessID's for the same application. The
applications sometimes is closed by the user, sometimes crash, but usually
they will (after a refresh of EM) not show. I see the Host name in the list
of items in Process Info, and now see that each machine has multiple entries
for the same application. It seems that the process Info remains fixed in
server memory.
Anyone know why this should have just started to happed. As far as I can
tell, only the clients would have any updates (MS Updates and fixes) the
client application has not changed apart from cosmetically. The connection
is through ADODB MDAC 2.8
Thanks for the time. Hope this is clear.The only times I have seen behavior like what I think you are
describing it was always a problem with the application. Rather than
using the connection it already had open, it kept opening a new
connection with each command. It was easy to see when monitoring
using Performance Monitor, watching the number of connections
climbing.
Which is not to say that your problem is the same, but it sure sounds
familiar.
Roy Harvey
Beacon Falls, CT
On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
<hughessatmdnationwide.co.uk> wrote:
>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
>Server 2003 and notice that applications that have been running during the
>day, have more and more ProcessID's for the same application. The
>applications sometimes is closed by the user, sometimes crash, but usually
>they will (after a refresh of EM) not show. I see the Host name in the list
>of items in Process Info, and now see that each machine has multiple entrie
s
>for the same application. It seems that the process Info remains fixed in
>server memory.
>Anyone know why this should have just started to happed. As far as I can
>tell, only the clients would have any updates (MS Updates and fixes) the
>client application has not changed apart from cosmetically. The connection
>is through ADODB MDAC 2.8
>Thanks for the time. Hope this is clear.|||Thanks, I believe that you are right, one of our developers did m ake a
change to the application, and did not free a query after use. This I think
has kept the connections open. I thought that SQL Server would release
unused connections after a period of inactivity but I guess that is not the
case. Oh well back to the drawing board
thanks for the input.
regards
steve
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:6jpp02dg831g66klbjtrt1isq4c2jquldk@.
4ax.com...[vbcol=seagreen]
> The only times I have seen behavior like what I think you are
> describing it was always a problem with the application. Rather than
> using the connection it already had open, it kept opening a new
> connection with each command. It was easy to see when monitoring
> using Performance Monitor, watching the number of connections
> climbing.
> Which is not to say that your problem is the same, but it sure sounds
> familiar.
> Roy Harvey
> Beacon Falls, CT
>
> On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
> <hughessatmdnationwide.co.uk> wrote:
>
Server 2003 and notice that applications that have been running during the
day, have more and more ProcessID's for the same application. The
applications sometimes is closed by the user, sometimes crash, but usually
they will (after a refresh of EM) not show. I see the Host name in the list
of items in Process Info, and now see that each machine has multiple entries
for the same application. It seems that the process Info remains fixed in
server memory.
Anyone know why this should have just started to happed. As far as I can
tell, only the clients would have any updates (MS Updates and fixes) the
client application has not changed apart from cosmetically. The connection
is through ADODB MDAC 2.8
Thanks for the time. Hope this is clear.The only times I have seen behavior like what I think you are
describing it was always a problem with the application. Rather than
using the connection it already had open, it kept opening a new
connection with each command. It was easy to see when monitoring
using Performance Monitor, watching the number of connections
climbing.
Which is not to say that your problem is the same, but it sure sounds
familiar.
Roy Harvey
Beacon Falls, CT
On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
<hughessatmdnationwide.co.uk> wrote:
>Can anyone help here. I monitor SQL Server EM (2000) SP4 running on Windows
>Server 2003 and notice that applications that have been running during the
>day, have more and more ProcessID's for the same application. The
>applications sometimes is closed by the user, sometimes crash, but usually
>they will (after a refresh of EM) not show. I see the Host name in the list
>of items in Process Info, and now see that each machine has multiple entrie
s
>for the same application. It seems that the process Info remains fixed in
>server memory.
>Anyone know why this should have just started to happed. As far as I can
>tell, only the clients would have any updates (MS Updates and fixes) the
>client application has not changed apart from cosmetically. The connection
>is through ADODB MDAC 2.8
>Thanks for the time. Hope this is clear.|||Thanks, I believe that you are right, one of our developers did m ake a
change to the application, and did not free a query after use. This I think
has kept the connections open. I thought that SQL Server would release
unused connections after a period of inactivity but I guess that is not the
case. Oh well back to the drawing board
thanks for the input.
regards
steve
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:6jpp02dg831g66klbjtrt1isq4c2jquldk@.
4ax.com...[vbcol=seagreen]
> The only times I have seen behavior like what I think you are
> describing it was always a problem with the application. Rather than
> using the connection it already had open, it kept opening a new
> connection with each command. It was easy to see when monitoring
> using Performance Monitor, watching the number of connections
> climbing.
> Which is not to say that your problem is the same, but it sure sounds
> familiar.
> Roy Harvey
> Beacon Falls, CT
>
> On Mon, 6 Mar 2006 12:23:26 -0000, "Steve"
> <hughessatmdnationwide.co.uk> wrote:
>
Friday, March 9, 2012
Processes locking themselves after SP4
Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave Wall
Are you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI
|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
Dave Wall
"zashah@.gmail.com" wrote:
> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>
|||Processes appearing to lock themselves is a change in reporting in SP4, not an actual issue. Basically the process reports itself as a blocking process when it goes to grab disk allocation (as I understand it). The Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on databases up to 400 GB in size.
Originally posted by Dave Wall
Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave Wall
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group/...513ab281?hl=en
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall
|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started to
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
Dave Wall
"Kyle Quinby" wrote:
> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
>
> --
> Kyle Quinby
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message1756427.html
>
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave Wall
Are you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI
|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
Dave Wall
"zashah@.gmail.com" wrote:
> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>
|||Processes appearing to lock themselves is a change in reporting in SP4, not an actual issue. Basically the process reports itself as a blocking process when it goes to grab disk allocation (as I understand it). The Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on databases up to 400 GB in size.
Quote:
Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave Wall
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group/...513ab281?hl=en
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall
|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started to
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
Dave Wall
"Kyle Quinby" wrote:
> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
>
> --
> Kyle Quinby
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message1756427.html
>
Processes locking themselves after SP4
Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
--
Dave WallAre you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
--
Dave Wall
"zashah@.gmail.com" wrote:
> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>|||Hi
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group/microsoft.public.sqlserver.server/msg/b86e343e513ab281?hl=en
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall|||Processes appearing to lock themselves is a change in reporting in SP4,
not an actual issue. Basically the process reports itself as a blocking
process when it goes to grab disk allocation (as I understand it). The
Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on
databases up to 400 GB in size.
Dave Wall wrote:
> *Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL
> Server
> 200 SP4. Users are complaining that the system is running slowly,
> looking at
> the processes, the active processes appear to be blocking themselves.
> The
> configuration of SQL is identical to before and the hardware is the
> same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall *
Kyle Quinby
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1756427.html|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started to
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
--
Dave Wall
"Kyle Quinby" wrote:
> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
> > *Hi All,
> >
> > We've recently rebuilt our failover cluster to Windows 2003 and SQL
> > Server
> > 200 SP4. Users are complaining that the system is running slowly,
> > looking at
> > the processes, the active processes appear to be blocking themselves.
> > The
> > configuration of SQL is identical to before and the hardware is the
> > same,
> > just the OS and the SP version of SQL has changed.
> >
> > Any ideas what might be causing the blocking? I've checked for lock
> > escalation (using profiler) and we're not experiencing it!
> >
> > --
> > Dave Wall *
>
> --
> Kyle Quinby
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message1756427.html
>
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking at
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
--
Dave WallAre you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
--
Dave Wall
"zashah@.gmail.com" wrote:
> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>|||Hi
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group/microsoft.public.sqlserver.server/msg/b86e343e513ab281?hl=en
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall|||Processes appearing to lock themselves is a change in reporting in SP4,
not an actual issue. Basically the process reports itself as a blocking
process when it goes to grab disk allocation (as I understand it). The
Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on
databases up to 400 GB in size.
Dave Wall wrote:
> *Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL
> Server
> 200 SP4. Users are complaining that the system is running slowly,
> looking at
> the processes, the active processes appear to be blocking themselves.
> The
> configuration of SQL is identical to before and the hardware is the
> same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall *
Kyle Quinby
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1756427.html|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started to
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
--
Dave Wall
"Kyle Quinby" wrote:
> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
> > *Hi All,
> >
> > We've recently rebuilt our failover cluster to Windows 2003 and SQL
> > Server
> > 200 SP4. Users are complaining that the system is running slowly,
> > looking at
> > the processes, the active processes appear to be blocking themselves.
> > The
> > configuration of SQL is identical to before and the hardware is the
> > same,
> > just the OS and the SP version of SQL has changed.
> >
> > Any ideas what might be causing the blocking? I've checked for lock
> > escalation (using profiler) and we're not experiencing it!
> >
> > --
> > Dave Wall *
>
> --
> Kyle Quinby
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message1756427.html
>
Processes locking themselves after SP4
Hi All,
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking a
t
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave WallAre you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
Dave Wall
"zashah@.gmail.com" wrote:
> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>|||Hi
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group...
513ab281?hl=en
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall|||Processes appearing to lock themselves is a change in reporting in SP4,
not an actual issue. Basically the process reports itself as a blocking
process when it goes to grab disk allocation (as I understand it). The
Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on
databases up to 400 GB in size.
Dave Wall wrote:
> *Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL
> Server
> 200 SP4. Users are complaining that the system is running slowly,
> looking at
> the processes, the active processes appear to be blocking themselves.
> The
> configuration of SQL is identical to before and the hardware is the
> same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall *
Kyle Quinby
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1756427.html|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started t
o
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
--
Dave Wall
"Kyle Quinby" wrote:
> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
>
> --
> Kyle Quinby
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message1756427.html
>
We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
200 SP4. Users are complaining that the system is running slowly, looking a
t
the processes, the active processes appear to be blocking themselves. The
configuration of SQL is identical to before and the hardware is the same,
just the OS and the SP version of SQL has changed.
Any ideas what might be causing the blocking? I've checked for lock
escalation (using profiler) and we're not experiencing it!
Dave WallAre you using the very latest SP4 for SQL2K? Does your system use RAM
above 4GB and is AWE-enabled?
This may not be the issue I know but better to check rather than
assume. I know the first SP4 release problems didn't necessarily
manifest in the way your system is but you can never be sure ...
ALI|||We're using the patch on SP4 to allow us to run AWE with RAM of 5GB
(restricted from 8GB)
Dave
Dave Wall
"zashah@.gmail.com" wrote:
> Are you using the very latest SP4 for SQL2K? Does your system use RAM
> above 4GB and is AWE-enabled?
> This may not be the issue I know but better to check rather than
> assume. I know the first SP4 release problems didn't necessarily
> manifest in the way your system is but you can never be sure ...
> ALI
>|||Hi
Have a look at this explanation by Santeri Voutilainen from MSFT
http://groups-beta.google.com/group...
513ab281?hl=en
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:B746F00D-1908-4D9B-9934-F35F24304D54@.microsoft.com...
> Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL Server
> 200 SP4. Users are complaining that the system is running slowly, looking
> at
> the processes, the active processes appear to be blocking themselves. The
> configuration of SQL is identical to before and the hardware is the same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall|||Processes appearing to lock themselves is a change in reporting in SP4,
not an actual issue. Basically the process reports itself as a blocking
process when it goes to grab disk allocation (as I understand it). The
Wait Type should display as PAGELATCH IO if I recall correctly.
Took me by surprise too but it isn't an actual blocked process.
As far as performance goes, I haven't seen any performance hits on
databases up to 400 GB in size.
Dave Wall wrote:
> *Hi All,
> We've recently rebuilt our failover cluster to Windows 2003 and SQL
> Server
> 200 SP4. Users are complaining that the system is running slowly,
> looking at
> the processes, the active processes appear to be blocking themselves.
> The
> configuration of SQL is identical to before and the hardware is the
> same,
> just the OS and the SP version of SQL has changed.
> Any ideas what might be causing the blocking? I've checked for lock
> escalation (using profiler) and we're not experiencing it!
> --
> Dave Wall *
Kyle Quinby
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1756427.html|||Thanks Kyle,
and thanks to everyone else for your input. Turns out that while our
networking team assured me that the server had been set up to use PAE it
wasn't entriely true. Once it was set and the server rebooted, SQL started t
o
use the additional memory, IO dropped to nothing (as it can now hold around
1/3 of the DB in memory) and the blocking spids disappeared.
Thanks again for everyones input!
Dave
--
Dave Wall
"Kyle Quinby" wrote:
> Processes appearing to lock themselves is a change in reporting in SP4,
> not an actual issue. Basically the process reports itself as a blocking
> process when it goes to grab disk allocation (as I understand it). The
> Wait Type should display as PAGELATCH IO if I recall correctly.
> Took me by surprise too but it isn't an actual blocked process.
> As far as performance goes, I haven't seen any performance hits on
> databases up to 400 GB in size.
> Dave Wall wrote:
>
> --
> Kyle Quinby
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message1756427.html
>
Saturday, February 25, 2012
process could not connect to Distributor
Sql Server SP4 on the publisher/distributer.
MSDE SP4 on the subscriber
Merge Replication
Anonymous Pull Subscriptions
TCP/IP only - removed Named Pipes
Windows Authent only - removed SQL Server
Setup an alias on the subscriber to the publisher.
Running on same network but different workgroups. Can not use Windows
Authentication as moving to Internet model.
Followed
http://support.microsoft.com/default...&Product=sql2k
So I setup the publisher to use an SA user and gave that SA user ownership
and admin rights to the publisher database.
I keep getting this error from the ActiveX component in VB.NET on the
subscriber: The process could not connect to Distributor 'W2KSERVER'.
SQL Server does not exist or access denied.
I had these guys working when it was SP3a, still had named pipes, and using
Windows Authentication passthrough.
Thanks,
Buzz
configure distributornetwork for tcpip, use the fqdn for the
distributoraddress (ie sqlserver.mydomainname.com).
Hilary Cotter
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
"Buzz" <buzz@.online.nospam> wrote in message
news:EC950BD0-5245-47EB-8320-06D6633633BA@.microsoft.com...
> Sql Server SP4 on the publisher/distributer.
> MSDE SP4 on the subscriber
> Merge Replication
> Anonymous Pull Subscriptions
> TCP/IP only - removed Named Pipes
> Windows Authent only - removed SQL Server
> Setup an alias on the subscriber to the publisher.
> Running on same network but different workgroups. Can not use Windows
> Authentication as moving to Internet model.
> Followed
>
http://support.microsoft.com/default...&Product=sql2k
> So I setup the publisher to use an SA user and gave that SA user ownership
> and admin rights to the publisher database.
> I keep getting this error from the ActiveX component in VB.NET on the
> subscriber: The process could not connect to Distributor 'W2KSERVER'.
> SQL Server does not exist or access denied.
> I had these guys working when it was SP3a, still had named pipes, and
using
> Windows Authentication passthrough.
> Thanks,
> Buzz
>
>
|||Hello,
Name resolution must be working between all machines involved in
replication. Otherwise, you may receive the error message.
I suggest that you perform the following steps to narrow down the issue:
* Drop the subcription and then drop the publication.
* Setup name resolution both ways between the machines. There are several
options for achieving name resolution. You can use CNU aliases
(cliconfg.exe), hosts files, WINS, and/or DNS.
* On the publisher reregister in publisher and subscriber in Enterprise
Manager by netbios name instead of by IP address.
* On the remote server, register the publisher and the subscriber in
Enterprise Manager by netbios name (@.@.servername).
* Recreate the publication and then recreate the subscription.
* Run the Merge agent. Check the issue.
The following information is for your reference:
Potential causes of the "SQL Server does not exist or access denied" error
message
http://support.microsoft.com/?id=328306
324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
2000)
http://support.microsoft.com/?id=324992
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||All that and it turns out it was a software firewall issue with XP on the
subscriber laptop.
However, now I am stuck with the next issue. Part of replicating over
untrusted domains or the internet means I need to use FTP. On the subscribers
I use the ActiveX merge module.
I specify the FTP address:
_merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
If Me.txtFtpAddress.Text.StartsWith("ftp://") = False Then
Me.txtFtpAddress.Text = "ftp://" & Me.txtFtpAddress.Text
End If
Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
_merge.FTPAddress = Me.txtFtpAddress.Text
But it keeps erroring out saying it cannot find the FTP location specified
at the value I have for _merge.Publisher?
The value for the Ftp is ftp://192.168.1.2/repldata.
The value for the Publisher is server909.
I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
But I'm not going to be doing LMHOSTS management on 500+ production laptops
and we plan on using different FTP servers that are different than the SQL
Server.
"Sophie Guo [MSFT]" wrote:
> Hello,
> Name resolution must be working between all machines involved in
> replication. Otherwise, you may receive the error message.
> I suggest that you perform the following steps to narrow down the issue:
> * Drop the subcription and then drop the publication.
> * Setup name resolution both ways between the machines. There are several
> options for achieving name resolution. You can use CNU aliases
> (cliconfg.exe), hosts files, WINS, and/or DNS.
> * On the publisher reregister in publisher and subscriber in Enterprise
> Manager by netbios name instead of by IP address.
> * On the remote server, register the publisher and the subscriber in
> Enterprise Manager by netbios name (@.@.servername).
> * Recreate the publication and then recreate the subscription.
> * Run the Merge agent. Check the issue.
> The following information is for your reference:
> Potential causes of the "SQL Server does not exist or access denied" error
> message
> http://support.microsoft.com/?id=328306
> 324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
> 2000)
> http://support.microsoft.com/?id=324992
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Not sure if the following will help, but let me try to clarify a few things:
1) Ftp support in SQL replication applies only to transfer of snapshot
files, movement of SQL changes would require a regular connection to SQL
server (Publisher and Distributor).
2) The Ftp* properties on the Merge\Distribution ActiveX control have
actually been deprecated in SQL2000, configuration of FTP snapshot support is
done at the publication level (right-click publication for properties). Once
that is confiigured, you will need to regenerate a new snapshot for the
settings to take effect. And when you start the merge control, all you need
to do is to specify a FileTransferType of FTP. In hind-sight, it was probably
a mistake not to take out the FTP* properties completely.
3) There is still the all important task of getting the merge activeX
control to establish a regular connection to SQL Server from an untrusted
domain in the first place. This typically means that either 1) to expose
whatever port that the distributor and publisher are listening on (default
SQL Server port is 1433) to the outside world (or accessible from the
laptops) and then use the Distributor|PublisherNetwork|Address properties to
point to the exposed IP address\port configuration, or 2) (recommended) to
configure VPN between the laptops and the Publisher\Distributor machines so
regular SQL Server connections can be established. If you decide to use the
VPN approach, there really is no need to configure FTP for the snapshot files
as regular UNC shares should be accessible by the laptops.
HTH
-Raymond
"Buzz" wrote:
[vbcol=seagreen]
> All that and it turns out it was a software firewall issue with XP on the
> subscriber laptop.
> However, now I am stuck with the next issue. Part of replicating over
> untrusted domains or the internet means I need to use FTP. On the subscribers
> I use the ActiveX merge module.
> I specify the FTP address:
> _merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
> If Me.txtFtpAddress.Text.StartsWith("ftp://") = False Then
> Me.txtFtpAddress.Text = "ftp://" & Me.txtFtpAddress.Text
> End If
> Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
> _merge.FTPAddress = Me.txtFtpAddress.Text
> But it keeps erroring out saying it cannot find the FTP location specified
> at the value I have for _merge.Publisher?
> The value for the Ftp is ftp://192.168.1.2/repldata.
> The value for the Publisher is server909.
> I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
> But I'm not going to be doing LMHOSTS management on 500+ production laptops
> and we plan on using different FTP servers that are different than the SQL
> Server.
> "Sophie Guo [MSFT]" wrote:
MSDE SP4 on the subscriber
Merge Replication
Anonymous Pull Subscriptions
TCP/IP only - removed Named Pipes
Windows Authent only - removed SQL Server
Setup an alias on the subscriber to the publisher.
Running on same network but different workgroups. Can not use Windows
Authentication as moving to Internet model.
Followed
http://support.microsoft.com/default...&Product=sql2k
So I setup the publisher to use an SA user and gave that SA user ownership
and admin rights to the publisher database.
I keep getting this error from the ActiveX component in VB.NET on the
subscriber: The process could not connect to Distributor 'W2KSERVER'.
SQL Server does not exist or access denied.
I had these guys working when it was SP3a, still had named pipes, and using
Windows Authentication passthrough.
Thanks,
Buzz
configure distributornetwork for tcpip, use the fqdn for the
distributoraddress (ie sqlserver.mydomainname.com).
Hilary Cotter
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
"Buzz" <buzz@.online.nospam> wrote in message
news:EC950BD0-5245-47EB-8320-06D6633633BA@.microsoft.com...
> Sql Server SP4 on the publisher/distributer.
> MSDE SP4 on the subscriber
> Merge Replication
> Anonymous Pull Subscriptions
> TCP/IP only - removed Named Pipes
> Windows Authent only - removed SQL Server
> Setup an alias on the subscriber to the publisher.
> Running on same network but different workgroups. Can not use Windows
> Authentication as moving to Internet model.
> Followed
>
http://support.microsoft.com/default...&Product=sql2k
> So I setup the publisher to use an SA user and gave that SA user ownership
> and admin rights to the publisher database.
> I keep getting this error from the ActiveX component in VB.NET on the
> subscriber: The process could not connect to Distributor 'W2KSERVER'.
> SQL Server does not exist or access denied.
> I had these guys working when it was SP3a, still had named pipes, and
using
> Windows Authentication passthrough.
> Thanks,
> Buzz
>
>
|||Hello,
Name resolution must be working between all machines involved in
replication. Otherwise, you may receive the error message.
I suggest that you perform the following steps to narrow down the issue:
* Drop the subcription and then drop the publication.
* Setup name resolution both ways between the machines. There are several
options for achieving name resolution. You can use CNU aliases
(cliconfg.exe), hosts files, WINS, and/or DNS.
* On the publisher reregister in publisher and subscriber in Enterprise
Manager by netbios name instead of by IP address.
* On the remote server, register the publisher and the subscriber in
Enterprise Manager by netbios name (@.@.servername).
* Recreate the publication and then recreate the subscription.
* Run the Merge agent. Check the issue.
The following information is for your reference:
Potential causes of the "SQL Server does not exist or access denied" error
message
http://support.microsoft.com/?id=328306
324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
2000)
http://support.microsoft.com/?id=324992
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||All that and it turns out it was a software firewall issue with XP on the
subscriber laptop.
However, now I am stuck with the next issue. Part of replicating over
untrusted domains or the internet means I need to use FTP. On the subscribers
I use the ActiveX merge module.
I specify the FTP address:
_merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
If Me.txtFtpAddress.Text.StartsWith("ftp://") = False Then
Me.txtFtpAddress.Text = "ftp://" & Me.txtFtpAddress.Text
End If
Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
_merge.FTPAddress = Me.txtFtpAddress.Text
But it keeps erroring out saying it cannot find the FTP location specified
at the value I have for _merge.Publisher?
The value for the Ftp is ftp://192.168.1.2/repldata.
The value for the Publisher is server909.
I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
But I'm not going to be doing LMHOSTS management on 500+ production laptops
and we plan on using different FTP servers that are different than the SQL
Server.
"Sophie Guo [MSFT]" wrote:
> Hello,
> Name resolution must be working between all machines involved in
> replication. Otherwise, you may receive the error message.
> I suggest that you perform the following steps to narrow down the issue:
> * Drop the subcription and then drop the publication.
> * Setup name resolution both ways between the machines. There are several
> options for achieving name resolution. You can use CNU aliases
> (cliconfg.exe), hosts files, WINS, and/or DNS.
> * On the publisher reregister in publisher and subscriber in Enterprise
> Manager by netbios name instead of by IP address.
> * On the remote server, register the publisher and the subscriber in
> Enterprise Manager by netbios name (@.@.servername).
> * Recreate the publication and then recreate the subscription.
> * Run the Merge agent. Check the issue.
> The following information is for your reference:
> Potential causes of the "SQL Server does not exist or access denied" error
> message
> http://support.microsoft.com/?id=328306
> 324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
> 2000)
> http://support.microsoft.com/?id=324992
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Not sure if the following will help, but let me try to clarify a few things:
1) Ftp support in SQL replication applies only to transfer of snapshot
files, movement of SQL changes would require a regular connection to SQL
server (Publisher and Distributor).
2) The Ftp* properties on the Merge\Distribution ActiveX control have
actually been deprecated in SQL2000, configuration of FTP snapshot support is
done at the publication level (right-click publication for properties). Once
that is confiigured, you will need to regenerate a new snapshot for the
settings to take effect. And when you start the merge control, all you need
to do is to specify a FileTransferType of FTP. In hind-sight, it was probably
a mistake not to take out the FTP* properties completely.
3) There is still the all important task of getting the merge activeX
control to establish a regular connection to SQL Server from an untrusted
domain in the first place. This typically means that either 1) to expose
whatever port that the distributor and publisher are listening on (default
SQL Server port is 1433) to the outside world (or accessible from the
laptops) and then use the Distributor|PublisherNetwork|Address properties to
point to the exposed IP address\port configuration, or 2) (recommended) to
configure VPN between the laptops and the Publisher\Distributor machines so
regular SQL Server connections can be established. If you decide to use the
VPN approach, there really is no need to configure FTP for the snapshot files
as regular UNC shares should be accessible by the laptops.
HTH
-Raymond
"Buzz" wrote:
[vbcol=seagreen]
> All that and it turns out it was a software firewall issue with XP on the
> subscriber laptop.
> However, now I am stuck with the next issue. Part of replicating over
> untrusted domains or the internet means I need to use FTP. On the subscribers
> I use the ActiveX merge module.
> I specify the FTP address:
> _merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
> If Me.txtFtpAddress.Text.StartsWith("ftp://") = False Then
> Me.txtFtpAddress.Text = "ftp://" & Me.txtFtpAddress.Text
> End If
> Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
> _merge.FTPAddress = Me.txtFtpAddress.Text
> But it keeps erroring out saying it cannot find the FTP location specified
> at the value I have for _merge.Publisher?
> The value for the Ftp is ftp://192.168.1.2/repldata.
> The value for the Publisher is server909.
> I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
> But I'm not going to be doing LMHOSTS management on 500+ production laptops
> and we plan on using different FTP servers that are different than the SQL
> Server.
> "Sophie Guo [MSFT]" wrote:
Process blocking itself since SP4
Hi,
Since installing SP4 we seem to encounter issues where a process seems to block itself. Has anyone seen this issue. Is this a feature?
Thanks,
Dave
Please refer to the following for more details. This may be the reason
The original posting can be found in many places, for example: http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server/23496/SP4-reports-queries-blocking-on-themselves
There is also a KB article on this: http://support.microsoft.com/default.aspx?scid=KB;EN-US;906344
Thanks
Subscribe to:
Posts (Atom)