Hi
We have the same tables which are used in multiple databases
(replication has been thought of) anyway we decided to centralise these tables in a central database and create views to the central db and grant the application logins sufficient rights to the db. i started with one db/app which will be the master tables. i renamed all the tables been used to this eg. cost_centre_old incase we had to rollback. the views were created using the original table names so as to limit the amount of code changes. eg. (view)cost_centre.
i ran selects to the "views" and updates and everything seemed to be working then on the one asp page this came up:
An Error Occured:
(3704) Operation is not allowed when the object is closed. - CloseConnection
ok...we then renamed the tables back to the original names and changed the view names. we still get the error. if we point the application at the application's staging db everything works fine. i even brought in tables from the production db to replace some of the affected tables used in the page/object and still get no resolution.
i know that its an ado message coming up since the error message for sql 3704 differs. all the other apps on our dev server is fine. its only the db that was changed that is affected. is their a db setting or system table entry that i can change to make it work again. it works on another db instance so it shouldn't be the objects but the programmers are looking at it. what would sql server have changed when those changes happened?
we have to centralise 4 existing apps and this whole centralization has to tie into future apps so i would appreciate any ideas as to what happened or what needs to be done to fix it or prevent it.
thanks
We have the same tables which are used in multiple databases
(replication has been thought of) anyway we decided to centralise these tables in a central database and create views to the central db and grant the application logins sufficient rights to the db. i started with one db/app which will be the master tables. i renamed all the tables been used to this eg. cost_centre_old incase we had to rollback. the views were created using the original table names so as to limit the amount of code changes. eg. (view)cost_centre.
i ran selects to the "views" and updates and everything seemed to be working then on the one asp page this came up:
An Error Occured:
(3704) Operation is not allowed when the object is closed. - CloseConnection
ok...we then renamed the tables back to the original names and changed the view names. we still get the error. if we point the application at the application's staging db everything works fine. i even brought in tables from the production db to replace some of the affected tables used in the page/object and still get no resolution.
i know that its an ado message coming up since the error message for sql 3704 differs. all the other apps on our dev server is fine. its only the db that was changed that is affected. is their a db setting or system table entry that i can change to make it work again. it works on another db instance so it shouldn't be the objects but the programmers are looking at it. what would sql server have changed when those changes happened?
we have to centralise 4 existing apps and this whole centralization has to tie into future apps so i would appreciate any ideas as to what happened or what needs to be done to fix it or prevent it.
thanks
