does RS have the mode "push" & "pull" ?

Hi, everyone,

When i use the crystal report, there have a option "push" & "pull" .

Does report in the SQL Server reporting Services have the same option ?
Thank you!With Reporting Services, you can subscribe to reports and also generate on-demand and data-driven reports. Is this the push and pull functionality you are looking for?|||

Not. In crystal report , use push mode need get the data by user not by the crystal report, the fill the data into the report. So this mode can improve the performance.

If there is large data in the database , use pull mode wil very slowly.

Thank you for your reply.

|||

Hi, does anyone knows how to this? I also need to push the data to the report because I have this scenario, I have to display a report on the changed data of the user (not yet being saved in the database). How could this be done in the reporting services?

Thanks a lot in advance and more power.

does RS have the mode "push" & "pull" ?

Hi, everyone,

When i use the crystal report, there have a option "push" & "pull" .

Does report in the SQL Server reporting Services have the same option ?
Thank you!
With Reporting Services, you can subscribe to reports and also generate on-demand and data-driven reports. Is this the push and pull functionality you are looking for?|||

Not. In crystal report , use push mode need get the data by user not by the crystal report, the fill the data into the report. So this mode can improve the performance.

If there is large data in the database , use pull mode wil very slowly.

Thank you for your reply.

|||

Hi, does anyone knows how to this? I also need to push the data to the report because I have this scenario, I have to display a report on the changed data of the user (not yet being saved in the database). How could this be done in the reporting services?

Thanks a lot in advance and more power.

Does replication setup make some entry in the Remote servers setti

If I create a transactional replication - Push method in SQL 2K standard with
sp4, will replication create entries in the Remote Servers setting in EM?
Currently I found three entries in the Remote Servers listing, server name
for the publishing server name, server name for the subscriber server, and
repl_distrbutor.
If the replication does make these entries, I have no problem with the
repl_distributor being there. But I have problem with the subscriber server
name being there because I want to create a Linked Server with that same name
but I can't since the name is already in use by the remote servers.
Please let me know which one or all of the above names are legit if indeed
repliation put them in there to begin with.
Say if the above entries need to be there, how I should move them to the
Linked Servers setting because the remote servers feature is for backward
compatible reason and linked servers is more dynamic and is the one to
replace it.
Thanks in advance.
Wingman
Remote Servers and Linked Servers are all stored in the sysservers table in
the master database. Different flag values determine what an entry actually
represents. There is even a special entry for the local server name. If
you want or need to use a replication participating server as a linked
server, there is a special work-around to enable that functionality.
PRB: Adding a Linked Server Causes Error 15028
http://support.microsoft.com/kb/274098/en-us
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:DC17EBF5-D4FF-49C6-83A7-7E3E4F8D0FE0@.microsoft.com...
> If I create a transactional replication - Push method in SQL 2K standard
> with
> sp4, will replication create entries in the Remote Servers setting in EM?
> Currently I found three entries in the Remote Servers listing, server name
> for the publishing server name, server name for the subscriber server, and
> repl_distrbutor.
> If the replication does make these entries, I have no problem with the
> repl_distributor being there. But I have problem with the subscriber
> server
> name being there because I want to create a Linked Server with that same
> name
> but I can't since the name is already in use by the remote servers.
> Please let me know which one or all of the above names are legit if indeed
> repliation put them in there to begin with.
> Say if the above entries need to be there, how I should move them to the
> Linked Servers setting because the remote servers feature is for backward
> compatible reason and linked servers is more dynamic and is the one to
> replace it.
> Thanks in advance.
> Wingman
|||Ok, I tried that stored procedure and the server name now shows up in both
linked server and remote servers. And I still can't execute the remote
stored procedure. Here is my observation after reading the link. It said
the status for a remote server of a subscriber supposedly a 69. In order for
it to become a linked server of a subscriber it needs to be 229. Before I
executed the stored procedure, the server name that I want to change its
status is 1093 not 69. After the execution, it added 160 to it to become
1253. Is the 1253 status correct? The initial status number 1093 is not 69,
is it because there are other settings added values to it?
Here are my questions:
1) is it correct that the server name will show up both in the linked
servers and remote servers in EM?
2) Is the 1253 new status correct?
3) the link didn't say I need to do a service restart, what do you think? I
am getting this error when I execute a remote stored procedure:
"Could not execute procedure on remote server 'server1' because SQL Server
is not configured for remote access. Ask your system administrator to
reconfigure SQL Server to allow remote access."
Also, when I try to double click on the 'table' of the linked server, it
said the server doesn't exist or access denied. The SQL login name I
entered in the Linked server properties has the sys admin right and this
account exists in both servers.
Wingman
"Wingman" wrote:

