Content db pointed to wrong instance of SQL
When we set up our MOSS apparently, even though we also installed full SQL 2005, the content db and config db got pointed to SQL Express. Now we are at the 4GB limit. We need to move the content db to SQL 2005 instance. Tried just changing the default database, but we just get "unknown error." Tried creating a new content db, moved a site collection into it, and detached and attached to SQL 2005. When we try to go to that site we get "an unexpected error has occurred." (Could they make these error messages any less descriptive?). Would like to either move the existing content db (WSS_Content) to SQL 2005 or move site collections to their own databases, also on 2005. Thanks for any assistance.
June 18th, 2010 8:19pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics