Hi,
I have a single value paramater that with a list of choices. I have a
second parameter, that is a mulit-value paramater with the choices derived
from a query. What I would lilke to do is filter the choice of the values
in the mult-value paramter by the value selected in the first single value
paramater. Is this possible. I know this can done on a web page, but so
far as I am aware the code behind these reports is XML and I don't know
enough about it to tell it to requery the multi-value parameter's query when
the sinlge value paramater's value is selected.
Can anyone explain how to do this, or let me know of any other way of
achieving this?
TIA,
JarrydHi Jarryd,
From your description, I understnad that you would like to implement
cascading parameters selection in your report.
If I have misunderstood, please let me know.
This seems to be a typical application scenario. I recommend that you refer
to this article to see if it helps:
Lesson 2: Adding Cascading Parameters to a Report
http://msdn2.microsoft.com/en-us/library/aa337426.aspx
If you have any other questioins or concerns, please feel free to let me
know. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@.microsoft.com.
===========================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================|||Charles my man, you have done it again! Genius!
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:07X9SNFoIHA.10116@.TK2MSFTNGHUB02.phx.gbl...
> Hi Jarryd,
> From your description, I understnad that you would like to implement
> cascading parameters selection in your report.
> If I have misunderstood, please let me know.
> This seems to be a typical application scenario. I recommend that you
> refer
> to this article to see if it helps:
> Lesson 2: Adding Cascading Parameters to a Report
> http://msdn2.microsoft.com/en-us/library/aa337426.aspx
> If you have any other questioins or concerns, please feel free to let me
> know. Have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ===========================================================> Delighting our customers is our #1 priority. We welcome your
> comments and suggestions about how we can improve the
> support we provide to you. Please feel free to let my manager
> know what you think of the level of service provided. You can
> send feedback directly to my manager at: msdnmg@.microsoft.com.
> ===========================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for
> non-urgent issues where an initial response from the community
> or a Microsoft Support Engineer within 1 business day is acceptable.
> Please note that each follow up response may take approximately
> 2 business days as the support professional working with you may
> need further investigation to reach the most efficient resolution.
> The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by
> contacting Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ============================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> =========================================================>|||:) My pleasure!
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@.microsoft.com.
=========================================================This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================sql
Showing posts with label filtered. Show all posts
Showing posts with label filtered. Show all posts
Friday, March 30, 2012
Monday, March 19, 2012
Multiple ToggleItems
I have a report that utilizes five separate tables. All of the tables
are filtered by the same datetimestamp, which appears in the detail
row. Right now, I have the ToggleItem for all of the tables set to
the same text box at the top of the report. I can also set the
ToggleItem for each of the tables to a cell contained in the same
table. Is there any way to specify multiple Toggleitem values, i.e.
the text box at the top of the report AND the cell in the table
itself?No, this isn't possible.
The closest I think you can get is to have a report parameter which
determines the initial visibility state of the tables.
<Hidden>=Parameters!InitiallyHidden.Value</Hidden>
Then instead of using the top level textbox be a toggle item, you make it a
drillthrough back to the same report with the initallyhidden parameter value
set to
=Not(Parameters!InitiallyHidden.Value)
--
This post is provided 'AS IS' with no warranties, and confers no rights. All
rights reserved. Some assembly required. Batteries not included. Your
mileage may vary. Objects in mirror may be closer than they appear. No user
serviceable parts inside. Opening cover voids warranty. Keep out of reach of
children under 3.
"utterman" <chris.utter@.gmail.com> wrote in message
news:806a4b3c.0407281257.46ecf520@.posting.google.com...
> I have a report that utilizes five separate tables. All of the tables
> are filtered by the same datetimestamp, which appears in the detail
> row. Right now, I have the ToggleItem for all of the tables set to
> the same text box at the top of the report. I can also set the
> ToggleItem for each of the tables to a cell contained in the same
> table. Is there any way to specify multiple Toggleitem values, i.e.
> the text box at the top of the report AND the cell in the table
> itself?
are filtered by the same datetimestamp, which appears in the detail
row. Right now, I have the ToggleItem for all of the tables set to
the same text box at the top of the report. I can also set the
ToggleItem for each of the tables to a cell contained in the same
table. Is there any way to specify multiple Toggleitem values, i.e.
the text box at the top of the report AND the cell in the table
itself?No, this isn't possible.
The closest I think you can get is to have a report parameter which
determines the initial visibility state of the tables.
<Hidden>=Parameters!InitiallyHidden.Value</Hidden>
Then instead of using the top level textbox be a toggle item, you make it a
drillthrough back to the same report with the initallyhidden parameter value
set to
=Not(Parameters!InitiallyHidden.Value)
--
This post is provided 'AS IS' with no warranties, and confers no rights. All
rights reserved. Some assembly required. Batteries not included. Your
mileage may vary. Objects in mirror may be closer than they appear. No user
serviceable parts inside. Opening cover voids warranty. Keep out of reach of
children under 3.
"utterman" <chris.utter@.gmail.com> wrote in message
news:806a4b3c.0407281257.46ecf520@.posting.google.com...
> I have a report that utilizes five separate tables. All of the tables
> are filtered by the same datetimestamp, which appears in the detail
> row. Right now, I have the ToggleItem for all of the tables set to
> the same text box at the top of the report. I can also set the
> ToggleItem for each of the tables to a cell contained in the same
> table. Is there any way to specify multiple Toggleitem values, i.e.
> the text box at the top of the report AND the cell in the table
> itself?
Friday, March 9, 2012
multiple subscriptions in to same table
We want to publish a row filtered table where each subscriber can have
one or more of the row partitions. We'd prefer not to have separate
databases or tables for each partition at the subscriber. We've look
at various scenarios, transactional repl with DTS filter, merge
replication with dynamic join filters. Can't figure out clearly if
this would work.
Is it possible to have multiple subscriptions in to the same target
table on the subscriber, assuming the same table structure?
Seems like this could work with merge replication provided the initial
snapshot is loaded without deleting existing table structure or data
since the updates are based on rowguid which would keep things
separate.
I am a little confused about what you are trying to accomplish. You can
publish a table multiple times in the same publication or in different
publications.
If you publish a table multiple times in the same publication the
destination object name must be different. Does this answer your question?
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
<vbhackattack@.hotmail.com> wrote in message
news:1172026819.916313.105530@.k78g2000cwa.googlegr oups.com...
> We want to publish a row filtered table where each subscriber can have
> one or more of the row partitions. We'd prefer not to have separate
> databases or tables for each partition at the subscriber. We've look
> at various scenarios, transactional repl with DTS filter, merge
> replication with dynamic join filters. Can't figure out clearly if
> this would work.
> Is it possible to have multiple subscriptions in to the same target
> table on the subscriber, assuming the same table structure?
> Seems like this could work with merge replication provided the initial
> snapshot is loaded without deleting existing table structure or data
> since the updates are based on rowguid which would keep things
> separate.
>
|||On Feb 20, 7:00 pm, vbhackatt...@.hotmail.com wrote:
> We want to publish a row filtered table where each subscriber can have
> one or more of the row partitions.
> Seems like this could work with merge replication
Yes this can be done with merge replication. You need to enable the
"multiple subscribers can have data" option -- I forget what it is
called exactly -- when you create the publication.
And also you need to have filtering logic that would result in
overlapped data such as "where SalesPersonId=X or RegionId=Y"; each
SalesPerson gets their individual data and everybody that asks for
RegionId Y gets gets data for RegionId=Y.
|||I will try to restate my scenario to clarify: I would like for a
single subscriber (a site) to get 2 or more horizontal partitions of a
publication (2 or more offices' data) in to the same local subscriber
table, and be able to update them back to the publisher. I say "in to
the same local table" so the local windows application reads/writes a
single table and knows nothing about the replication configuration. I
do not want multiple tables or multiple databases one for each
horizontal partition. Reading the docs I figure replication could
possibly handle this:
- snapshots are partitioned so they can be loaded more than one in the
same table, use option not to drop existing schema
- updates with a single partition will work because insert/update/
delete only touches rows within the partition subscription
Might have to config manually since replication wizard might create
the agent jobs with overlapping names
One problem I see is if an update causes a row to disqualify for one
partition and requalify for the other partition, this would translate
in to a delete from one and insert in the other so the data gets
dropped at the subscriber and then re-downloaded. Not a big deal with
just a single table but eventually I'm extending this to multiple
tables some with lots of data in each partition.
Does that make my scenario clearer?
On Feb 21, 8:58 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> I am a little confused about what you are trying to accomplish. You can
> publish a table multiple times in the same publication or in different
> publications.
> If you publish a table multiple times in the same publication the
> destination object name must be different. Does this answer your question?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> <vbhackatt...@.hotmail.com> wrote in message
> news:1172026819.916313.105530@.k78g2000cwa.googlegr oups.com...
>
|||Yes it does. The best way to do this would be to make the single subscriber
a publisher and the other current publishers subscribers.
In this case the single publisher could start off as empty and you could use
sp_addtabletocontents on the subscribers to push their data to the
publisher.
With filtering DML on subscriber a would move to the publisher and not be
replicated to subscriber b. The partition realignments you speak of
(deleting a row on subscriber b and have it inserted on subscriber a) are
handled if you use join filters which extend the join to all child rows of a
modified parent row.
Yours is a complex scenario - have I understood it correctly?
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
<vbhackattack@.hotmail.com> wrote in message
news:1172146434.103851.121880@.l53g2000cwa.googlegr oups.com...
>I will try to restate my scenario to clarify: I would like for a
> single subscriber (a site) to get 2 or more horizontal partitions of a
> publication (2 or more offices' data) in to the same local subscriber
> table, and be able to update them back to the publisher. I say "in to
> the same local table" so the local windows application reads/writes a
> single table and knows nothing about the replication configuration. I
> do not want multiple tables or multiple databases one for each
> horizontal partition. Reading the docs I figure replication could
> possibly handle this:
> - snapshots are partitioned so they can be loaded more than one in the
> same table, use option not to drop existing schema
> - updates with a single partition will work because insert/update/
> delete only touches rows within the partition subscription
> Might have to config manually since replication wizard might create
> the agent jobs with overlapping names
> One problem I see is if an update causes a row to disqualify for one
> partition and requalify for the other partition, this would translate
> in to a delete from one and insert in the other so the data gets
> dropped at the subscriber and then re-downloaded. Not a big deal with
> just a single table but eventually I'm extending this to multiple
> tables some with lots of data in each partition.
> Does that make my scenario clearer?
> On Feb 21, 8:58 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
>
one or more of the row partitions. We'd prefer not to have separate
databases or tables for each partition at the subscriber. We've look
at various scenarios, transactional repl with DTS filter, merge
replication with dynamic join filters. Can't figure out clearly if
this would work.
Is it possible to have multiple subscriptions in to the same target
table on the subscriber, assuming the same table structure?
Seems like this could work with merge replication provided the initial
snapshot is loaded without deleting existing table structure or data
since the updates are based on rowguid which would keep things
separate.
I am a little confused about what you are trying to accomplish. You can
publish a table multiple times in the same publication or in different
publications.
If you publish a table multiple times in the same publication the
destination object name must be different. Does this answer your question?
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
<vbhackattack@.hotmail.com> wrote in message
news:1172026819.916313.105530@.k78g2000cwa.googlegr oups.com...
> We want to publish a row filtered table where each subscriber can have
> one or more of the row partitions. We'd prefer not to have separate
> databases or tables for each partition at the subscriber. We've look
> at various scenarios, transactional repl with DTS filter, merge
> replication with dynamic join filters. Can't figure out clearly if
> this would work.
> Is it possible to have multiple subscriptions in to the same target
> table on the subscriber, assuming the same table structure?
> Seems like this could work with merge replication provided the initial
> snapshot is loaded without deleting existing table structure or data
> since the updates are based on rowguid which would keep things
> separate.
>
|||On Feb 20, 7:00 pm, vbhackatt...@.hotmail.com wrote:
> We want to publish a row filtered table where each subscriber can have
> one or more of the row partitions.
> Seems like this could work with merge replication
Yes this can be done with merge replication. You need to enable the
"multiple subscribers can have data" option -- I forget what it is
called exactly -- when you create the publication.
And also you need to have filtering logic that would result in
overlapped data such as "where SalesPersonId=X or RegionId=Y"; each
SalesPerson gets their individual data and everybody that asks for
RegionId Y gets gets data for RegionId=Y.
|||I will try to restate my scenario to clarify: I would like for a
single subscriber (a site) to get 2 or more horizontal partitions of a
publication (2 or more offices' data) in to the same local subscriber
table, and be able to update them back to the publisher. I say "in to
the same local table" so the local windows application reads/writes a
single table and knows nothing about the replication configuration. I
do not want multiple tables or multiple databases one for each
horizontal partition. Reading the docs I figure replication could
possibly handle this:
- snapshots are partitioned so they can be loaded more than one in the
same table, use option not to drop existing schema
- updates with a single partition will work because insert/update/
delete only touches rows within the partition subscription
Might have to config manually since replication wizard might create
the agent jobs with overlapping names
One problem I see is if an update causes a row to disqualify for one
partition and requalify for the other partition, this would translate
in to a delete from one and insert in the other so the data gets
dropped at the subscriber and then re-downloaded. Not a big deal with
just a single table but eventually I'm extending this to multiple
tables some with lots of data in each partition.
Does that make my scenario clearer?
On Feb 21, 8:58 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> I am a little confused about what you are trying to accomplish. You can
> publish a table multiple times in the same publication or in different
> publications.
> If you publish a table multiple times in the same publication the
> destination object name must be different. Does this answer your question?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> <vbhackatt...@.hotmail.com> wrote in message
> news:1172026819.916313.105530@.k78g2000cwa.googlegr oups.com...
>
|||Yes it does. The best way to do this would be to make the single subscriber
a publisher and the other current publishers subscribers.
In this case the single publisher could start off as empty and you could use
sp_addtabletocontents on the subscribers to push their data to the
publisher.
With filtering DML on subscriber a would move to the publisher and not be
replicated to subscriber b. The partition realignments you speak of
(deleting a row on subscriber b and have it inserted on subscriber a) are
handled if you use join filters which extend the join to all child rows of a
modified parent row.
Yours is a complex scenario - have I understood it correctly?
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
<vbhackattack@.hotmail.com> wrote in message
news:1172146434.103851.121880@.l53g2000cwa.googlegr oups.com...
>I will try to restate my scenario to clarify: I would like for a
> single subscriber (a site) to get 2 or more horizontal partitions of a
> publication (2 or more offices' data) in to the same local subscriber
> table, and be able to update them back to the publisher. I say "in to
> the same local table" so the local windows application reads/writes a
> single table and knows nothing about the replication configuration. I
> do not want multiple tables or multiple databases one for each
> horizontal partition. Reading the docs I figure replication could
> possibly handle this:
> - snapshots are partitioned so they can be loaded more than one in the
> same table, use option not to drop existing schema
> - updates with a single partition will work because insert/update/
> delete only touches rows within the partition subscription
> Might have to config manually since replication wizard might create
> the agent jobs with overlapping names
> One problem I see is if an update causes a row to disqualify for one
> partition and requalify for the other partition, this would translate
> in to a delete from one and insert in the other so the data gets
> dropped at the subscriber and then re-downloaded. Not a big deal with
> just a single table but eventually I'm extending this to multiple
> tables some with lots of data in each partition.
> Does that make my scenario clearer?
> On Feb 21, 8:58 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
>
Subscribe to:
Posts (Atom)