Monday, March 19, 2012
[SQL Server 2000] How to programmatically read Merge Agent properties
I would like to read from SQL Server information that is presented in
Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
Agents (particularly the columns "Subscription" and "Action Time").
Which tables should I read? I checked the tables in msdb and master database
but couldn't find anything suitable. BOL and Google were of no help either.
Thank you in advance for your help.
Best regards,
AndrewTry a profiler trace and examine the source of the executed procs.
Hope this helps.
Dan Guzman
SQL Server MVP
"Andrew Drake" <andrewdrake@.hotmail.com> wrote in message
news:uBPvoxZAHHA.4024@.TK2MSFTNGP04.phx.gbl...
> Dear all,
> I would like to read from SQL Server information that is presented in
> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
> Agents (particularly the columns "Subscription" and "Action Time").
> Which tables should I read? I checked the tables in msdb and master
> database
> but couldn't find anything suitable. BOL and Google were of no help
> either.
> Thank you in advance for your help.
> Best regards,
> Andrew
>
>|||"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:12D028F8-1237-454D-8387-4A30B283851F@.microsoft.com...[vbcol=seagreen]
> Try a profiler trace and examine the source of the executed procs.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>
Ok, I've checked, but unfortunately that is an undocumented procedure:
sp_MSenum_replication_agents @.type = 4
(type = 4 stands for merge replication agent)
Thank you for your help.
Best regards,
Andrew|||I took cursory look at the text of that proc and the called proc and it
looks to me like the source of the data is the MSmerge_history table. It's
documented in the Books Online.
Hope this helps.
Dan Guzman
SQL Server MVP
"Andrew Drake" <andrewdrake@.hotmail.com> wrote in message
news:uizTrebAHHA.4328@.TK2MSFTNGP03.phx.gbl...
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:12D028F8-1237-454D-8387-4A30B283851F@.microsoft.com...
> Ok, I've checked, but unfortunately that is an undocumented procedure:
> sp_MSenum_replication_agents @.type = 4
> (type = 4 stands for merge replication agent)
> Thank you for your help.
> Best regards,
> Andrew
>|||"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:CF65CD9F-E7BA-4FAB-AC81-326BD56C2FB7@.microsoft.com...
>I took cursory look at the text of that proc and the called proc and it
>looks to me like the source of the data is the MSmerge_history table. It's
>documented in the Books Online.
[...][vbcol=seagreen]
> Dan Guzman
> SQL Server MVP
>
Dan,
Thank you for your help!
Best regards,
Andrew
[SQL Server 2000] How to programmatically read Merge Agent properties
I would like to read from SQL Server information that is presented in
Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
Agents (particularly the columns "Subscription" and "Action Time").
Which tables should I read? I checked the tables in msdb and master database
but couldn't find anything suitable. BOL and Google were of no help either.
Thank you in advance for your help.
Best regards,
AndrewTry a profiler trace and examine the source of the executed procs.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Andrew Drake" <andrewdrake@.hotmail.com> wrote in message
news:uBPvoxZAHHA.4024@.TK2MSFTNGP04.phx.gbl...
> Dear all,
> I would like to read from SQL Server information that is presented in
> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
> Agents (particularly the columns "Subscription" and "Action Time").
> Which tables should I read? I checked the tables in msdb and master
> database
> but couldn't find anything suitable. BOL and Google were of no help
> either.
> Thank you in advance for your help.
> Best regards,
> Andrew
>
>|||"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:12D028F8-1237-454D-8387-4A30B283851F@.microsoft.com...
> Try a profiler trace and examine the source of the executed procs.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>> Dear all,
>> I would like to read from SQL Server information that is presented in
>> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
>> Agents (particularly the columns "Subscription" and "Action Time").
>> Which tables should I read? I checked the tables in msdb and master
>> database
>> but couldn't find anything suitable. BOL and Google were of no help
>> either.
>> Thank you in advance for your help.
>> Best regards,
>> Andrew
Ok, I've checked, but unfortunately that is an undocumented procedure:
sp_MSenum_replication_agents @.type = 4
(type = 4 stands for merge replication agent)
Thank you for your help.
Best regards,
Andrew|||I took cursory look at the text of that proc and the called proc and it
looks to me like the source of the data is the MSmerge_history table. It's
documented in the Books Online.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Andrew Drake" <andrewdrake@.hotmail.com> wrote in message
news:uizTrebAHHA.4328@.TK2MSFTNGP03.phx.gbl...
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:12D028F8-1237-454D-8387-4A30B283851F@.microsoft.com...
>> Try a profiler trace and examine the source of the executed procs.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> Dear all,
>> I would like to read from SQL Server information that is presented in
>> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \
>> Merge
>> Agents (particularly the columns "Subscription" and "Action Time").
>> Which tables should I read? I checked the tables in msdb and master
>> database
>> but couldn't find anything suitable. BOL and Google were of no help
>> either.
>> Thank you in advance for your help.
>> Best regards,
>> Andrew
> Ok, I've checked, but unfortunately that is an undocumented procedure:
> sp_MSenum_replication_agents @.type = 4
> (type = 4 stands for merge replication agent)
> Thank you for your help.
> Best regards,
> Andrew
>|||"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:CF65CD9F-E7BA-4FAB-AC81-326BD56C2FB7@.microsoft.com...
>I took cursory look at the text of that proc and the called proc and it
>looks to me like the source of the data is the MSmerge_history table. It's
>documented in the Books Online.
[...]
> Dan Guzman
> SQL Server MVP
>> Dear all,
>> I would like to read from SQL Server information that is presented in
>> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \
>> Merge
>> Agents (particularly the columns "Subscription" and "Action Time").
>> Which tables should I read? I checked the tables in msdb and master
>> database
>> but couldn't find anything suitable. BOL and Google were of no help
>> either.
>> Ok, I've checked, but unfortunately that is an undocumented procedure:
>> sp_MSenum_replication_agents @.type = 4
>> (type = 4 stands for merge replication agent)
Dan,
Thank you for your help!
Best regards,
Andrew
Sunday, February 19, 2012
[F4] properties dialog does not follow convention of defaultvalue <> bold, changedvalue=bo
I'd post it on Connect but then I'd wait 2 months to get "won't fix - this does not 'fit' with the current Katmai schedule" i.e. if I'm lucky (based on the new improved 3yr delivery of sql) it might get delivered in 2011. Wow.
Imagine if Xbox or PS3 designers told their customers, "sorry we know that up/down/left/right are in fact right/left/down/up, as you may expect on a game controller, but if you wait 3 years we might fix it"
I'm tired of your attitude regarding Connect. That is the means we have in place right now. Submit the Connect bug and move on. At least then it is flagged.|||
Adolf,
I would suggest to open a a report in connect and to place the link in this thread; that way others can add their vote if they want. I agree on something, requests at connect sometimes do not get the attention we would want, but you always have the opportunity of replying back.|||
Rafael Salas wrote:
Adolf,I would suggest to open a a report in connect and to place the link in this thread; that way others can add their vote if they want. I agree on something, requests at connect sometimes do not get the attention we would want, but you always have the opportunity of replying back.
And at least there is an official record of the bug. That is the most important part.