Hi,
I working on Report Delivery by "Report Server File Share".
I like to add parameters into the name.
for example,
report name is "order". there are paremeter name "startdate" and "endate".
I'd like to change the filename "order_startdate_12_1_06_enddate_12_2_06"
something like that.
Is there any way to attach parameters to FileName?
Thanks
KenHi Ken,
I am not sure if you can add a parameter to change the file name at
runtime after you have created the subscription.
I can suggest Data driven subscriptions where you can execute a query
which will return all these parameters to you from the data base. You
can specify a name for the report based on your requirements and this
column can be mapped to the FileName in the subscription which will
create a file witht that name.
If you dont know what a data driven subscription is this will get you
started.
http://msdn2.microsoft.com/en-us/library/ms156012.aspx
Hope this helps,
Virat
Ken wrote:
> Hi,
> I working on Report Delivery by "Report Server File Share".
> I like to add parameters into the name.
> for example,
> report name is "order". there are paremeter name "startdate" and "endate".
> I'd like to change the filename "order_startdate_12_1_06_enddate_12_2_06"
> something like that.
> Is there any way to attach parameters to FileName?
> Thanks
> Ken
Showing posts with label subscription. Show all posts
Showing posts with label subscription. Show all posts
Monday, March 12, 2012
How to add new column in MERGE replication
I am using MERGE replication.
Subscription is done @. 17 branch offices @. various locations. It running
successfuly.
Now I want to modify the table and want to add new column to the customer
table.
What should I do. Any changes made @. publisher side, how to apply @.
subscribers side.
Best Regards
Sanjay
Sanjay - please check out sp_repladdcolumn in BOL.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Subscription is done @. 17 branch offices @. various locations. It running
successfuly.
Now I want to modify the table and want to add new column to the customer
table.
What should I do. Any changes made @. publisher side, how to apply @.
subscribers side.
Best Regards
Sanjay
Sanjay - please check out sp_repladdcolumn in BOL.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Friday, February 24, 2012
how to active a push subscriptin?
Hi all:
How to active a push subscription after created push subscription?
Cheers
nick
Drop the push subscription. At the publisher or distributor if you have a
remote distributor go to Tools, Replication, Configure Publishing,
Distributor, Subscribers. Enable your subscriber. The connect to the
subscriber, enable replication. After this go to tools, replication, create
pull subscription. Follow the prompts.
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
"Nick" <fsheng@.ebreathe.co.nz> wrote in message
news:OnRBILjCFHA.2876@.TK2MSFTNGP12.phx.gbl...
> Hi all:
> How to active a push subscription after created push subscription?
>
> Cheers
> nick
>
|||Thanks Hilary
can i ask one more question about push subscription?
i got two DB in my SQL server, call A, B for exampl. A is a publication DB,
B is push subscription DB, so whenever data been changed in B database that
will be updated in A database,
is that good way to manage in this situation?
Cheers
Nick
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:#Mme7OjCFHA.4036@.TK2MSFTNGP15.phx.gbl...
> Drop the push subscription. At the publisher or distributor if you have a
> remote distributor go to Tools, Replication, Configure Publishing,
> Distributor, Subscribers. Enable your subscriber. The connect to the
> subscriber, enable replication. After this go to tools, replication,
create
> pull subscription. Follow the prompts.
> --
> 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
> "Nick" <fsheng@.ebreathe.co.nz> wrote in message
> news:OnRBILjCFHA.2876@.TK2MSFTNGP12.phx.gbl...
>
|||No, its not. Push and pull do not refer to the direction of data movement.
Rather they refer to whether the changes are pushed from the publisher to
the subscriber, or whether the changes are pulled from the publisher to the
subscriber.
This is only valid for transactional or snapshot replication.
If you have snapshot or transactional replication with updatable
subscribers, changes which occur on the subscriber can be pushed from the
subscriber to the publisher. With merge, if you have a push subscription,
the changes are merged at the publisher and pushed to the subscriber. If you
have a pull merge subscription, the changes are merged at the publisher and
pulled to the subscriber.
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
"Nick" <fsheng@.ebreathe.co.nz> wrote in message
news:u4qlYujCFHA.1396@.TK2MSFTNGP14.phx.gbl...
> Thanks Hilary
> can i ask one more question about push subscription?
> i got two DB in my SQL server, call A, B for exampl. A is a publication
DB,
> B is push subscription DB, so whenever data been changed in B database
that[vbcol=seagreen]
> will be updated in A database,
> is that good way to manage in this situation?
> Cheers
> Nick
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:#Mme7OjCFHA.4036@.TK2MSFTNGP15.phx.gbl...
a
> create
>
|||Hi Hilary:
Do you mean only transactional or snapshot replication can handle this case,
but not merge replication?
Cheers
nick
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eTUf#0mCFHA.3376@.TK2MSFTNGP12.phx.gbl...
> No, its not. Push and pull do not refer to the direction of data movement.
> Rather they refer to whether the changes are pushed from the publisher to
> the subscriber, or whether the changes are pulled from the publisher to
the
> subscriber.
> This is only valid for transactional or snapshot replication.
> If you have snapshot or transactional replication with updatable
> subscribers, changes which occur on the subscriber can be pushed from the
> subscriber to the publisher. With merge, if you have a push subscription,
> the changes are merged at the publisher and pushed to the subscriber. If
you
> have a pull merge subscription, the changes are merged at the publisher
and[vbcol=seagreen]
> pulled to the subscriber.
> --
> 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
> "Nick" <fsheng@.ebreathe.co.nz> wrote in message
> news:u4qlYujCFHA.1396@.TK2MSFTNGP14.phx.gbl...
> DB,
> that
have
> a
>
How to active a push subscription after created push subscription?
Cheers
nick
Drop the push subscription. At the publisher or distributor if you have a
remote distributor go to Tools, Replication, Configure Publishing,
Distributor, Subscribers. Enable your subscriber. The connect to the
subscriber, enable replication. After this go to tools, replication, create
pull subscription. Follow the prompts.
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
"Nick" <fsheng@.ebreathe.co.nz> wrote in message
news:OnRBILjCFHA.2876@.TK2MSFTNGP12.phx.gbl...
> Hi all:
> How to active a push subscription after created push subscription?
>
> Cheers
> nick
>
|||Thanks Hilary
can i ask one more question about push subscription?
i got two DB in my SQL server, call A, B for exampl. A is a publication DB,
B is push subscription DB, so whenever data been changed in B database that
will be updated in A database,
is that good way to manage in this situation?
Cheers
Nick
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:#Mme7OjCFHA.4036@.TK2MSFTNGP15.phx.gbl...
> Drop the push subscription. At the publisher or distributor if you have a
> remote distributor go to Tools, Replication, Configure Publishing,
> Distributor, Subscribers. Enable your subscriber. The connect to the
> subscriber, enable replication. After this go to tools, replication,
create
> pull subscription. Follow the prompts.
> --
> 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
> "Nick" <fsheng@.ebreathe.co.nz> wrote in message
> news:OnRBILjCFHA.2876@.TK2MSFTNGP12.phx.gbl...
>
|||No, its not. Push and pull do not refer to the direction of data movement.
Rather they refer to whether the changes are pushed from the publisher to
the subscriber, or whether the changes are pulled from the publisher to the
subscriber.
This is only valid for transactional or snapshot replication.
If you have snapshot or transactional replication with updatable
subscribers, changes which occur on the subscriber can be pushed from the
subscriber to the publisher. With merge, if you have a push subscription,
the changes are merged at the publisher and pushed to the subscriber. If you
have a pull merge subscription, the changes are merged at the publisher and
pulled to the subscriber.
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
"Nick" <fsheng@.ebreathe.co.nz> wrote in message
news:u4qlYujCFHA.1396@.TK2MSFTNGP14.phx.gbl...
> Thanks Hilary
> can i ask one more question about push subscription?
> i got two DB in my SQL server, call A, B for exampl. A is a publication
DB,
> B is push subscription DB, so whenever data been changed in B database
that[vbcol=seagreen]
> will be updated in A database,
> is that good way to manage in this situation?
> Cheers
> Nick
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:#Mme7OjCFHA.4036@.TK2MSFTNGP15.phx.gbl...
a
> create
>
|||Hi Hilary:
Do you mean only transactional or snapshot replication can handle this case,
but not merge replication?
Cheers
nick
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eTUf#0mCFHA.3376@.TK2MSFTNGP12.phx.gbl...
> No, its not. Push and pull do not refer to the direction of data movement.
> Rather they refer to whether the changes are pushed from the publisher to
> the subscriber, or whether the changes are pulled from the publisher to
the
> subscriber.
> This is only valid for transactional or snapshot replication.
> If you have snapshot or transactional replication with updatable
> subscribers, changes which occur on the subscriber can be pushed from the
> subscriber to the publisher. With merge, if you have a push subscription,
> the changes are merged at the publisher and pushed to the subscriber. If
you
> have a pull merge subscription, the changes are merged at the publisher
and[vbcol=seagreen]
> pulled to the subscriber.
> --
> 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
> "Nick" <fsheng@.ebreathe.co.nz> wrote in message
> news:u4qlYujCFHA.1396@.TK2MSFTNGP14.phx.gbl...
> DB,
> that
have
> a
>
Subscribe to:
Posts (Atom)