MS Scripting bug

SQL Server 2005
I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
(after both specifying 2000 in the scripting options and
setting database compatibility to 80) still used sys.objects and WITH
(IGNORE_DUP_KEY = OFF).
Since I wasn't expecting it, it was kind of a pain.
If this is, in fact, a bug, where would I report it?You can report it at http://connect.microsoft.com
Jason Massie
Web: http://statisticsio.com
RSS: http://statisticsio.com/Home/tabid/.../1/Default.aspx
"Jay" <nospam@.nospam.org> wrote in message
news:%233LgD74NIHA.3852@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>|||Hi Jay,
I tried the same on SQL Server 2005 (Service Pack 2) and didnt find any
problem. Right click >>tasks>>generate scripts wizard generated the scripts
for indexes correctly for both 2000 and 2005.
Not sure whether in SP 2 MS resolved it.
Manu
"Jay" wrote:

> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
>