> If I create a transactional replication - Push method in SQL 2K standard with
> sp4, will replication create entries in the Remote Servers setting in EM?
> Currently I found three entries in the Remote Servers listing, server name
> for the publishing server name, server name for the subscriber server, and
> repl_distrbutor.
> If the replication does make these entries, I have no problem with the
> repl_distributor being there. But I have problem with the subscriber server
> name being there because I want to create a Linked Server with that same name
> but I can't since the name is already in use by the remote servers.
> Please let me know which one or all of the above names are legit if indeed
> repliation put them in there to begin with.
> Say if the above entries need to be there, how I should move them to the
> Linked Servers setting because the remote servers feature is for backward
> compatible reason and linked servers is more dynamic and is the one to
> replace it.
> Thanks in advance.
> Wingman
|||Yes, it is correct to see the servers listed in more than one place. The
values you refer to are bit flags held in an integer field. Addition is not
the correct operation, logical OR is the correct operation.
You need to enable each server for remote access, just like it says. Login
to each remote SQL server and execute the following:
exec sp_configure 'remote access', 1
go
reconfigure with override
go
This tells the remote server to accept remote queries.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:59C3CADD-1BCB-45CD-9DB0-2EEEFCADCA6B@.microsoft.com...[vbcol=seagreen]
> Ok, I tried that stored procedure and the server name now shows up in both
> linked server and remote servers. And I still can't execute the remote
> stored procedure. Here is my observation after reading the link. It said
> the status for a remote server of a subscriber supposedly a 69. In order
> for
> it to become a linked server of a subscriber it needs to be 229. Before
> I
> executed the stored procedure, the server name that I want to change its
> status is 1093 not 69. After the execution, it added 160 to it to become
> 1253. Is the 1253 status correct? The initial status number 1093 is not
> 69,
> is it because there are other settings added values to it?
> Here are my questions:
> 1) is it correct that the server name will show up both in the linked
> servers and remote servers in EM?
> 2) Is the 1253 new status correct?
> 3) the link didn't say I need to do a service restart, what do you think?
> I
> am getting this error when I execute a remote stored procedure:
> "Could not execute procedure on remote server 'server1' because SQL Server
> is not configured for remote access. Ask your system administrator to
> reconfigure SQL Server to allow remote access."
> Also, when I try to double click on the 'table' of the linked server, it
> said the server doesn't exist or access denied. The SQL login name I
> entered in the Linked server properties has the sys admin right and this
> account exists in both servers.
>
> Wingman
>
> "Wingman" wrote:

Documentation of RMO and Merge Replication

Hi there,

In a lot of the Replication documentation it only refers to the merge agent operating in the context of a push or a pull configuration. i.e. if it is push then the merge agent is at the distributor but if it is a pull then the merge agent functions at the subscriber.

I recently joined a project which is configured as a push but it uses RMO for synchronisation. This RMO application is installed on a compeletely separate server. Initially I thought the RMO was just passing requests through to the publisher/distributor/subscriber but the distributor didn't seem to be doing any of the work. It therefore seems that the merging/synchronisation is being performed on this RMO application server and not the distributor or subscriber.

I therefore think it would be good (assuming I am correct of course) that the documentation reflects this caveat

As a general observation Replication programming seems to be quite detached from the rest of the replication documentation. Is this a deliberate decision?

It isn't normally, but I'll ping the writer in charge of this and ask.

Buck Woody

|||

To answer your last question first. Yes, it was a product-wide design decision to put all of the programming API documentation for SQL Server together in a separate node. I agree with you that it isn't ideal. In the next release of SQL Server, we will include the programming content for each component with the rest of the component's conceptual content.

There is no general requirement that an RMO application run on a replication server. SQL Server Management Studio (SSMS) uses RMO to perform administrative tasks in replication, and you can administer replication on remote servers using SSMS. You can also synchronize subscriptions remotely using RMO (MergeSubscription.SynchronizeWithJob in the case of a push subscription), which runs the agent job on the Distributor to asynchronously start the Merge Agent. To run the Merge Agent synchronously (MergeSynchronizationAgent.Synchronize) and receive callbacks (synchronization status events), your application needs to run on the same server as the Merge Agent (the Distributor in your case).

