March 31, 2003 at 10:53 am
Hi,
I'm a little new to sqlServer administration and I have a little problem. I have created a database for a asp.net web app, which works fine locally, but when I've exported it to the actual server, it does not carry with it the table relationships, or the primary keys as specified for the tables. It seems this has something to do with the database roles? I'm in a bit of a tough spot now as the client has updated data on the database, but now I may not be able to create relationships becuase of referential integrity.(?)
How do you simply "replicate" the database to the server along with all it's relationships and properties? Seems like this would be the defualt action?
Thanks for any info!
March 31, 2003 at 11:07 am
In the Import/Export Wizard, you must choose 'Copy Objects and Data between SQL Server Databases' in order to get all the data and relationships. Now your best bet is to use Query Analyzer and script those relationships so you can create them on the new server. Would that that has been added/updated have a timestamp that would help you know what has changed?
Michelle
March 31, 2003 at 11:24 am
Yes, that is what I did, and the objects and data transferred, but I didn't realize until later that the relationships/primary keys were not there. Do I need to have the "extended properties" enabled for this?
I am stuck now, as far as I can tell.... I have tried downloading the data into a "backup" database, then exporting the data into the original local copy, but I get "foriegn key constraint" errors when doing so, which, I imagine is because the local (non-backup) database has the relationships and there is possibly some erroneous data in the backup version??
I don't have a time field for most tables, if that is what you mean, however almost all data is new on the server.
I guess I'll have to rebuild it on the remote server? Gawd that is so slow....
Thanks for any other help!!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply