Hi all.
I've been working with RS for a month or so migrating all our client-side
reports (MS Access) to server-side (RS). I have a bunch of them to be
converted yet but I think I have some experience and can do some suggestions
to a product that is a very good product to be the 1st version. I hope next
version in SQL Server 2005 improves some things like:
* Add the option to select a RGB color for using it as transparency for the
Image control: You can add transparencies to the images themselves when
using GIF or PNG formats. However when images are bitmaps, since bitmap
format does not have support for transparency layers, it would be usefull to
have that support from RS itself.
* Render to .SNP format (MS Access Snapshot format).
* Within the VS IDE, when you copy a group of controls and paste them in
another report, they are not located at the same X,Y positions as they were
in the original report, but at the middle/center of the space they have been
inserted into (parent). I think that report designers would prefer to paste
the copied controls in the place they were instead of another coordinates
that sometimes are not aligned to the grid either (even though align to grid
is active).
* When you copy a control named MyUserRenamedControl1 (a textbox for
instance) and paste into the same report, since that control name is already
used, the new control is named TexboxX (being X a free number that makes the
name unique in the report). I think that if report designers have renamed a
default name component to another name (for whatever the reason), the IDE
should try to keep the same name and add numbers to the end of the name that
the designer has selected. In this case the names of new controls should be
MyUserRenamedControl2, MyUserRenamedControl3, etc.
* Rounded corners for rectangles, components for circles, ellipses, oblique
text (number of degrees selectable). This might be of less use for many
people, mainly when they use RS to generate pure-listing reports. However if
you use RS to generate invoices or other kind of documents that need quality
and be visually attractive, this kind of improvements would help a lot.
Regards and congratulations for such a good work.Also, report headers and footers, to supplement page headers and
footers.|||Report headers and footers are equivalent to objects that appear before any
data regions.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Parker" <psmith@.iquest.net> wrote in message
news:1116090620.154601.166470@.g49g2000cwa.googlegroups.com...
> Also, report headers and footers, to supplement page headers and
> footers.
>
Showing posts with label request. Show all posts
Showing posts with label request. Show all posts
Friday, March 23, 2012
feature requests to MS? How? Where?
Hi,
Anyone know how to request features for SQL server?
eg "reverse index" - like a phone number, if it was
reversed in the index it would be highly selective and low
density which would make it a lot faster. In Sydney
Australia most numbers have a 9 in the begining...
eg #2. "Ent. Mgr, diagrams across 2 or more databases".
Currently you can only diagram across one db at a time. I
have multiple db related.
eg #3. "programing sql trees". Support for programing sql
trees / parent child relationships.
And all sorts of other stuff developers and dba's need.
Cheers,
JohnSend email to :- sqlwish@.microsoft.com
--
HTH
Ryan Waight, MCDBA, MCSE
"John" <john.reed@.ht.com.au> wrote in message
news:0b4a01c3a455$57b94180$a301280a@.phx.gbl...
> Hi,
> Anyone know how to request features for SQL server?
> eg "reverse index" - like a phone number, if it was
> reversed in the index it would be highly selective and low
> density which would make it a lot faster. In Sydney
> Australia most numbers have a 9 in the begining...
> eg #2. "Ent. Mgr, diagrams across 2 or more databases".
> Currently you can only diagram across one db at a time. I
> have multiple db related.
> eg #3. "programing sql trees". Support for programing sql
> trees / parent child relationships.
> And all sorts of other stuff developers and dba's need.
> Cheers,
> John|||"John" <john.reed@.ht.com.au> wrote in message
news:0b4a01c3a455$57b94180$a301280a@.phx.gbl...
> eg "reverse index" - like a phone number, if it was
> reversed in the index it would be highly selective and low
> density which would make it a lot faster. In Sydney
> Australia most numbers have a 9 in the begining...
Store them backwards...
> eg #3. "programing sql trees". Support for programing sql
> trees / parent child relationships.
How is this not already supported?
Anyone know how to request features for SQL server?
eg "reverse index" - like a phone number, if it was
reversed in the index it would be highly selective and low
density which would make it a lot faster. In Sydney
Australia most numbers have a 9 in the begining...
eg #2. "Ent. Mgr, diagrams across 2 or more databases".
Currently you can only diagram across one db at a time. I
have multiple db related.
eg #3. "programing sql trees". Support for programing sql
trees / parent child relationships.
And all sorts of other stuff developers and dba's need.
Cheers,
JohnSend email to :- sqlwish@.microsoft.com
--
HTH
Ryan Waight, MCDBA, MCSE
"John" <john.reed@.ht.com.au> wrote in message
news:0b4a01c3a455$57b94180$a301280a@.phx.gbl...
> Hi,
> Anyone know how to request features for SQL server?
> eg "reverse index" - like a phone number, if it was
> reversed in the index it would be highly selective and low
> density which would make it a lot faster. In Sydney
> Australia most numbers have a 9 in the begining...
> eg #2. "Ent. Mgr, diagrams across 2 or more databases".
> Currently you can only diagram across one db at a time. I
> have multiple db related.
> eg #3. "programing sql trees". Support for programing sql
> trees / parent child relationships.
> And all sorts of other stuff developers and dba's need.
> Cheers,
> John|||"John" <john.reed@.ht.com.au> wrote in message
news:0b4a01c3a455$57b94180$a301280a@.phx.gbl...
> eg "reverse index" - like a phone number, if it was
> reversed in the index it would be highly selective and low
> density which would make it a lot faster. In Sydney
> Australia most numbers have a 9 in the begining...
Store them backwards...
> eg #3. "programing sql trees". Support for programing sql
> trees / parent child relationships.
How is this not already supported?
Feature request: Show login name at home page
in order to see under which account one is currently logged in. This would
be usefull in development state.
rolandTry
User!UserID
"Roland" <nomail@.spamprotect.com> wrote in message
news:u6NCJ7VXEHA.3016@.tk2msftngp13.phx.gbl...
> in order to see under which account one is currently logged in. This would
> be usefull in development state.
> roland
>|||Cool. Thanks. But I wanted to see this on the homepage, not in a report
roland
be usefull in development state.
rolandTry
User!UserID
"Roland" <nomail@.spamprotect.com> wrote in message
news:u6NCJ7VXEHA.3016@.tk2msftngp13.phx.gbl...
> in order to see under which account one is currently logged in. This would
> be usefull in development state.
> roland
>|||Cool. Thanks. But I wanted to see this on the homepage, not in a report
roland
FEATURE REQUEST: Jump to Report with rs:, rc: parameters
FEATURE REQUEST (already submitted to sqlwish@.microsoft.com): Allow rs: and
rc: parameters as an exception to the "CLR-compliant parameter name" rule
within Navigation Parameter properties.
Background: I have created a custom report manager that displays reports
within an IFRAME. With URL access, the rc:LinkTarget points to the IFRAME
name.
Problem: Using the "Jump to report" navigation does not carry the
rc:LinkTarget=iframename parameter forward to the linked report. Subsequent
clicks break the report out of the IFRAME. The workaround, dynamically
creating the URL, is cumbersome and limits report portability. In the
Navigation tab (Parameters button), I tried to set rc:LinkTarget as a
parameter with iframename as the value, which produced a compilation error,
that parameter names must be CLR-compliant. This is true except for rs: and
rc: parameters. Please consider allowing a report to compile and publish
with rs: and rc: parameters specified in the Jump to... links.
Thanks,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---I should have mentioned an alternative (also sent to sqlwish):
FEATURE REQUEST ALTERNATIVE: Provide an option to automatically carry
rc:LinkTarget paramters forward in linked (Jump to) reports.
Thanks,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Jeff A. Stucker" <jeff@.mobilize.net> wrote in message
news:usQBm8DzEHA.2624@.TK2MSFTNGP11.phx.gbl...
> FEATURE REQUEST (already submitted to sqlwish@.microsoft.com): Allow rs:
> and rc: parameters as an exception to the "CLR-compliant parameter name"
> rule within Navigation Parameter properties.
> Background: I have created a custom report manager that displays reports
> within an IFRAME. With URL access, the rc:LinkTarget points to the IFRAME
> name.
> Problem: Using the "Jump to report" navigation does not carry the
> rc:LinkTarget=iframename parameter forward to the linked report.
> Subsequent clicks break the report out of the IFRAME. The workaround,
> dynamically creating the URL, is cumbersome and limits report portability.
> In the Navigation tab (Parameters button), I tried to set rc:LinkTarget as
> a parameter with iframename as the value, which produced a compilation
> error, that parameter names must be CLR-compliant. This is true except for
> rs: and rc: parameters. Please consider allowing a report to compile and
> publish with rs: and rc: parameters specified in the Jump to... links.
> Thanks,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
>
rc: parameters as an exception to the "CLR-compliant parameter name" rule
within Navigation Parameter properties.
Background: I have created a custom report manager that displays reports
within an IFRAME. With URL access, the rc:LinkTarget points to the IFRAME
name.
Problem: Using the "Jump to report" navigation does not carry the
rc:LinkTarget=iframename parameter forward to the linked report. Subsequent
clicks break the report out of the IFRAME. The workaround, dynamically
creating the URL, is cumbersome and limits report portability. In the
Navigation tab (Parameters button), I tried to set rc:LinkTarget as a
parameter with iframename as the value, which produced a compilation error,
that parameter names must be CLR-compliant. This is true except for rs: and
rc: parameters. Please consider allowing a report to compile and publish
with rs: and rc: parameters specified in the Jump to... links.
Thanks,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---I should have mentioned an alternative (also sent to sqlwish):
FEATURE REQUEST ALTERNATIVE: Provide an option to automatically carry
rc:LinkTarget paramters forward in linked (Jump to) reports.
Thanks,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Jeff A. Stucker" <jeff@.mobilize.net> wrote in message
news:usQBm8DzEHA.2624@.TK2MSFTNGP11.phx.gbl...
> FEATURE REQUEST (already submitted to sqlwish@.microsoft.com): Allow rs:
> and rc: parameters as an exception to the "CLR-compliant parameter name"
> rule within Navigation Parameter properties.
> Background: I have created a custom report manager that displays reports
> within an IFRAME. With URL access, the rc:LinkTarget points to the IFRAME
> name.
> Problem: Using the "Jump to report" navigation does not carry the
> rc:LinkTarget=iframename parameter forward to the linked report.
> Subsequent clicks break the report out of the IFRAME. The workaround,
> dynamically creating the URL, is cumbersome and limits report portability.
> In the Navigation tab (Parameters button), I tried to set rc:LinkTarget as
> a parameter with iframename as the value, which produced a compilation
> error, that parameter names must be CLR-compliant. This is true except for
> rs: and rc: parameters. Please consider allowing a report to compile and
> publish with rs: and rc: parameters specified in the Jump to... links.
> Thanks,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
>
Feature request: Code packages
Hi. One feature that would be great for SQL Server is the ability to wrap your code (functions, stored procs) in a package, like you can on Oracle. Then when moving code to production, you can just move the package. This might already be possible and I'm not familiar with how to do it. This would make a great database even better. Thanks 
Many folks typically do that by using the Source Code Control tool.
(You do use a Source Code tool, don't you?)
Otherwise, in order to post a suggestion that will be considered by the SQL Server development team, visit this link.
Suggestions for SQL Server
http://connect.microsoft.com/sqlserver
Feature Request: ANSI/MS Access Unique Key Implementation
Not sure if this is the right place to post this, but:
In a future release of SQL Server, could there be an option that would implement the ANSI/MS Access version of a Unique Key.
As I understand it, the implementation of Unique Key in SQL Server considers Null as one of the values, so that there can only be one entry in the field with Null.
In MS Access and, as I understand it, in the ANSI Standard, there is an option to ignore Null entries in a Unique Key field. In this implementation, there can be many instances where Null is used, but each non-Null value must be unique.
I am building a database and in one of my tables, the field identifies a predecessor record, which could be either Null or one of the other records in the table. In order to ensure that a record is only used once, I would have liked to use the Unique Key, but can't. So, I have had to build a second table, with triggers and foreign keys, and it is ugly. Would have been so much simpler with an ANSI Unique Key.
I understand that this would have to be an option, since there is existing code that probably depends on the current implementation of the Unique Key in SQL Server, but it would have been nice to have the option to use the ANSI Implementation.
Thanks,
Flavelle
Regards,
FlavelleLow priority - the workaround is to build a schema-bound view containing the column to be indexed where the content of the column includes only those non-Null value. A unique index can then be applied to the view.sql
Feature Request: 2005 Beta 2
Greetings,
I have a feature request for the Enterprise Studio.
We have about 500+ stored procedures in our CRM application and opening up
Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at a
huge list of stored procedures and find the one I'm specifically looking
for. Granted, in 2005 there is a "filter" it is rather unintuitive.
I'd like to request the abililty to add my own "folder" to the list where I
can create categories to group my stored procedures. for example, I can
create a "Invoices" group where all my invoice related SP's go, and a
"Policies" group where all my policies related SP's will go. In addition to
this, we have more tables than SPs, so we should be able to group any
object, Table, SP, View, etc.
Not sure if you've considered this already but the filtering isn't as
intuitive. It requires me to have to constantly enter in new filters to
filter the list before I can browse around. I'd like to browse directly to
what I'm looking for.
Thanks,
Shawn
Hi Shawn,
Have you considered using Schemas for this? (Introduced in SQL Server 2005
also).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shawn B." <leabre@.html.com> wrote in message
news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
> Greetings,
> I have a feature request for the Enterprise Studio.
> We have about 500+ stored procedures in our CRM application and opening up
> Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at
> a
> huge list of stored procedures and find the one I'm specifically looking
> for. Granted, in 2005 there is a "filter" it is rather unintuitive.
> I'd like to request the abililty to add my own "folder" to the list where
> I
> can create categories to group my stored procedures. for example, I can
> create a "Invoices" group where all my invoice related SP's go, and a
> "Policies" group where all my policies related SP's will go. In addition
> to
> this, we have more tables than SPs, so we should be able to group any
> object, Table, SP, View, etc.
> Not sure if you've considered this already but the filtering isn't as
> intuitive. It requires me to have to constantly enter in new filters to
> filter the list before I can browse around. I'd like to browse directly
> to
> what I'm looking for.
>
> Thanks,
> Shawn
>
|||What are schemas in this context? after a cursory google and help topics
lookup, I have no clue what they can do for me.
Thanks,
Shawn
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:e8NiNJ8zEHA.2528@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi Shawn,
> Have you considered using Schemas for this? (Introduced in SQL Server 2005
> also).
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Shawn B." <leabre@.html.com> wrote in message
> news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
up[vbcol=seagreen]
at[vbcol=seagreen]
where[vbcol=seagreen]
addition
>
|||I believe this has been suggested before but to make sure please send the
details of your request to sqlwish@.microsoft.com
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Shawn B." <leabre@.html.com> wrote in message
news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
> Greetings,
> I have a feature request for the Enterprise Studio.
> We have about 500+ stored procedures in our CRM application and opening up
> Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at
> a
> huge list of stored procedures and find the one I'm specifically looking
> for. Granted, in 2005 there is a "filter" it is rather unintuitive.
> I'd like to request the abililty to add my own "folder" to the list where
> I
> can create categories to group my stored procedures. for example, I can
> create a "Invoices" group where all my invoice related SP's go, and a
> "Policies" group where all my policies related SP's will go. In addition
> to
> this, we have more tables than SPs, so we should be able to group any
> object, Table, SP, View, etc.
> Not sure if you've considered this already but the filtering isn't as
> intuitive. It requires me to have to constantly enter in new filters to
> filter the list before I can browse around. I'd like to browse directly
> to
> what I'm looking for.
>
> Thanks,
> Shawn
>
|||Hi Shawn,
Take a look at the Northwind sample database in SQL Server 2005 Beta if you
have access to it from the MSDN site. Whereas Northwind's tables, procs,
etc. before were just one big list, now there are separate schemas for
HumanResources, etc. with only those objects relevant to that part of the
app in them.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shawn B." <leabre@.html.com> wrote in message
news:OWVSG5A0EHA.1192@.tk2msftngp13.phx.gbl...
> What are schemas in this context? after a cursory google and help topics
> lookup, I have no clue what they can do for me.
>
> Thanks,
> Shawn
>
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:e8NiNJ8zEHA.2528@.TK2MSFTNGP10.phx.gbl...
> up
> at
> where
> addition
>
|||Sorry, brain explosion - meant to point you to the Adventureworks sample,
not Northwind.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:OLy2UoU0EHA.3244@.TK2MSFTNGP10.phx.gbl...
> Hi Shawn,
> Take a look at the Northwind sample database in SQL Server 2005 Beta if
> you have access to it from the MSDN site. Whereas Northwind's tables,
> procs, etc. before were just one big list, now there are separate schemas
> for HumanResources, etc. with only those objects relevant to that part of
> the app in them.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Shawn B." <leabre@.html.com> wrote in message
> news:OWVSG5A0EHA.1192@.tk2msftngp13.phx.gbl...
>
I have a feature request for the Enterprise Studio.
We have about 500+ stored procedures in our CRM application and opening up
Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at a
huge list of stored procedures and find the one I'm specifically looking
for. Granted, in 2005 there is a "filter" it is rather unintuitive.
I'd like to request the abililty to add my own "folder" to the list where I
can create categories to group my stored procedures. for example, I can
create a "Invoices" group where all my invoice related SP's go, and a
"Policies" group where all my policies related SP's will go. In addition to
this, we have more tables than SPs, so we should be able to group any
object, Table, SP, View, etc.
Not sure if you've considered this already but the filtering isn't as
intuitive. It requires me to have to constantly enter in new filters to
filter the list before I can browse around. I'd like to browse directly to
what I'm looking for.
Thanks,
Shawn
Hi Shawn,
Have you considered using Schemas for this? (Introduced in SQL Server 2005
also).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shawn B." <leabre@.html.com> wrote in message
news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
> Greetings,
> I have a feature request for the Enterprise Studio.
> We have about 500+ stored procedures in our CRM application and opening up
> Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at
> a
> huge list of stored procedures and find the one I'm specifically looking
> for. Granted, in 2005 there is a "filter" it is rather unintuitive.
> I'd like to request the abililty to add my own "folder" to the list where
> I
> can create categories to group my stored procedures. for example, I can
> create a "Invoices" group where all my invoice related SP's go, and a
> "Policies" group where all my policies related SP's will go. In addition
> to
> this, we have more tables than SPs, so we should be able to group any
> object, Table, SP, View, etc.
> Not sure if you've considered this already but the filtering isn't as
> intuitive. It requires me to have to constantly enter in new filters to
> filter the list before I can browse around. I'd like to browse directly
> to
> what I'm looking for.
>
> Thanks,
> Shawn
>
|||What are schemas in this context? after a cursory google and help topics
lookup, I have no clue what they can do for me.
Thanks,
Shawn
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:e8NiNJ8zEHA.2528@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi Shawn,
> Have you considered using Schemas for this? (Introduced in SQL Server 2005
> also).
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Shawn B." <leabre@.html.com> wrote in message
> news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
up[vbcol=seagreen]
at[vbcol=seagreen]
where[vbcol=seagreen]
addition
>
|||I believe this has been suggested before but to make sure please send the
details of your request to sqlwish@.microsoft.com
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Shawn B." <leabre@.html.com> wrote in message
news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
> Greetings,
> I have a feature request for the Enterprise Studio.
> We have about 500+ stored procedures in our CRM application and opening up
> Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at
> a
> huge list of stored procedures and find the one I'm specifically looking
> for. Granted, in 2005 there is a "filter" it is rather unintuitive.
> I'd like to request the abililty to add my own "folder" to the list where
> I
> can create categories to group my stored procedures. for example, I can
> create a "Invoices" group where all my invoice related SP's go, and a
> "Policies" group where all my policies related SP's will go. In addition
> to
> this, we have more tables than SPs, so we should be able to group any
> object, Table, SP, View, etc.
> Not sure if you've considered this already but the filtering isn't as
> intuitive. It requires me to have to constantly enter in new filters to
> filter the list before I can browse around. I'd like to browse directly
> to
> what I'm looking for.
>
> Thanks,
> Shawn
>
|||Hi Shawn,
Take a look at the Northwind sample database in SQL Server 2005 Beta if you
have access to it from the MSDN site. Whereas Northwind's tables, procs,
etc. before were just one big list, now there are separate schemas for
HumanResources, etc. with only those objects relevant to that part of the
app in them.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shawn B." <leabre@.html.com> wrote in message
news:OWVSG5A0EHA.1192@.tk2msftngp13.phx.gbl...
> What are schemas in this context? after a cursory google and help topics
> lookup, I have no clue what they can do for me.
>
> Thanks,
> Shawn
>
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:e8NiNJ8zEHA.2528@.TK2MSFTNGP10.phx.gbl...
> up
> at
> where
> addition
>
|||Sorry, brain explosion - meant to point you to the Adventureworks sample,
not Northwind.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:OLy2UoU0EHA.3244@.TK2MSFTNGP10.phx.gbl...
> Hi Shawn,
> Take a look at the Northwind sample database in SQL Server 2005 Beta if
> you have access to it from the MSDN site. Whereas Northwind's tables,
> procs, etc. before were just one big list, now there are separate schemas
> for HumanResources, etc. with only those objects relevant to that part of
> the app in them.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Shawn B." <leabre@.html.com> wrote in message
> news:OWVSG5A0EHA.1192@.tk2msftngp13.phx.gbl...
>
Feature request
Some of our users who may be running packages are not so adept at editing XML configuration files. It'd be nice if we could instead either:
1. Have an interface to modify the XML dtsConfig files
or 2. Have another option that would prompt via dialog box for the configuration options when the DTS package is run.
On #1, anyone know of any existing programs that would be useful (something that would ignore the markup and just edit the variables)?
Thanks for the request, Jonathan. It's on our list of things to consider for the next version, we just didn't have the time to get it into SQL Server 2005.
1. Have an interface to modify the XML dtsConfig files
or 2. Have another option that would prompt via dialog box for the configuration options when the DTS package is run.
On #1, anyone know of any existing programs that would be useful (something that would ignore the markup and just edit the variables)?
Thanks for the request, Jonathan. It's on our list of things to consider for the next version, we just didn't have the time to get it into SQL Server 2005.
regards,
ash
Feature request
Hi,
It would be very nice if the following feature would somehow be implemented
in future releases:
- A report with two datasets
- A list on the report consuming records from dataset 1
- A list inside the existing list consuming records from dataset 2 with a
filter defined that allows an expression on a value from the current record
in dataset 1
This would allow us to create a master-detail report consuming two different
databases/queries without using sub-reports.
Thanks,
ErikThank you for your input. We have considered adding join functionality, but
have not scheduled the work for a particular release.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Erik Tamminga" <newsgroups@.NeOtammiSnPgAaM.nl> wrote in message
news:cbkt5q$m1m$1@.news5.tilbu1.nb.home.nl...
> Hi,
> It would be very nice if the following feature would somehow be
implemented
> in future releases:
> - A report with two datasets
> - A list on the report consuming records from dataset 1
> - A list inside the existing list consuming records from dataset 2 with a
> filter defined that allows an expression on a value from the current
record
> in dataset 1
> This would allow us to create a master-detail report consuming two
different
> databases/queries without using sub-reports.
> Thanks,
> Erik
>|||Hi,
Yes, reporting services almost contains all the required functionality, but
when defining the filter on the second list (bound to the second dataset)
you don't have the option to match a field from the current record on the
first/parent list.
Erik
"chanley54" <chanley54@.discussions.microsoft.com> schreef in bericht
news:2717F0E8-2847-4DD7-A29F-81B2459F318F@.microsoft.com...
> Erik,
> It already supports multiple datasets. On the data region, click the
drop-down and you should see "New Dataset". If you want your other dataset
to use a different datasource simply add another datasource to the project.
> I believe that once you do this you will also not have an issue with
section 2 of your feature request. HTH
> "Erik Tamminga" wrote:
> > Hi,
> >
> > It would be very nice if the following feature would somehow be
implemented
> > in future releases:
> >
> > - A report with two datasets
> > - A list on the report consuming records from dataset 1
> > - A list inside the existing list consuming records from dataset 2 with
a
> > filter defined that allows an expression on a value from the current
record
> > in dataset 1
> >
> > This would allow us to create a master-detail report consuming two
different
> > databases/queries without using sub-reports.
> >
> > Thanks,
> >
> > Erik
> >
> >
> >|||Yes, this is heterogenous join. While it is simple to design, it is pretty
complex to make it perform. It is high on the list for a future release.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Erik Tamminga" <newsgroups@.NeOtammiSnPgAaM.nl> wrote in message
news:cbkt5q$m1m$1@.news5.tilbu1.nb.home.nl...
> Hi,
> It would be very nice if the following feature would somehow be
> implemented
> in future releases:
> - A report with two datasets
> - A list on the report consuming records from dataset 1
> - A list inside the existing list consuming records from dataset 2 with a
> filter defined that allows an expression on a value from the current
> record
> in dataset 1
> This would allow us to create a master-detail report consuming two
> different
> databases/queries without using sub-reports.
> Thanks,
> Erik
>|||Hi Brian,
If only I could allow the filter to evaluate fields of the current record of
other datasets .... (doesn't sound too hard to implement).
You'll find me among the people waiting for the future release! But, good
job so far!
Erik
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> schreef in bericht
news:uYLtvH0XEHA.2408@.tk2msftngp13.phx.gbl...
> Yes, this is heterogenous join. While it is simple to design, it is pretty
> complex to make it perform. It is high on the list for a future release.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Erik Tamminga" <newsgroups@.NeOtammiSnPgAaM.nl> wrote in message
> news:cbkt5q$m1m$1@.news5.tilbu1.nb.home.nl...
> > Hi,
> >
> > It would be very nice if the following feature would somehow be
> > implemented
> > in future releases:
> >
> > - A report with two datasets
> > - A list on the report consuming records from dataset 1
> > - A list inside the existing list consuming records from dataset 2 with
a
> > filter defined that allows an expression on a value from the current
> > record
> > in dataset 1
> >
> > This would allow us to create a master-detail report consuming two
> > different
> > databases/queries without using sub-reports.
> >
> > Thanks,
> >
> > Erik
> >
> >
>
It would be very nice if the following feature would somehow be implemented
in future releases:
- A report with two datasets
- A list on the report consuming records from dataset 1
- A list inside the existing list consuming records from dataset 2 with a
filter defined that allows an expression on a value from the current record
in dataset 1
This would allow us to create a master-detail report consuming two different
databases/queries without using sub-reports.
Thanks,
ErikThank you for your input. We have considered adding join functionality, but
have not scheduled the work for a particular release.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Erik Tamminga" <newsgroups@.NeOtammiSnPgAaM.nl> wrote in message
news:cbkt5q$m1m$1@.news5.tilbu1.nb.home.nl...
> Hi,
> It would be very nice if the following feature would somehow be
implemented
> in future releases:
> - A report with two datasets
> - A list on the report consuming records from dataset 1
> - A list inside the existing list consuming records from dataset 2 with a
> filter defined that allows an expression on a value from the current
record
> in dataset 1
> This would allow us to create a master-detail report consuming two
different
> databases/queries without using sub-reports.
> Thanks,
> Erik
>|||Hi,
Yes, reporting services almost contains all the required functionality, but
when defining the filter on the second list (bound to the second dataset)
you don't have the option to match a field from the current record on the
first/parent list.
Erik
"chanley54" <chanley54@.discussions.microsoft.com> schreef in bericht
news:2717F0E8-2847-4DD7-A29F-81B2459F318F@.microsoft.com...
> Erik,
> It already supports multiple datasets. On the data region, click the
drop-down and you should see "New Dataset". If you want your other dataset
to use a different datasource simply add another datasource to the project.
> I believe that once you do this you will also not have an issue with
section 2 of your feature request. HTH
> "Erik Tamminga" wrote:
> > Hi,
> >
> > It would be very nice if the following feature would somehow be
implemented
> > in future releases:
> >
> > - A report with two datasets
> > - A list on the report consuming records from dataset 1
> > - A list inside the existing list consuming records from dataset 2 with
a
> > filter defined that allows an expression on a value from the current
record
> > in dataset 1
> >
> > This would allow us to create a master-detail report consuming two
different
> > databases/queries without using sub-reports.
> >
> > Thanks,
> >
> > Erik
> >
> >
> >|||Yes, this is heterogenous join. While it is simple to design, it is pretty
complex to make it perform. It is high on the list for a future release.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Erik Tamminga" <newsgroups@.NeOtammiSnPgAaM.nl> wrote in message
news:cbkt5q$m1m$1@.news5.tilbu1.nb.home.nl...
> Hi,
> It would be very nice if the following feature would somehow be
> implemented
> in future releases:
> - A report with two datasets
> - A list on the report consuming records from dataset 1
> - A list inside the existing list consuming records from dataset 2 with a
> filter defined that allows an expression on a value from the current
> record
> in dataset 1
> This would allow us to create a master-detail report consuming two
> different
> databases/queries without using sub-reports.
> Thanks,
> Erik
>|||Hi Brian,
If only I could allow the filter to evaluate fields of the current record of
other datasets .... (doesn't sound too hard to implement).
You'll find me among the people waiting for the future release! But, good
job so far!
Erik
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> schreef in bericht
news:uYLtvH0XEHA.2408@.tk2msftngp13.phx.gbl...
> Yes, this is heterogenous join. While it is simple to design, it is pretty
> complex to make it perform. It is high on the list for a future release.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Erik Tamminga" <newsgroups@.NeOtammiSnPgAaM.nl> wrote in message
> news:cbkt5q$m1m$1@.news5.tilbu1.nb.home.nl...
> > Hi,
> >
> > It would be very nice if the following feature would somehow be
> > implemented
> > in future releases:
> >
> > - A report with two datasets
> > - A list on the report consuming records from dataset 1
> > - A list inside the existing list consuming records from dataset 2 with
a
> > filter defined that allows an expression on a value from the current
> > record
> > in dataset 1
> >
> > This would allow us to create a master-detail report consuming two
> > different
> > databases/queries without using sub-reports.
> >
> > Thanks,
> >
> > Erik
> >
> >
>
Subscribe to:
Posts (Atom)