Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ProEdge
Yak Posting Veteran
64 Posts |
 Posted - 2007-08-13 : 17:03:33
|
| Hi everyone, I've done a little research regarding this but haven't found much. Essentially, I just created a new database in 2005 and forward engineered my tables from Erwin. Now, according to my database options, I set the features for ANSI_NULL DEFAULTS, ANSI_NULL ENABLED to false. As a matter of fact, everything that falls under Miscellaneous was false. Now, whenever I go into one of my tables and change something in the schema, let's say a data type, I get the following message from Mgmt Studio:- Warning: One or more existing columns have ANSI_PADDING 'off' and will be re-created with ANSI_PADDING 'on'.- Warning: The table was created with ANSI_NULLS 'off' and will be re-created with ANSI_NULLS 'on'.I'm a little confused because my default options are set to 'off' for both these options yet it wants to re-save the table with them on. Does anyone know why this happens? |
|
|
ProEdge
Yak Posting Veteran
64 Posts |
Posted - 2007-08-16 : 18:13:06
|
| Don't know what the rules are here for bumping but here it goes...*BUMP* |
 |
|
|
|
|
|
ANSI_NULL Options