Very Computer

by **Ivan Arjentinsk** » Thu, 23 Aug 2001 19:23:18

Hi all,

While playing with EM I received easily reproducible error situation.

Steps:
1. Start creating new table.
2. Create a column (in the example a, type CHAR(10)).
3. Type description of the column.
4. Create other columns (in the example: column b of type CHAR(10))
5. Delete the column (a).
6. Try to save the table (Table1)

This leads to error message similar to:

'Table1' table
- Unable to create table.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Object is
invalid. Extended properties are not permitted on 'dbo.Table1.a', or the
object does not exist.

This is minor bug. But sometimes it might be annoying since one can define a
whole new table with many columns and fail to save his job....

BTW, possible workaround: Save the script, copy to QA, modify, execute.

Q1. Is this known bug? Where can we check?

I don't want to open support case for such a minor bug...

--
Ivan Arjentinski

-----------------------------------------------------------
Checkout the SQL Schema Upgrade Wizard -
upgrade production DB schema, while keeping the data.
www.aloeco.com/upgrader
-----------------------------------------------------------

by **Andrew J. Kell** » Thu, 23 Aug 2001 21:13:46

Ivan,

If you have a situation that you believe is a real bug and you need imediate
help you should call MS PSS. They will charge you for the call but
re-emburse you if they determine it to in fact be a bug. If you have a
situation such as this, if you post it here one of the MVP's will usually
try and repro it. If it's reproducable (which this is) then they will submit
it to MS via a private forum. I will let them know of this since I can repro
it easily.

--
Andrew J. Kelly, SQL Server MVP
TargitInteractive

I proudly support the PASS SQL Server user community and its upcoming user
event,
PASS 2001 North America. For details, visit <http://www.sqlpass.org>
www.sqlpass.org.)

> Hi all,

> While playing with EM I received easily reproducible error situation.

> Steps:
> 1. Start creating new table.
> 2. Create a column (in the example a, type CHAR(10)).
> 3. Type description of the column.
> 4. Create other columns (in the example: column b of type CHAR(10))
> 5. Delete the column (a).
> 6. Try to save the table (Table1)

> This leads to error message similar to:

> 'Table1' table
> - Unable to create table.
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Object is
> invalid. Extended properties are not permitted on 'dbo.Table1.a', or the
> object does not exist.

> This is minor bug. But sometimes it might be annoying since one can define
a
> whole new table with many columns and fail to save his job....

> BTW, possible workaround: Save the script, copy to QA, modify, execute.

> Q1. Is this known bug? Where can we check?

> I don't want to open support case for such a minor bug...

> --
> Ivan Arjentinski

> -----------------------------------------------------------
> Checkout the SQL Schema Upgrade Wizard -
> upgrade production DB schema, while keeping the data.
> www.aloeco.com/upgrader
> -----------------------------------------------------------

by **Henrik Staun Poulse** » Sat, 25 Aug 2001 00:37:42

Andrew,

Please note that if you get the table to save, the record size might be
something very big (5000 bytes or so) even if the table has just two
fields (columns).

I managed to crash a server belonging to a new client of mine. It had
50 GB free space when I started, and it ran out 10 minutes after I left
the client. I had created about 4 almost similar tables, and only one of
them were bloated beyond recognition.
This was on MS SQL 7, 4 cpu.

Best regards

Henrik Staun Poulsen
Stovi Software
Denmark

Very Computer

Where do we report bugs? (EM bug)

Where do we report bugs? (EM bug)

Where do we report bugs? (EM bug)

Where do we report bugs? (EM bug)