<div>
backup everything and do the install; you can upgrade directly from 2012 express to 2019 standard<br>cleaner, though, to do a new install of sql 2019 on a new server then export/import databases - less risk compared to doing an in-place upgrade. <br><br><h2><em><u>Upgrades from Earlier Versions to SQL Server 2019 (15.x)</u></em></h2><a href="https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-version-15?view=sql-server-ver15#upgrades-from-earlier-versions-to-" rel="ugc">https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-version-15?view=sql-server-ver15#upgrades-from-earlier-versions-to-</a><br><br>SQL 2019 also requires Windows 2016 or 2019 so if your 2012 instance is on an older windows version, will need to build a new server<br><br><h2><em><u>Operating system support</u></em></h2><a href="https://docs.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-ver15?view=sql-server-ver15#operating-system-support" rel="ugc">https://docs.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-ver15?view=sql-server-ver15#operating-system-support</a>
</div>


PAMurillo

<div>
If other than disk size, Express works for you, then it might be easier -- and will definitely be less costly -- to just spread the tables out over multiple dbs, each db &lt;= 10GB, but the total size could be much more. &nbsp;You can do this using synonyms, so the existing code would not have to change at all.
</div>


<div>
Thanks guys. I am more of a network admin/tech, not a DB guy so I am looking for the easiest path to gettting them working again. &nbsp;<br><br>@Seth<br>Apparently the database will also work with SQL Std 2017. Would there be less chance of corruption with this version vs the bigger leap to ver 2019?
</div>


<div>
Follow up question. After Exporting/Importing in to the new SQL would I need to remove the origianl database from the old SQL Express. How would the software know where to look after the move?
</div>


<div>
<blockquote>Would there be less chance of corruption with this version vs the bigger leap to ver 2019?</blockquote><br>wouldn't make a difference; any in-place upgrade comes with risk regardless if it is 2017 or 2019<br><br><blockquote>Exporting/Importing in to the new SQL would I need to remove the origianl database from the old SQL Express. &nbsp;</blockquote><br>no need to do that; would suggest stopping the sql services or shutting down the server to make sure no systems are still talking to it<br><br><blockquote>How would the software know where to look after the move?</blockquote><br>you would need to update odbc connection to point to the new server and instance<br>another option would be to backup up all of your databases then remove the server from the domain and turn off<br>your new server could have the same name as the old one then after you restore, your clients should just connect though I have not tested that<br><br>
</div>


<div>
Thanks Guys! In the meantime, someone at the office locked up the database by trying their own solutions. So it went from mostly working to not working for anyone. I had to do a restore and get them operational.<br><br>I am attampting to upgrade to MSSQL2017 and will let you know what happens
</div>


<div>
@Seth<br>So when you mean Import and Export you mean using the SQL Server Import and Export Wizard, correct?<br><br>I muddled my way throught the process and was at the final part when I got this error message.&nbsp;<img src="https://filedb.experts-exchange.com/incoming/2021/09_w37/1572053/Import-Wizard-Error.PNG" class="fr-fic fr-dib">Any advise?
</div>


Import-Wizard-Error.PNG

<div>
<div class="content wysiwyg-content fr-view">
<div><div class="content wysiwyg-content fr-view"><div><div class="content wysiwyg-content fr-view"><p>I have a client with eMDs Solution software running on a server and the database has maxed out at 10GB. Support say we need to upgrade to MS SQL 2019 Std or 2017 Std but do not offer support or instruction to upgrade. I am looking for a path to complete this process. &nbsp;My client is currently not able to use the management software.</p><p><br></p><p>Any help would be appreciated!</p></div></div></div></div>
</div>
</div>



I have a client with eMDs Solution software running on a server and the database has maxed out at 10GB. Support say we need to upgrade to MS SQL 2019 Std or 2017 Std but do not offer support or instruction to upgrade. I am looking for a path to complete this process.  My client is currently not able to use the management software.
Any help would be appreciated!

What is the process to upgrade a database from MS SQL 2012 Express to MS SQL 2019 Standard ed for eMDs?

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.

Databases

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.