I will see if we can make the RMO documentation more clear on this point.

Best wishes,

Glenn Gailey [MSFT]

SQL Server UE

|||

Hi Glenn & Buck,

Thanks very much for getting back to me.

I am glad to hear that the API docs will be more integrated in katmai.

On the other point I am a little confused. In our setup the merge application using RMO runs on a totally separate server to the distributor but this third machine (distributor is remote to the publisher) has SQL Express installed. We get back all the callbacks and replication is operating. I mention this because I think this kind of setup isn't really referred to in BOL but I also believe it is a permissable setup (although not perhaps a very common one).

Cheers, James

|||Is your RMO application running on the Subscriber server, or on a 4th server totally outside the Pub/Dist/Sub topology?|||

It sits on a completely separate 4th server.

Cheers, James

|||

I checked with the development team, and it is possible to run the Merge Agent remotely (both synchronously and asynchronously) using RMO. I will look into providing this information in the documentation.

Cheers!

|||Is it possible to run application that uses RMO on a server without installing SQL server? From the posts in this thread I assume the 4th server has SQLServer Express 2005 installation just to be able to run RMO app.|||

That is correct. You do need to have at least sql express installed. This is the only way to get the RMO components onto the server.

Cheers, James

Documentation of RMO and Merge Replication

Hi there,

In a lot of the Replication documentation it only refers to the merge agent operating in the context of a push or a pull configuration. i.e. if it is push then the merge agent is at the distributor but if it is a pull then the merge agent functions at the subscriber.

I recently joined a project which is configured as a push but it uses RMO for synchronisation. This RMO application is installed on a compeletely separate server. Initially I thought the RMO was just passing requests through to the publisher/distributor/subscriber but the distributor didn't seem to be doing any of the work. It therefore seems that the merging/synchronisation is being performed on this RMO application server and not the distributor or subscriber.

I therefore think it would be good (assuming I am correct of course) that the documentation reflects this caveat

As a general observation Replication programming seems to be quite detached from the rest of the replication documentation. Is this a deliberate decision?

It isn't normally, but I'll ping the writer in charge of this and ask.

Buck Woody

|||

To answer your last question first. Yes, it was a product-wide design decision to put all of the programming API documentation for SQL Server together in a separate node. I agree with you that it isn't ideal. In the next release of SQL Server, we will include the programming content for each component with the rest of the component's conceptual content.

There is no general requirement that an RMO application run on a replication server. SQL Server Management Studio (SSMS) uses RMO to perform administrative tasks in replication, and you can administer replication on remote servers using SSMS. You can also synchronize subscriptions remotely using RMO (MergeSubscription.SynchronizeWithJob in the case of a push subscription), which runs the agent job on the Distributor to asynchronously start the Merge Agent. To run the Merge Agent synchronously (MergeSynchronizationAgent.Synchronize) and receive callbacks (synchronization status events), your application needs to run on the same server as the Merge Agent (the Distributor in your case).

I will see if we can make the RMO documentation more clear on this point.

Best wishes,

Glenn Gailey [MSFT]

SQL Server UE

|||

Hi Glenn & Buck,

Thanks very much for getting back to me.

I am glad to hear that the API docs will be more integrated in katmai.

On the other point I am a little confused. In our setup the merge application using RMO runs on a totally separate server to the distributor but this third machine (distributor is remote to the publisher) has SQL Express installed. We get back all the callbacks and replication is operating. I mention this because I think this kind of setup isn't really referred to in BOL but I also believe it is a permissable setup (although not perhaps a very common one).

Cheers, James

|||Is your RMO application running on the Subscriber server, or on a 4th server totally outside the Pub/Dist/Sub topology?|||

It sits on a completely separate 4th server.

Cheers, James

|||

I checked with the development team, and it is possible to run the Merge Agent remotely (both synchronously and asynchronously) using RMO. I will look into providing this information in the documentation.

Cheers!

|||Is it possible to run application that uses RMO on a server without installing SQL server? From the posts in this thread I assume the 4th server has SQLServer Express 2005 installation just to be able to run RMO app.
|||

That is correct. You do need to have at least sql express installed. This is the only way to get the RMO components onto the server.

Cheers, James