Defaults Values Missing After DB Move

[cbuechler]

Hi,



I have several SQL databases on two SQL servers (2000 and 2005) and when I move them to a new SQL 2005 server via detach and attach all of the "Default Values or Bindings" I have set on fields dissapear.

I noticed this first when I opened one and added a new record and my date created field that should fill with getdate() didn't populate. Checking the table design I can see that getdate() is missing from the default value. I checked other fields and they were missing from there as well and one of the db's wasn't my design so I don't look forward to replacing them all by hand.

Any ideas on what I need to do to move these without losing those settings? Even reattaching the db's back to the same server doesn't help as the default settings are gone now from there as well. I had to revert to a backup to get things functioning again on the old servers.

Thanks!

[NoellaG]

Hi,

SQL server does handle defaults in a different way since version 2005: default definitions. And although the old default object is still supported for now, MS states in its help function this feature will be removed in later versions. So this could be the cause of loosing the default objects when moving the database to a new format.
However you can replace them by creating default definitions.

success
NG

btw: as this is an Access forum, you will get more answers to questions about SQl server if you put them on the proper SQL server forums.

[cbuechler]

Thanks for the reply.

I went ahead and restored a copy of the database from backup to the new server rather than follow up with another Detach/Attach attempt and the restore carried over the defaults while the D/A actions didn't; so all is well.