February 18, 2011 at 8:10 am
Doesn't matter what the app is written in, unless it was designed to be able to handle data spread across two databases it won't be able to and it will be a substantial amount of work to change that.
Main options:
* Upgrade to SQL 2008 R2 Express. Con: Risk of breaking the app if it depends on functionality that changed between 2005 and 2008. Temporary fix, there's still a limit, if the DB keeps growing it will hit the new limit
* Clean out older data. Need to know from users what data can be deleted. Temporary fix
* Upgrade to a full version of SQL without a size limit (well, there is one but you won't reach it). Con: cost.
http://www.microsoft.com/express/Database/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 18, 2011 at 9:44 am
Thanks you were a big help. I now have A DBA that will help me Rebuild the data base the right way. Not only was the SQL server not set up right same goes for Server 2003 or Exchange 😉 and I do not know to set them up. Just have to fix the hole thing :laugh:
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply