How can we help you today? How can we help you today?
jheidt
Activity overview Badges (0) Posts (3) Comments (5)

Comments

Sort by recent activity
This is great! I have told the guys here and we will be renewing our license today. Thank you so very much Red Gate, you guys rock! / comments
  1. Community
  2. SQL Compare Previous Versions
  3. SQL Compare - changing nullability
This is great! I have told the guys here and we will be renewing our license today. Thank you so very much Red Gate, you guys rock!
0 votes
Andras wrote: Well, this is a rather interesting problem. You set up a default value, and no longer allow nulls. But the table itself contains nulls [image] IMHO null data in such tables should be updated first to the new desired value, which may or may not be the new default value. It is difficult to decide automatically whether the nullability has been changed by mistake, or what the new value for the nullable column should be. While I would say that doing the data change automatically would corrupt the database, not everyone is as paranoid as I am, and I can see your point that such behaviour could be useful in certain cases. Therefore I've added this feature to SQL Compare. We will use the DRI default with ISNULL if a colum is changed from nullable to not nullable and a DRI default is already set up on the non nullable side, but not on the column that allows nulls. Also, in the first iteration we will not allow automatic reverting to the default value if the datatype has changed in any way. Assuming this feature will not bring unforseen problems in our tests it will be available in the next major release of SQL Compare (SQL Compare 7, scheduled for release in Q3). There will be a high priority warning accompanying such automatic data mangling. Regards, Andras Indeed, it could cause unintended values to be inserted to the column, a perfect example would be DateUpdated or DateCreated columns with default values, would then get bad data. I am aware of that situation, but the problem is that we can't use SQL Compare to automate our schema deployments even though thats exactly why we purchased it, and it's a bit frustrating - various versions of our schema exist on our customers side and the nullability thing is really a show stopper. It's unfortunate, but I guess I'll have to wait for v7. Is there an extensibility model I can plug into and write some code for? This is going to really backburner our planned roll-out, and SQL Compare is pretty much the only game in town, and I dont want to hand-roll the code to avoid this situation. Any suggestions? / comments
  1. Community
  2. SQL Compare Previous Versions
  3. SQL Compare - changing nullability
Andras wrote: Well, this is a rather interesting problem. You set up a default value, and no longer allow nulls. But the table itself contains nulls IMHO null data in such tables should be upda...
0 votes
Does anyone have any feedback for me about this? My support contract and licenses for my red gate products are about to expire, and I'm considering my options for what to renew, as it stands here, if I have to manually edit these files or create a tool to do such I don't think SQL compare will work for what my office needs. Maybe I just overlooked something? / comments
  1. Community
  2. SQL Compare Previous Versions
  3. SQL Compare - changing nullability
Does anyone have any feedback for me about this? My support contract and licenses for my red gate products are about to expire, and I'm considering my options for what to renew, as it stands here, ...
0 votes
David, the new column does have a default value. The old column did not, and allowed nulls. The insert statement SQL Compare generates when filling the temp table it creates (which has the default value specified) fails because the insert statement doesnt specify what to do if the value is null - this is per the ANSI SQL spec. What SQL Compare should do is use IsNull([ChangedColumn],<default value>) in its select statement, or give the user the option to do that. see here for more of what im talking about: http://www.developersdex.com/sql/messag ... &r=6164216 / comments
  1. Community
  2. SQL Compare Previous Versions
  3. SQL Compare - changing nullability
David, the new column does have a default value. The old column did not, and allowed nulls. The insert statement SQL Compare generates when filling the temp table it creates (which has the default ...
0 votes
Couldn't you just put the value you wanted as the default value for the column, run the synch, remove the default value, and then resynch? / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Setting a Default for a New Column
Couldn't you just put the value you wanted as the default value for the column, run the synch, remove the default value, and then resynch?
0 votes
Total activity
10
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
2