SSMS : Edit Top N Rows expects 'true'/'false' in BIT columns - by AaronBertrand

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


17
1
Sign in
to vote
ID 264592 Comments
Status Closed Workarounds
Type Suggestion Repros 1
Opened 3/21/2007 2:42:05 PM
Access Restriction Public

Description

Yes, I am going to get a lot of boos and hissing from the "SQL Server is a spreadsheet" crowd (the title of this suggestion was originally "Deprecate Open Table").

The Open Table feature just has so many problems, and because Visual Studio and add-ins like Telerik make it so easy to whip together a comparable app in minutes, I think this holdover should be abandoned.  In a casual review of bugs reported since Jan 1st 2007, I literally lost count of how many revolved around some obscure scenario in Open Table.

This one has been around since the early previews of Yukon:

CREATE TABLE dbo.Test(yn BIT);

Now, open the table and enter a 1 into the first row.  You get this lovely error:

---------------------------
Microsoft SQL Server Management Studio
---------------------------
Invalid value for cell (row 1, column 1).

The changed value in this cell was not recognized as valid.
.Net Framework Data Type: Boolean
Error Message: String was not recognized as a valid Boolean.

Type a value appropriate for the data type or press ESC to cancel the change.
---------------------------
OK   Help   
---------------------------

Why on earth is BOOLEAN here?  Why should I be typing TRUE into a BIT column?

(BTW, this was closed as "Thanks for your feature request. This was viewed as the best desired behavior." in Connect #124584.)

I strongly suggest that maybe it is time to let go of this severely crippled and limited tool.  
Sign in to post a comment.
Posted by Microsoft on 8/5/2011 at 5:20 AM
Hi,

Thanks for reporting this issue, this has been fixed in an internal build and will be available in next release of SQL Server "Denali". We have fixed the open table window to accept 0 / 1 instead of throwing error for coumns of type bit.

Thanks,
Sravanthi Andhavarapu,
SQL Server Manageability Team
Posted by Jermyh on 10/11/2007 at 3:18 AM
When you want to open table, you just need use the same Grid of Query Results, with SELECT * FFOM <table_name>, then you can change the query, and you should be able to change the data in the table by chooseing to make it updateable. So, smooth, so elegant and as most of the users most of the time just want to see the data of a single table, or just want to see the columns names/order/meaning with some data, so you can give by default TOP X rows in the query.
I would also add this feature from right click on a Table name in the Query Text Pane, as well as count(*), sp_help, sp_helptext for procedure, etc.
Posted by Microsoft on 4/19/2007 at 3:03 AM
Thanks for reporting this issue. We will update this space accrodingly based on investigation of your comments. We are aware of the issue reported by you. Thanks again for your feedback , cause that reiterates the vulnerability in terms of usability that the table designer posses.

Regards
Vinod