Hello,
I am dealing with a quite big application written in ASP communicating
directly with the database. The problem is that there is performance
problems with the DB and after investigating things a bit more I have
found that the number of User Connection are over 32000 according to
the Performance Monitor.
Yes, it would be better too have a 3-tier architecture but I am stuck
with what I have and have to do the best of the situation. I have gone
through every page to make sure that the ADO connection is closed and
that the connection object is set to nothing. I have also tried to
change the MAX Pool Size from everything from 50 upp to 500 and
Connection Lifetime I have set to 10. My conclusion is that I am
dealing with a leak somewhere (but I can not find it). My question is,
is there a way in SQL Server to clean up un-used user connection - let
them time out by them self.
Any suggestions? Anybody encountered anything similar? All ideas and
comments are welcomed.You could create a job that took the data from sp_who2 and compared the time
now to the LastBatch column. If they exceed your threshold disconnect them
with the KILL command.
Ensure your application can handle this and exit gracefully.
HTH. Ryan
<mathias_pettersson@.hotmail.com> wrote in message
news:1137510134.733734.249390@.g49g2000cwa.googlegroups.com...
> Hello,
> I am dealing with a quite big application written in ASP communicating
> directly with the database. The problem is that there is performance
> problems with the DB and after investigating things a bit more I have
> found that the number of User Connection are over 32000 according to
> the Performance Monitor.
> Yes, it would be better too have a 3-tier architecture but I am stuck
> with what I have and have to do the best of the situation. I have gone
> through every page to make sure that the ADO connection is closed and
> that the connection object is set to nothing. I have also tried to
> change the MAX Pool Size from everything from 50 upp to 500 and
> Connection Lifetime I have set to 10. My conclusion is that I am
> dealing with a leak somewhere (but I can not find it). My question is,
> is there a way in SQL Server to clean up un-used user connection - let
> them time out by them self.
> Any suggestions? Anybody encountered anything similar? All ideas and
> comments are welcomed.
>|||Just out of interest how much memory does your server have..?
Each connection takes around 24KB, you've got 24Kb * 320000 which is about
750Mb gone from SQL Server.
HTH. Ryan
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uoYfth3GGHA.1032@.TK2MSFTNGP11.phx.gbl...
> You could create a job that took the data from sp_who2 and compared the
> time
> now to the LastBatch column. If they exceed your threshold disconnect them
> with the KILL command.
> Ensure your application can handle this and exit gracefully.
> --
> HTH. Ryan
> <mathias_pettersson@.hotmail.com> wrote in message
> news:1137510134.733734.249390@.g49g2000cwa.googlegroups.com...
>|||The server has 1GB of RAM and dual 2.4Ghz processors
Showing posts with label monitor. Show all posts
Showing posts with label monitor. Show all posts
Sunday, March 25, 2012
32000 User Connections (According to Performance Monitor)
Hello,
I am dealing with a quite big application written in ASP communicating
directly with the database. The problem is that there is performance
problems with the DB and after investigating things a bit more I have
found that the number of User Connection are over 32000 according to
the Performance Monitor.
Yes, it would be better too have a 3-tier architecture but I am stuck
with what I have and have to do the best of the situation. I have gone
through every page to make sure that the ADO connection is closed and
that the connection object is set to nothing. I have also tried to
change the MAX Pool Size from everything from 50 upp to 500 and
Connection Lifetime I have set to 10. My conclusion is that I am
dealing with a leak somewhere (but I can not find it). My question is,
is there a way in SQL Server to clean up un-used user connection - let
them time out by them self.
Any suggestions? Anybody encountered anything similar? All ideas and
comments are welcomed.
You could create a job that took the data from sp_who2 and compared the time
now to the LastBatch column. If they exceed your threshold disconnect them
with the KILL command.
Ensure your application can handle this and exit gracefully.
HTH. Ryan
<mathias_pettersson@.hotmail.com> wrote in message
news:1137510134.733734.249390@.g49g2000cwa.googlegr oups.com...
> Hello,
> I am dealing with a quite big application written in ASP communicating
> directly with the database. The problem is that there is performance
> problems with the DB and after investigating things a bit more I have
> found that the number of User Connection are over 32000 according to
> the Performance Monitor.
> Yes, it would be better too have a 3-tier architecture but I am stuck
> with what I have and have to do the best of the situation. I have gone
> through every page to make sure that the ADO connection is closed and
> that the connection object is set to nothing. I have also tried to
> change the MAX Pool Size from everything from 50 upp to 500 and
> Connection Lifetime I have set to 10. My conclusion is that I am
> dealing with a leak somewhere (but I can not find it). My question is,
> is there a way in SQL Server to clean up un-used user connection - let
> them time out by them self.
> Any suggestions? Anybody encountered anything similar? All ideas and
> comments are welcomed.
>
|||Just out of interest how much memory does your server have..?
Each connection takes around 24KB, you've got 24Kb * 320000 which is about
750Mb gone from SQL Server.
HTH. Ryan
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uoYfth3GGHA.1032@.TK2MSFTNGP11.phx.gbl...
> You could create a job that took the data from sp_who2 and compared the
> time
> now to the LastBatch column. If they exceed your threshold disconnect them
> with the KILL command.
> Ensure your application can handle this and exit gracefully.
> --
> HTH. Ryan
> <mathias_pettersson@.hotmail.com> wrote in message
> news:1137510134.733734.249390@.g49g2000cwa.googlegr oups.com...
>
|||The server has 1GB of RAM and dual 2.4Ghz processors
I am dealing with a quite big application written in ASP communicating
directly with the database. The problem is that there is performance
problems with the DB and after investigating things a bit more I have
found that the number of User Connection are over 32000 according to
the Performance Monitor.
Yes, it would be better too have a 3-tier architecture but I am stuck
with what I have and have to do the best of the situation. I have gone
through every page to make sure that the ADO connection is closed and
that the connection object is set to nothing. I have also tried to
change the MAX Pool Size from everything from 50 upp to 500 and
Connection Lifetime I have set to 10. My conclusion is that I am
dealing with a leak somewhere (but I can not find it). My question is,
is there a way in SQL Server to clean up un-used user connection - let
them time out by them self.
Any suggestions? Anybody encountered anything similar? All ideas and
comments are welcomed.
You could create a job that took the data from sp_who2 and compared the time
now to the LastBatch column. If they exceed your threshold disconnect them
with the KILL command.
Ensure your application can handle this and exit gracefully.
HTH. Ryan
<mathias_pettersson@.hotmail.com> wrote in message
news:1137510134.733734.249390@.g49g2000cwa.googlegr oups.com...
> Hello,
> I am dealing with a quite big application written in ASP communicating
> directly with the database. The problem is that there is performance
> problems with the DB and after investigating things a bit more I have
> found that the number of User Connection are over 32000 according to
> the Performance Monitor.
> Yes, it would be better too have a 3-tier architecture but I am stuck
> with what I have and have to do the best of the situation. I have gone
> through every page to make sure that the ADO connection is closed and
> that the connection object is set to nothing. I have also tried to
> change the MAX Pool Size from everything from 50 upp to 500 and
> Connection Lifetime I have set to 10. My conclusion is that I am
> dealing with a leak somewhere (but I can not find it). My question is,
> is there a way in SQL Server to clean up un-used user connection - let
> them time out by them self.
> Any suggestions? Anybody encountered anything similar? All ideas and
> comments are welcomed.
>
|||Just out of interest how much memory does your server have..?
Each connection takes around 24KB, you've got 24Kb * 320000 which is about
750Mb gone from SQL Server.
HTH. Ryan
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uoYfth3GGHA.1032@.TK2MSFTNGP11.phx.gbl...
> You could create a job that took the data from sp_who2 and compared the
> time
> now to the LastBatch column. If they exceed your threshold disconnect them
> with the KILL command.
> Ensure your application can handle this and exit gracefully.
> --
> HTH. Ryan
> <mathias_pettersson@.hotmail.com> wrote in message
> news:1137510134.733734.249390@.g49g2000cwa.googlegr oups.com...
>
|||The server has 1GB of RAM and dual 2.4Ghz processors
32000 User Connections (According to Performance Monitor)
Hello,
I am dealing with a quite big application written in ASP communicating
directly with the database. The problem is that there is performance
problems with the DB and after investigating things a bit more I have
found that the number of User Connection are over 32000 according to
the Performance Monitor.
Yes, it would be better too have a 3-tier architecture but I am stuck
with what I have and have to do the best of the situation. I have gone
through every page to make sure that the ADO connection is closed and
that the connection object is set to nothing. I have also tried to
change the MAX Pool Size from everything from 50 upp to 500 and
Connection Lifetime I have set to 10. My conclusion is that I am
dealing with a leak somewhere (but I can not find it). My question is,
is there a way in SQL Server to clean up un-used user connection - let
them time out by them self.
Any suggestions? Anybody encountered anything similar? All ideas and
comments are welcomed.You could create a job that took the data from sp_who2 and compared the time
now to the LastBatch column. If they exceed your threshold disconnect them
with the KILL command.
Ensure your application can handle this and exit gracefully.
--
HTH. Ryan
<mathias_pettersson@.hotmail.com> wrote in message
news:1137510134.733734.249390@.g49g2000cwa.googlegroups.com...
> Hello,
> I am dealing with a quite big application written in ASP communicating
> directly with the database. The problem is that there is performance
> problems with the DB and after investigating things a bit more I have
> found that the number of User Connection are over 32000 according to
> the Performance Monitor.
> Yes, it would be better too have a 3-tier architecture but I am stuck
> with what I have and have to do the best of the situation. I have gone
> through every page to make sure that the ADO connection is closed and
> that the connection object is set to nothing. I have also tried to
> change the MAX Pool Size from everything from 50 upp to 500 and
> Connection Lifetime I have set to 10. My conclusion is that I am
> dealing with a leak somewhere (but I can not find it). My question is,
> is there a way in SQL Server to clean up un-used user connection - let
> them time out by them self.
> Any suggestions? Anybody encountered anything similar? All ideas and
> comments are welcomed.
>|||Just out of interest how much memory does your server have..?
Each connection takes around 24KB, you've got 24Kb * 320000 which is about
750Mb gone from SQL Server.
--
HTH. Ryan
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uoYfth3GGHA.1032@.TK2MSFTNGP11.phx.gbl...
> You could create a job that took the data from sp_who2 and compared the
> time
> now to the LastBatch column. If they exceed your threshold disconnect them
> with the KILL command.
> Ensure your application can handle this and exit gracefully.
> --
> HTH. Ryan
> <mathias_pettersson@.hotmail.com> wrote in message
> news:1137510134.733734.249390@.g49g2000cwa.googlegroups.com...
>> Hello,
>> I am dealing with a quite big application written in ASP communicating
>> directly with the database. The problem is that there is performance
>> problems with the DB and after investigating things a bit more I have
>> found that the number of User Connection are over 32000 according to
>> the Performance Monitor.
>> Yes, it would be better too have a 3-tier architecture but I am stuck
>> with what I have and have to do the best of the situation. I have gone
>> through every page to make sure that the ADO connection is closed and
>> that the connection object is set to nothing. I have also tried to
>> change the MAX Pool Size from everything from 50 upp to 500 and
>> Connection Lifetime I have set to 10. My conclusion is that I am
>> dealing with a leak somewhere (but I can not find it). My question is,
>> is there a way in SQL Server to clean up un-used user connection - let
>> them time out by them self.
>> Any suggestions? Anybody encountered anything similar? All ideas and
>> comments are welcomed.
>|||The server has 1GB of RAM and dual 2.4Ghz processorssql
I am dealing with a quite big application written in ASP communicating
directly with the database. The problem is that there is performance
problems with the DB and after investigating things a bit more I have
found that the number of User Connection are over 32000 according to
the Performance Monitor.
Yes, it would be better too have a 3-tier architecture but I am stuck
with what I have and have to do the best of the situation. I have gone
through every page to make sure that the ADO connection is closed and
that the connection object is set to nothing. I have also tried to
change the MAX Pool Size from everything from 50 upp to 500 and
Connection Lifetime I have set to 10. My conclusion is that I am
dealing with a leak somewhere (but I can not find it). My question is,
is there a way in SQL Server to clean up un-used user connection - let
them time out by them self.
Any suggestions? Anybody encountered anything similar? All ideas and
comments are welcomed.You could create a job that took the data from sp_who2 and compared the time
now to the LastBatch column. If they exceed your threshold disconnect them
with the KILL command.
Ensure your application can handle this and exit gracefully.
--
HTH. Ryan
<mathias_pettersson@.hotmail.com> wrote in message
news:1137510134.733734.249390@.g49g2000cwa.googlegroups.com...
> Hello,
> I am dealing with a quite big application written in ASP communicating
> directly with the database. The problem is that there is performance
> problems with the DB and after investigating things a bit more I have
> found that the number of User Connection are over 32000 according to
> the Performance Monitor.
> Yes, it would be better too have a 3-tier architecture but I am stuck
> with what I have and have to do the best of the situation. I have gone
> through every page to make sure that the ADO connection is closed and
> that the connection object is set to nothing. I have also tried to
> change the MAX Pool Size from everything from 50 upp to 500 and
> Connection Lifetime I have set to 10. My conclusion is that I am
> dealing with a leak somewhere (but I can not find it). My question is,
> is there a way in SQL Server to clean up un-used user connection - let
> them time out by them self.
> Any suggestions? Anybody encountered anything similar? All ideas and
> comments are welcomed.
>|||Just out of interest how much memory does your server have..?
Each connection takes around 24KB, you've got 24Kb * 320000 which is about
750Mb gone from SQL Server.
--
HTH. Ryan
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uoYfth3GGHA.1032@.TK2MSFTNGP11.phx.gbl...
> You could create a job that took the data from sp_who2 and compared the
> time
> now to the LastBatch column. If they exceed your threshold disconnect them
> with the KILL command.
> Ensure your application can handle this and exit gracefully.
> --
> HTH. Ryan
> <mathias_pettersson@.hotmail.com> wrote in message
> news:1137510134.733734.249390@.g49g2000cwa.googlegroups.com...
>> Hello,
>> I am dealing with a quite big application written in ASP communicating
>> directly with the database. The problem is that there is performance
>> problems with the DB and after investigating things a bit more I have
>> found that the number of User Connection are over 32000 according to
>> the Performance Monitor.
>> Yes, it would be better too have a 3-tier architecture but I am stuck
>> with what I have and have to do the best of the situation. I have gone
>> through every page to make sure that the ADO connection is closed and
>> that the connection object is set to nothing. I have also tried to
>> change the MAX Pool Size from everything from 50 upp to 500 and
>> Connection Lifetime I have set to 10. My conclusion is that I am
>> dealing with a leak somewhere (but I can not find it). My question is,
>> is there a way in SQL Server to clean up un-used user connection - let
>> them time out by them self.
>> Any suggestions? Anybody encountered anything similar? All ideas and
>> comments are welcomed.
>|||The server has 1GB of RAM and dual 2.4Ghz processorssql
Friday, February 24, 2012
2005 selected databas monitoring - how?
I have three databases with same user login. How can I monitor activity only
for one database (logins, transactions) in SQL 2005 server?
I can't change the user for this database.
Hi
You can filter the database by db_id within sql server profiler
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>I have three databases with same user login. How can I monitor activity
>only for one database (logins, transactions) in SQL 2005 server?
> I can't change the user for this database.
>
|||Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that it
was in 2000 profiler, but it's like here is some changes in 2005.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Hi
> You can filter the database by db_id within sql server profiler
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>
|||No, just check all events and all columns and you will see
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
> it was in 2000 profiler, but it's like here is some changes in 2005.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>
|||Thank You. I found it.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urV6K7WZHHA.4396@.TK2MSFTNGP06.phx.gbl...
> No, just check all events and all columns and you will see
>
>
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>
for one database (logins, transactions) in SQL 2005 server?
I can't change the user for this database.
Hi
You can filter the database by db_id within sql server profiler
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>I have three databases with same user login. How can I monitor activity
>only for one database (logins, transactions) in SQL 2005 server?
> I can't change the user for this database.
>
|||Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that it
was in 2000 profiler, but it's like here is some changes in 2005.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Hi
> You can filter the database by db_id within sql server profiler
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>
|||No, just check all events and all columns and you will see
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
> it was in 2000 profiler, but it's like here is some changes in 2005.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>
|||Thank You. I found it.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urV6K7WZHHA.4396@.TK2MSFTNGP06.phx.gbl...
> No, just check all events and all columns and you will see
>
>
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>
2005 selected databas monitoring - how?
I have three databases with same user login. How can I monitor activity only
for one database (logins, transactions) in SQL 2005 server?
I can't change the user for this database.Hi
You can filter the database by db_id within sql server profiler
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>I have three databases with same user login. How can I monitor activity
>only for one database (logins, transactions) in SQL 2005 server?
> I can't change the user for this database.
>|||Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that it
was in 2000 profiler, but it's like here is some changes in 2005.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Hi
> You can filter the database by db_id within sql server profiler
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>>I have three databases with same user login. How can I monitor activity
>>only for one database (logins, transactions) in SQL 2005 server?
>> I can't change the user for this database.
>|||No, just check all events and all columns and you will see
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
> it was in 2000 profiler, but it's like here is some changes in 2005.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>> Hi
>> You can filter the database by db_id within sql server profiler
>>
>> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
>> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>>I have three databases with same user login. How can I monitor activity
>>only for one database (logins, transactions) in SQL 2005 server?
>> I can't change the user for this database.
>>
>|||Thank You. I found it.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urV6K7WZHHA.4396@.TK2MSFTNGP06.phx.gbl...
> No, just check all events and all columns and you will see
>
>
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
>> it was in 2000 profiler, but it's like here is some changes in 2005.
>>
>> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>> Hi
>> You can filter the database by db_id within sql server profiler
>>
>> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
>> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>>I have three databases with same user login. How can I monitor activity
>>only for one database (logins, transactions) in SQL 2005 server?
>> I can't change the user for this database.
>>
>>
>
for one database (logins, transactions) in SQL 2005 server?
I can't change the user for this database.Hi
You can filter the database by db_id within sql server profiler
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>I have three databases with same user login. How can I monitor activity
>only for one database (logins, transactions) in SQL 2005 server?
> I can't change the user for this database.
>|||Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that it
was in 2000 profiler, but it's like here is some changes in 2005.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Hi
> You can filter the database by db_id within sql server profiler
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>>I have three databases with same user login. How can I monitor activity
>>only for one database (logins, transactions) in SQL 2005 server?
>> I can't change the user for this database.
>|||No, just check all events and all columns and you will see
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
> it was in 2000 profiler, but it's like here is some changes in 2005.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>> Hi
>> You can filter the database by db_id within sql server profiler
>>
>> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
>> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>>I have three databases with same user login. How can I monitor activity
>>only for one database (logins, transactions) in SQL 2005 server?
>> I can't change the user for this database.
>>
>|||Thank You. I found it.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urV6K7WZHHA.4396@.TK2MSFTNGP06.phx.gbl...
> No, just check all events and all columns and you will see
>
>
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
>> it was in 2000 profiler, but it's like here is some changes in 2005.
>>
>> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>> Hi
>> You can filter the database by db_id within sql server profiler
>>
>> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
>> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>>I have three databases with same user login. How can I monitor activity
>>only for one database (logins, transactions) in SQL 2005 server?
>> I can't change the user for this database.
>>
>>
>
2005 selected databas monitoring - how?
I have three databases with same user login. How can I monitor activity only
for one database (logins, transactions) in SQL 2005 server?
I can't change the user for this database.
Hi
You can filter the database by db_id within sql server profiler
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>I have three databases with same user login. How can I monitor activity
>only for one database (logins, transactions) in SQL 2005 server?
> I can't change the user for this database.
>
|||Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that it
was in 2000 profiler, but it's like here is some changes in 2005.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Hi
> You can filter the database by db_id within sql server profiler
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>
|||No, just check all events and all columns and you will see
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
> it was in 2000 profiler, but it's like here is some changes in 2005.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>
|||Thank You. I found it.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urV6K7WZHHA.4396@.TK2MSFTNGP06.phx.gbl...
> No, just check all events and all columns and you will see
>
>
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>
for one database (logins, transactions) in SQL 2005 server?
I can't change the user for this database.
Hi
You can filter the database by db_id within sql server profiler
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>I have three databases with same user login. How can I monitor activity
>only for one database (logins, transactions) in SQL 2005 server?
> I can't change the user for this database.
>
|||Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that it
was in 2000 profiler, but it's like here is some changes in 2005.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Hi
> You can filter the database by db_id within sql server profiler
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>
|||No, just check all events and all columns and you will see
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
> it was in 2000 profiler, but it's like here is some changes in 2005.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>
|||Thank You. I found it.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urV6K7WZHHA.4396@.TK2MSFTNGP06.phx.gbl...
> No, just check all events and all columns and you will see
>
>
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>
2005 selected databas monitoring - how?
I have three databases with same user login. How can I monitor activity only
for one database (logins, transactions) in SQL 2005 server?
I can't change the user for this database.Hi
You can filter the database by db_id within sql server profiler
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>I have three databases with same user login. How can I monitor activity
>only for one database (logins, transactions) in SQL 2005 server?
> I can't change the user for this database.
>|||Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that it
was in 2000 profiler, but it's like here is some changes in 2005.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Hi
> You can filter the database by db_id within sql server profiler
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>|||No, just check all events and all columns and you will see
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
> it was in 2000 profiler, but it's like here is some changes in 2005.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>|||Thank You. I found it.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urV6K7WZHHA.4396@.TK2MSFTNGP06.phx.gbl...
> No, just check all events and all columns and you will see
>
>
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>
for one database (logins, transactions) in SQL 2005 server?
I can't change the user for this database.Hi
You can filter the database by db_id within sql server profiler
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>I have three databases with same user login. How can I monitor activity
>only for one database (logins, transactions) in SQL 2005 server?
> I can't change the user for this database.
>|||Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that it
was in 2000 profiler, but it's like here is some changes in 2005.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Hi
> You can filter the database by db_id within sql server profiler
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:OFp1vMWZHHA.1220@.TK2MSFTNGP03.phx.gbl...
>|||No, just check all events and all columns and you will see
"Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Unfortunately I can't find DB_ID field in 2005 SQL Profiler. I know that
> it was in 2000 profiler, but it's like here is some changes in 2005.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ePqsQWWZHHA.2552@.TK2MSFTNGP06.phx.gbl...
>|||Thank You. I found it.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urV6K7WZHHA.4396@.TK2MSFTNGP06.phx.gbl...
> No, just check all events and all columns and you will see
>
>
>
> "Sergejs Degtjars" <sergeydeg@.inbox.lv> wrote in message
> news:uwTjr1WZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>
Sunday, February 19, 2012
2005 Replication Monitor != MSdistribution_status.undelivCmdsInDis
22 of my 36 distribution agents currently show a total of 400,000+
undistributed commands in MSdistribution_status, but if I look a the agents
individually in SQL Server 2005 Replication Monitor they all show 0
undistributed commands. And if I use sp_browsereplcmds to get a specific
insert in question I find that it has, indeed, been applied to both
subscribers.
How can I get MSdistribution_status cleaned-up?
Can you run the distribution clean up job? This should take care of it.
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
"ravenbrk" <ravenbrk@.discussions.microsoft.com> wrote in message
news:43090C21-D19D-4C3D-B8A0-283F7CD0BACD@.microsoft.com...
> 22 of my 36 distribution agents currently show a total of 400,000+
> undistributed commands in MSdistribution_status, but if I look a the
> agents
> individually in SQL Server 2005 Replication Monitor they all show 0
> undistributed commands. And if I use sp_browsereplcmds to get a specific
> insert in question I find that it has, indeed, been applied to both
> subscribers.
> How can I get MSdistribution_status cleaned-up?
>
|||Yes, the distribution cleanup job runs successfully every 10 minutes and has
no effect.
"Hilary Cotter" wrote:
> Can you run the distribution clean up job? This should take care of it.
> --
> 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
>
> "ravenbrk" <ravenbrk@.discussions.microsoft.com> wrote in message
> news:43090C21-D19D-4C3D-B8A0-283F7CD0BACD@.microsoft.com...
>
>
|||You can safely delete the contents of msrepl_transactions and
msrepl_commands which are beyond the retention period manually.
It seems like you have an ophaned subscription or inconsistent metadata.
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
"ravenbrk" <ravenbrk@.discussions.microsoft.com> wrote in message
news:D7E9736D-F3A6-429B-9CDC-E9495782041D@.microsoft.com...[vbcol=seagreen]
> Yes, the distribution cleanup job runs successfully every 10 minutes and
> has
> no effect.
>
> "Hilary Cotter" wrote:
|||Before I went to anything drastic like manually deleting the commands, I dug
a little deeper and found that each of my publications has four agents
showing in msdistribution_agents. They have subscriber_id values of -1, -2,
2, and 3.
Subscribers 2 & 3 show a status of 2 in mssubscriptions, a runstatus of
either 3 or 4 in MSdistribution_history, and are the same subscribers that
show up in Replication Monitor and just like in Replication Monitor they show
zero undistributed transactions in the tables that lie under
MSdistribution_status.
The subscriber_id -1 and -2 agents show a status of 1, a runstatus of 0, a
subscriber_db of "virtual", and a xact_seqno of 0x0 (in
MSdistribution_history) which is causing all transactions to show in
MSdistribution_status as undelivered. These "virtual" agents were created at
the same time and day as the "real" agents.
What are "virtual" subscribers, how were they created, why are they hanging
onto all my transactions but not distributing them anywhere, and how can I
get rid of them?
"Hilary Cotter" wrote:
> You can safely delete the contents of msrepl_transactions and
> msrepl_commands which are beyond the retention period manually.
> It seems like you have an ophaned subscription or inconsistent metadata.
> --
> 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
>
> "ravenbrk" <ravenbrk@.discussions.microsoft.com> wrote in message
> news:D7E9736D-F3A6-429B-9CDC-E9495782041D@.microsoft.com...
>
>
|||There are two major findings related to the issue of unwanted retention of
delivered transactions in the distribution database that were not apparently
removed with the sp_MSdistribution_cleanup procedure.
A) Virtual subscribers (-1, -2) are created (or not created) -- see
distribution..MSsubscriptions table -- with the sp_addarticle procedure call,
depending upon the following property settings as specified in the
sp_addpublication procedure call.
1) virtual subscribers created
@.allow_pull='true'
@.allow_anonymous='false'
@.immediate_sync='true'
2) virtual subscribers NOT created
@.allow_pull='true'
@.allow_anonymous='false'
@.immediate_sync='false'
3) virtual subscribers NOT created
@.allow_pull='false'
@.allow_anonymous='false'
@.immediate_sync='false'
4) virtual subscribers created
@.allow_pull='false'
@.allow_anonymous='false'
@.immediate_sync='true'
5) no, not a valid combination of property settings for sp_addpublication
@.allow_pull='false'
@.allow_anonymous='true'
@.immediate_sync='false'
6) virtual subscribers created
@.allow_pull='true'
@.allow_anonymous='true'
@.immediate_sync='true'
The desired combination for our configuration is 3). In order to remove the
virtual subscriptions, the named subscriptions then publications have to be
removed. Our replication configuration will have to be recreated ensuring
the modification of the sp_addpublication commands is as stated in 3).
B) When using the wizard there is a check box on the Snapshot Agent dialog
that states 'Create a snapshot immediately and keep the snapshot available to
initialize subscriptions'. If it is checked then publication property
combination 6) is used. If the box is NOT checked, then publication property
combination 2) is used. If we use the wizard, we should NOT check this box,
then later, modify the publication manually to NOT allow_pull subscriptions.
C) After A) was determined, it was noticed that the
sp_MSdistribution_cleanup procedure always seemed to fail to delete the most
recent set of delivered transactions. Troubleshooting revealed a bug -- I
hope this is not a feature -- in the last statement of the procedure
sp_MSmaximum_cleanup_seqno.
The SP1 version of the procedure's last statement is:
select top 1 @.max_cleanup_xact_seqno = xact_seqno
from MSrepl_transactions with (nolock)
where
publisher_database_id = @.publisher_database_id and
(xact_seqno < @.min_xact_seqno
or @.min_xact_seqno IS NULL) and
entry_time <= @.min_cutoff_time
order by xact_seqno desc
By changing 'xact_seqno < @.min_xact_seqno' to 'xact_seqno <=
@.min_xact_seqno' the sp_MSdistribution_cleanup procedure will now delete all
delivered transactions. Also found in the procedure was logic to ignore
cleanup of commands in which the publication has the property
@.immediate_sync=1 (true), which further solidifies the conclusion found in A)
to set the @.immediate_sync property to (false).
James Brake
"ravenbrk" wrote:
> 22 of my 36 distribution agents currently show a total of 400,000+
> undistributed commands in MSdistribution_status, but if I look a the agents
> individually in SQL Server 2005 Replication Monitor they all show 0
> undistributed commands. And if I use sp_browsereplcmds to get a specific
> insert in question I find that it has, indeed, been applied to both
> subscribers.
> How can I get MSdistribution_status cleaned-up?
>
undistributed commands in MSdistribution_status, but if I look a the agents
individually in SQL Server 2005 Replication Monitor they all show 0
undistributed commands. And if I use sp_browsereplcmds to get a specific
insert in question I find that it has, indeed, been applied to both
subscribers.
How can I get MSdistribution_status cleaned-up?
Can you run the distribution clean up job? This should take care of it.
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
"ravenbrk" <ravenbrk@.discussions.microsoft.com> wrote in message
news:43090C21-D19D-4C3D-B8A0-283F7CD0BACD@.microsoft.com...
> 22 of my 36 distribution agents currently show a total of 400,000+
> undistributed commands in MSdistribution_status, but if I look a the
> agents
> individually in SQL Server 2005 Replication Monitor they all show 0
> undistributed commands. And if I use sp_browsereplcmds to get a specific
> insert in question I find that it has, indeed, been applied to both
> subscribers.
> How can I get MSdistribution_status cleaned-up?
>
|||Yes, the distribution cleanup job runs successfully every 10 minutes and has
no effect.
"Hilary Cotter" wrote:
> Can you run the distribution clean up job? This should take care of it.
> --
> 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
>
> "ravenbrk" <ravenbrk@.discussions.microsoft.com> wrote in message
> news:43090C21-D19D-4C3D-B8A0-283F7CD0BACD@.microsoft.com...
>
>
|||You can safely delete the contents of msrepl_transactions and
msrepl_commands which are beyond the retention period manually.
It seems like you have an ophaned subscription or inconsistent metadata.
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
"ravenbrk" <ravenbrk@.discussions.microsoft.com> wrote in message
news:D7E9736D-F3A6-429B-9CDC-E9495782041D@.microsoft.com...[vbcol=seagreen]
> Yes, the distribution cleanup job runs successfully every 10 minutes and
> has
> no effect.
>
> "Hilary Cotter" wrote:
|||Before I went to anything drastic like manually deleting the commands, I dug
a little deeper and found that each of my publications has four agents
showing in msdistribution_agents. They have subscriber_id values of -1, -2,
2, and 3.
Subscribers 2 & 3 show a status of 2 in mssubscriptions, a runstatus of
either 3 or 4 in MSdistribution_history, and are the same subscribers that
show up in Replication Monitor and just like in Replication Monitor they show
zero undistributed transactions in the tables that lie under
MSdistribution_status.
The subscriber_id -1 and -2 agents show a status of 1, a runstatus of 0, a
subscriber_db of "virtual", and a xact_seqno of 0x0 (in
MSdistribution_history) which is causing all transactions to show in
MSdistribution_status as undelivered. These "virtual" agents were created at
the same time and day as the "real" agents.
What are "virtual" subscribers, how were they created, why are they hanging
onto all my transactions but not distributing them anywhere, and how can I
get rid of them?
"Hilary Cotter" wrote:
> You can safely delete the contents of msrepl_transactions and
> msrepl_commands which are beyond the retention period manually.
> It seems like you have an ophaned subscription or inconsistent metadata.
> --
> 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
>
> "ravenbrk" <ravenbrk@.discussions.microsoft.com> wrote in message
> news:D7E9736D-F3A6-429B-9CDC-E9495782041D@.microsoft.com...
>
>
|||There are two major findings related to the issue of unwanted retention of
delivered transactions in the distribution database that were not apparently
removed with the sp_MSdistribution_cleanup procedure.
A) Virtual subscribers (-1, -2) are created (or not created) -- see
distribution..MSsubscriptions table -- with the sp_addarticle procedure call,
depending upon the following property settings as specified in the
sp_addpublication procedure call.
1) virtual subscribers created
@.allow_pull='true'
@.allow_anonymous='false'
@.immediate_sync='true'
2) virtual subscribers NOT created
@.allow_pull='true'
@.allow_anonymous='false'
@.immediate_sync='false'
3) virtual subscribers NOT created
@.allow_pull='false'
@.allow_anonymous='false'
@.immediate_sync='false'
4) virtual subscribers created
@.allow_pull='false'
@.allow_anonymous='false'
@.immediate_sync='true'
5) no, not a valid combination of property settings for sp_addpublication
@.allow_pull='false'
@.allow_anonymous='true'
@.immediate_sync='false'
6) virtual subscribers created
@.allow_pull='true'
@.allow_anonymous='true'
@.immediate_sync='true'
The desired combination for our configuration is 3). In order to remove the
virtual subscriptions, the named subscriptions then publications have to be
removed. Our replication configuration will have to be recreated ensuring
the modification of the sp_addpublication commands is as stated in 3).
B) When using the wizard there is a check box on the Snapshot Agent dialog
that states 'Create a snapshot immediately and keep the snapshot available to
initialize subscriptions'. If it is checked then publication property
combination 6) is used. If the box is NOT checked, then publication property
combination 2) is used. If we use the wizard, we should NOT check this box,
then later, modify the publication manually to NOT allow_pull subscriptions.
C) After A) was determined, it was noticed that the
sp_MSdistribution_cleanup procedure always seemed to fail to delete the most
recent set of delivered transactions. Troubleshooting revealed a bug -- I
hope this is not a feature -- in the last statement of the procedure
sp_MSmaximum_cleanup_seqno.
The SP1 version of the procedure's last statement is:
select top 1 @.max_cleanup_xact_seqno = xact_seqno
from MSrepl_transactions with (nolock)
where
publisher_database_id = @.publisher_database_id and
(xact_seqno < @.min_xact_seqno
or @.min_xact_seqno IS NULL) and
entry_time <= @.min_cutoff_time
order by xact_seqno desc
By changing 'xact_seqno < @.min_xact_seqno' to 'xact_seqno <=
@.min_xact_seqno' the sp_MSdistribution_cleanup procedure will now delete all
delivered transactions. Also found in the procedure was logic to ignore
cleanup of commands in which the publication has the property
@.immediate_sync=1 (true), which further solidifies the conclusion found in A)
to set the @.immediate_sync property to (false).
James Brake
"ravenbrk" wrote:
> 22 of my 36 distribution agents currently show a total of 400,000+
> undistributed commands in MSdistribution_status, but if I look a the agents
> individually in SQL Server 2005 Replication Monitor they all show 0
> undistributed commands. And if I use sp_browsereplcmds to get a specific
> insert in question I find that it has, indeed, been applied to both
> subscribers.
> How can I get MSdistribution_status cleaned-up?
>
2005 Replication Mon Interface
I am playing around with the new Replication Monitor in 2005. In the old
Replication Monitor (SQL Sever2k), you could right click on a subscription
and Start or Stop Synchronizing. So far I have not been able to find this
feature in the new Replication Monitor and I've had to SQL Server Management
Studio to be able to control the subscription. Our subscriptions frequently
go off-line (off-site) and sometimes require a manual start when they
return, so access to this feature for all subscriptions in one place is
handy.
Thanks for any help.
Ted.
The button you are looking for is called "Start Synchronizing" with the
corrollary of "Stop Synchronizing". I can't remember exactly where it is,
but it is located somewhere around the actual subscription.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"TCorp" <tcorpus@.hotmail.com> wrote in message
news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>I am playing around with the new Replication Monitor in 2005. In the old
>Replication Monitor (SQL Sever2k), you could right click on a subscription
>and Start or Stop Synchronizing. So far I have not been able to find this
>feature in the new Replication Monitor and I've had to SQL Server
>Management Studio to be able to control the subscription. Our
>subscriptions frequently go off-line (off-site) and sometimes require a
>manual start when they return, so access to this feature for all
>subscriptions in one place is handy.
> Thanks for any help.
> Ted.
>
|||Connect to your Publisher in WorkBench, expand the Replication node, expand
Local Publications, right click on your publication and select Launch
Replication Monitor (I think you are already here). Expand the Replication
Monitor Node, My Publishers node, and your Publisher node, and locate your
publication. Click on it and then in the Right Hand pane, select Warnings
and Agents tab. In the lower portion of the pane locate your snapshot agent
and right click on it to start it or stop it.
You can also access it through the SQL Server Agent node in SQL WorkBench
for your SQL Server, and expand the Jobs folder. Right click on your Agent
(if you can locate it by its name) and select Start Job or Stop Job.
I think at this point it is important to point out that the Replication
Wizards and interfaces were completely redesigned to make them more
intuitive and less confusing.
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
"TCorp" <tcorpus@.hotmail.com> wrote in message
news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>I am playing around with the new Replication Monitor in 2005. In the old
>Replication Monitor (SQL Sever2k), you could right click on a subscription
>and Start or Stop Synchronizing. So far I have not been able to find this
>feature in the new Replication Monitor and I've had to SQL Server
>Management Studio to be able to control the subscription. Our
>subscriptions frequently go off-line (off-site) and sometimes require a
>manual start when they return, so access to this feature for all
>subscriptions in one place is handy.
> Thanks for any help.
> Ted.
>
|||Translated, it will take you a while to figure out where they put
everything.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OwvBUtMEGHA.344@.TK2MSFTNGP11.phx.gbl...
> Connect to your Publisher in WorkBench, expand the Replication node,
> expand Local Publications, right click on your publication and select
> Launch Replication Monitor (I think you are already here). Expand the
> Replication Monitor Node, My Publishers node, and your Publisher node, and
> locate your publication. Click on it and then in the Right Hand pane,
> select Warnings and Agents tab. In the lower portion of the pane locate
> your snapshot agent and right click on it to start it or stop it.
> You can also access it through the SQL Server Agent node in SQL WorkBench
> for your SQL Server, and expand the Jobs folder. Right click on your Agent
> (if you can locate it by its name) and select Start Job or Stop Job.
> I think at this point it is important to point out that the Replication
> Wizards and interfaces were completely redesigned to make them more
> intuitive and less confusing.
> --
> 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
> "TCorp" <tcorpus@.hotmail.com> wrote in message
> news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>
|||This article should help clarify things a bit:
http://www.replicationanswers.com/GUIArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks everyone for your help and prompt replies.
But what I am looking for is to stop and start my (pull) Merge Agents.
Looking at Paul Ibison's helpful article, I realize that the option to Start
and Stop the merge agents is not there (in the All Subscriptions Tab of my
publication). The only options when I right-click the subscription are:
- View Details
- Reinitialize Subscription
- Validate Subscription
- Agent Profile
- Properties
- Refresh
Currently, the only way I can Start/Stop the merge agents is to connect to
the [subscription] server in Management Studio, open the
"Replication-->Local Subscriptions" folder, right-click the subscription and
select "View Synchronization Status". That dialog box give me buttons to
Start and Stop the agent.
Strangely, I thought I created a publication last week (in my testing) that
had that option there, and that's part of the reason I am so confused right
now, as it seems to have disappeared.
My publisher/distributor is SQL Server 2005 and my pull merge subscriptions
are running on MSDE.
Thanks again.
------
"TCorp" <tcorpus@.hotmail.com> wrote in message
news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>I am playing around with the new Replication Monitor in 2005. In the old
>Replication Monitor (SQL Sever2k), you could right click on a subscription
>and Start or Stop Synchronizing. So far I have not been able to find this
>feature in the new Replication Monitor and I've had to SQL Server
>Management Studio to be able to control the subscription. Our
>subscriptions frequently go off-line (off-site) and sometimes require a
>manual start when they return, so access to this feature for all
>subscriptions in one place is handy.
> Thanks for any help.
> Ted.
>
|||Now that I know where the option to synchronize really was (Thanks Paul) and
that it was missing, I was able to look further into it.
It seems that it is a difference between push and pull merge agents. The
option to Start/Stop synchronizing the Merge agents seems to only be
available for PUSH subscriptions in the Replication monitor. These articles
implicate such:
http://msdn2.microsoft.com/en-us/library/ms152749.aspx
http://msdn2.microsoft.com/en-us/library/ms151261.aspx
We've historically used Pull subscriptions because our MSDE subscribers were
often off-line and we were experiencing a lot of error messages in the
replication monitor. But now I must reconsider using push again.
My only recourse now to to ask if anyone knows why the 2005 Replication
Monitor does not allow us to Start/Stop pull subscriptions.
Thanks, Ted.
"TCorp" <tcorpus@.hotmail.com> wrote in message
news:OxOc%23ZVEGHA.1120@.TK2MSFTNGP11.phx.gbl...
> Thanks everyone for your help and prompt replies.
> But what I am looking for is to stop and start my (pull) Merge Agents.
> Looking at Paul Ibison's helpful article, I realize that the option to
> Start and Stop the merge agents is not there (in the All Subscriptions Tab
> of my publication). The only options when I right-click the subscription
> are:
> - View Details
> - Reinitialize Subscription
> - Validate Subscription
> - Agent Profile
> - Properties
> - Refresh
> Currently, the only way I can Start/Stop the merge agents is to connect to
> the [subscription] server in Management Studio, open the
> "Replication-->Local Subscriptions" folder, right-click the subscription
> and select "View Synchronization Status". That dialog box give me buttons
> to Start and Stop the agent.
> Strangely, I thought I created a publication last week (in my testing)
> that had that option there, and that's part of the reason I am so confused
> right now, as it seems to have disappeared.
> My publisher/distributor is SQL Server 2005 and my pull merge
> subscriptions are running on MSDE.
> Thanks again.
> ------
> "TCorp" <tcorpus@.hotmail.com> wrote in message
> news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>
Replication Monitor (SQL Sever2k), you could right click on a subscription
and Start or Stop Synchronizing. So far I have not been able to find this
feature in the new Replication Monitor and I've had to SQL Server Management
Studio to be able to control the subscription. Our subscriptions frequently
go off-line (off-site) and sometimes require a manual start when they
return, so access to this feature for all subscriptions in one place is
handy.
Thanks for any help.
Ted.
The button you are looking for is called "Start Synchronizing" with the
corrollary of "Stop Synchronizing". I can't remember exactly where it is,
but it is located somewhere around the actual subscription.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"TCorp" <tcorpus@.hotmail.com> wrote in message
news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>I am playing around with the new Replication Monitor in 2005. In the old
>Replication Monitor (SQL Sever2k), you could right click on a subscription
>and Start or Stop Synchronizing. So far I have not been able to find this
>feature in the new Replication Monitor and I've had to SQL Server
>Management Studio to be able to control the subscription. Our
>subscriptions frequently go off-line (off-site) and sometimes require a
>manual start when they return, so access to this feature for all
>subscriptions in one place is handy.
> Thanks for any help.
> Ted.
>
|||Connect to your Publisher in WorkBench, expand the Replication node, expand
Local Publications, right click on your publication and select Launch
Replication Monitor (I think you are already here). Expand the Replication
Monitor Node, My Publishers node, and your Publisher node, and locate your
publication. Click on it and then in the Right Hand pane, select Warnings
and Agents tab. In the lower portion of the pane locate your snapshot agent
and right click on it to start it or stop it.
You can also access it through the SQL Server Agent node in SQL WorkBench
for your SQL Server, and expand the Jobs folder. Right click on your Agent
(if you can locate it by its name) and select Start Job or Stop Job.
I think at this point it is important to point out that the Replication
Wizards and interfaces were completely redesigned to make them more
intuitive and less confusing.
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
"TCorp" <tcorpus@.hotmail.com> wrote in message
news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>I am playing around with the new Replication Monitor in 2005. In the old
>Replication Monitor (SQL Sever2k), you could right click on a subscription
>and Start or Stop Synchronizing. So far I have not been able to find this
>feature in the new Replication Monitor and I've had to SQL Server
>Management Studio to be able to control the subscription. Our
>subscriptions frequently go off-line (off-site) and sometimes require a
>manual start when they return, so access to this feature for all
>subscriptions in one place is handy.
> Thanks for any help.
> Ted.
>
|||Translated, it will take you a while to figure out where they put
everything.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OwvBUtMEGHA.344@.TK2MSFTNGP11.phx.gbl...
> Connect to your Publisher in WorkBench, expand the Replication node,
> expand Local Publications, right click on your publication and select
> Launch Replication Monitor (I think you are already here). Expand the
> Replication Monitor Node, My Publishers node, and your Publisher node, and
> locate your publication. Click on it and then in the Right Hand pane,
> select Warnings and Agents tab. In the lower portion of the pane locate
> your snapshot agent and right click on it to start it or stop it.
> You can also access it through the SQL Server Agent node in SQL WorkBench
> for your SQL Server, and expand the Jobs folder. Right click on your Agent
> (if you can locate it by its name) and select Start Job or Stop Job.
> I think at this point it is important to point out that the Replication
> Wizards and interfaces were completely redesigned to make them more
> intuitive and less confusing.
> --
> 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
> "TCorp" <tcorpus@.hotmail.com> wrote in message
> news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>
|||This article should help clarify things a bit:
http://www.replicationanswers.com/GUIArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks everyone for your help and prompt replies.
But what I am looking for is to stop and start my (pull) Merge Agents.
Looking at Paul Ibison's helpful article, I realize that the option to Start
and Stop the merge agents is not there (in the All Subscriptions Tab of my
publication). The only options when I right-click the subscription are:
- View Details
- Reinitialize Subscription
- Validate Subscription
- Agent Profile
- Properties
- Refresh
Currently, the only way I can Start/Stop the merge agents is to connect to
the [subscription] server in Management Studio, open the
"Replication-->Local Subscriptions" folder, right-click the subscription and
select "View Synchronization Status". That dialog box give me buttons to
Start and Stop the agent.
Strangely, I thought I created a publication last week (in my testing) that
had that option there, and that's part of the reason I am so confused right
now, as it seems to have disappeared.
My publisher/distributor is SQL Server 2005 and my pull merge subscriptions
are running on MSDE.
Thanks again.
------
"TCorp" <tcorpus@.hotmail.com> wrote in message
news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>I am playing around with the new Replication Monitor in 2005. In the old
>Replication Monitor (SQL Sever2k), you could right click on a subscription
>and Start or Stop Synchronizing. So far I have not been able to find this
>feature in the new Replication Monitor and I've had to SQL Server
>Management Studio to be able to control the subscription. Our
>subscriptions frequently go off-line (off-site) and sometimes require a
>manual start when they return, so access to this feature for all
>subscriptions in one place is handy.
> Thanks for any help.
> Ted.
>
|||Now that I know where the option to synchronize really was (Thanks Paul) and
that it was missing, I was able to look further into it.
It seems that it is a difference between push and pull merge agents. The
option to Start/Stop synchronizing the Merge agents seems to only be
available for PUSH subscriptions in the Replication monitor. These articles
implicate such:
http://msdn2.microsoft.com/en-us/library/ms152749.aspx
http://msdn2.microsoft.com/en-us/library/ms151261.aspx
We've historically used Pull subscriptions because our MSDE subscribers were
often off-line and we were experiencing a lot of error messages in the
replication monitor. But now I must reconsider using push again.
My only recourse now to to ask if anyone knows why the 2005 Replication
Monitor does not allow us to Start/Stop pull subscriptions.
Thanks, Ted.
"TCorp" <tcorpus@.hotmail.com> wrote in message
news:OxOc%23ZVEGHA.1120@.TK2MSFTNGP11.phx.gbl...
> Thanks everyone for your help and prompt replies.
> But what I am looking for is to stop and start my (pull) Merge Agents.
> Looking at Paul Ibison's helpful article, I realize that the option to
> Start and Stop the merge agents is not there (in the All Subscriptions Tab
> of my publication). The only options when I right-click the subscription
> are:
> - View Details
> - Reinitialize Subscription
> - Validate Subscription
> - Agent Profile
> - Properties
> - Refresh
> Currently, the only way I can Start/Stop the merge agents is to connect to
> the [subscription] server in Management Studio, open the
> "Replication-->Local Subscriptions" folder, right-click the subscription
> and select "View Synchronization Status". That dialog box give me buttons
> to Start and Stop the agent.
> Strangely, I thought I created a publication last week (in my testing)
> that had that option there, and that's part of the reason I am so confused
> right now, as it seems to have disappeared.
> My publisher/distributor is SQL Server 2005 and my pull merge
> subscriptions are running on MSDE.
> Thanks again.
> ------
> "TCorp" <tcorpus@.hotmail.com> wrote in message
> news:OtxxSZMEGHA.2300@.TK2MSFTNGP15.phx.gbl...
>
Saturday, February 11, 2012
2005 Developer - Perf Monitor Counter Check Failed message
Trying to install 2005 Dev edition in xp pro, sp2.
I was able to complete the installation and thought all was well.
I was wrong.
Performance Monitor Counter Check Failed Error.
Had to stop the install twice at the point it verified what components were to be included as
the docs were not going to be installed. Resolved the issue.
Now it won't pass the system config test because the registry is not the way it wants it.
I look up the messages and the only solution is to hack the registry and risk my system.
This is nuts.
Isn't there some way to restart cleanly without hacking registry keys ?
Help.
I know it isn't a nice solution, but this thread sums up the registry changes to fix this problem. Sorry for the hassle. The thread discusses the released article to solve this, as well as some gotchas that aren't covered in the doc.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=356308&SiteID=1
Thanks,
Sam Lester (MSFT)
I was able to complete the installation and thought all was well.
I was wrong.
No data base tools or docs were installed, so I ran the install again
and it says they are already there.. They are not.
I installed 2005 dev on my laptop with no issues and the installed dirs and products are
not the same.
I tried to uninstall 2005 on the problem desktop but it errors out during uninstall and no
I am trapped in do mans land.
Why can't the install program function correctly?
How can I start from scratch without rebuilding my machine?
Subscribe to:
Posts (Atom)