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

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
> >
> >
>