 | |
varchar(10) --> varchar(50) AAAGGGHHHH!!!
microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: varchar(10) --> varchar(50) AAAGGGHHHH!!! -
05-23-2008
, 05:11 PM
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#12
| |||
| |||
|
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#13
| |||
| |||
|
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#14
| |||
| |||
|
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#15
| |||
| |||
|
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#16
| |||
| |||
|
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#17
| |||
| |||
|
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#18
| |||
| |||
|
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#19
| |||
| |||
|
|
"Jeff Johnson" <i.get (AT) enough (DOT) spam> wrote in message news:Ub-dnVgl3If9jarVnZ2dnUVZ_oninZ2d (AT) posted (DOT) datapex... Does anyone know if there are any outstanding requests on the Connect site asking that the table designer in SSMS please stop automatically changing varchar(10) into varchar(50) the first time you enter it? Am I the only one this drives up a wall? Argh, search first, then post. http://connect.microsoft.com/SQLServ...dbackID=127135 Didn't SP2 come out after this? You'd think something like this would have been easy to fix. |
a harmless one. There are a lot more serious bugs in the table designer
with regards to creating change scripts, that I strongly recommend
that you do not use the designer at all.
This particular bug appears to be fixed in SQL 2008. The really serious
bugs aren't. But at least now the dangerous parts are disabled by
default.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.