Published wish list?

Greetings,
Is there a published wish-list or a prioritised "future features" list for
Reporting Services?
Such a list would help me avoid asking if a non-existent feature has been
implemented and (maybe) give me some idea of when a particular desirable
feature may become available...
--
Regards,
Neale NOONSorry, we don't publish the wishlist. (Even if we did, it wouldn't include
current plans/priorities since those are subject to change).
--
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.
"noonie" <noonie1155@.hotmail.com> wrote in message
news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
> Greetings,
> Is there a published wish-list or a prioritised "future features" list for
> Reporting Services?
> Such a list would help me avoid asking if a non-existent feature has been
> implemented and (maybe) give me some idea of when a particular desirable
> feature may become available...
> --
> Regards,
> Neale NOON
>|||Thanks Chris,
"Chris Hays [MSFT]" <chays@.online.microsoft.com> wrote in message
news:O2PeLbMdEHA.4048@.TK2MSFTNGP12.phx.gbl...
> Sorry, we don't publish the wishlist. (Even if we did, it wouldn't
include
> current plans/priorities since those are subject to change).
Then is this the appropriate forum to "make a wish"?
1. Support for more CSS properties in RDL (background-attachment for
background images would be helpful)
2. More reliable column name discovery in the dataset designer when using
stored procedures (I want to reuse some stored procedures designed for
another application but they potentially return more than one data set and
the designer only identifies the column names of the first potential table
even after running the query with the correct parameters to select the right
data for the second potential table)
3. More rendering choices in the export report function. (RTF is high on my
list)
> "noonie" <noonie1155@.hotmail.com> wrote in message
> news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
> > Greetings,
> >
> > Is there a published wish-list or a prioritised "future features" list
for
> > Reporting Services?
> >
> > Such a list would help me avoid asking if a non-existent feature has
been
> > implemented and (maybe) give me some idea of when a particular desirable
> > feature may become available...
--
Regards,
Neale NOON|||Anytime you'd like to see something added to SQL Server, send email to
sqlwish@.microsoft.com. Those emails go directly into the mailboxes of the
folks making the decisions and are also logged into an internal database so
we can track them. You probably won't get a personal response, just an
automatic one, but these really are listened to and acted upon. Trust me.
:-)
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"noonie" <noonie1155@.hotmail.com> wrote in message
news:uKLIJfOdEHA.2352@.TK2MSFTNGP09.phx.gbl...
> Thanks Chris,
> "Chris Hays [MSFT]" <chays@.online.microsoft.com> wrote in message
> news:O2PeLbMdEHA.4048@.TK2MSFTNGP12.phx.gbl...
>> Sorry, we don't publish the wishlist. (Even if we did, it wouldn't
> include
>> current plans/priorities since those are subject to change).
> Then is this the appropriate forum to "make a wish"?
> 1. Support for more CSS properties in RDL (background-attachment for
> background images would be helpful)
> 2. More reliable column name discovery in the dataset designer when using
> stored procedures (I want to reuse some stored procedures designed for
> another application but they potentially return more than one data set and
> the designer only identifies the column names of the first potential table
> even after running the query with the correct parameters to select the
> right
> data for the second potential table)
> 3. More rendering choices in the export report function. (RTF is high on
> my
> list)
>> "noonie" <noonie1155@.hotmail.com> wrote in message
>> news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
>> > Greetings,
>> >
>> > Is there a published wish-list or a prioritised "future features" list
> for
>> > Reporting Services?
>> >
>> > Such a list would help me avoid asking if a non-existent feature has
> been
>> > implemented and (maybe) give me some idea of when a particular
>> > desirable
>> > feature may become available...
> --
> Regards,
> Neale NOON
>|||Thanks Stephen :-)
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:uftM3IadEHA.3380@.TK2MSFTNGP12.phx.gbl...
> Anytime you'd like to see something added to SQL Server, send email to
> sqlwish@.microsoft.com. Those emails go directly into the mailboxes of the
> folks making the decisions and are also logged into an internal database
so
> we can track them. You probably won't get a personal response, just an
> automatic one, but these really are listened to and acted upon. Trust me.
> :-)
> --
> Sincerely,
> Stephen Dybing
--
Regards,
Neale NOON

publication retention to increase, how to avoid missing metadata after cleanup

I currently use 7 days for subscription expiration setting for my two merge publications, which will cause metadata to clean up very 7 days. Now I need to increase the retention period to be 14 days. How I can avoid missing metadata after cleanup? Microsoft ms151188 (http://msdn2.microsoft.com/en-us/library/ms151188.aspx) warns that publisher may not have enough metadata, which may lead to non-convergence. I want to change this setting without causing any data loss.

Thanks much,

I don't think changing retention setting will cause metadata loss. Of course if you want to be 100% sure, quiesce the system and then change the setting.