Alcatel Unleashed

Hello,
We have recently installed and configured OXR 2.3.1 in environment but after some days I saw sql issue because one table (ServerStatus) of OPCXR_Config database had a size over 15 GB.

DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database

I can't undertand why but now I setuped Windows task for Truncate table but it's not normal. In additional I should use SQL profiler to get sql logs.

More about environment:
Windows server version - Windows server 2012 R2 Standard
SQL server version - Microsoft SQL Server 2014 Express Edition (64-bit)

Can anyone the same issue and what is the right way to fix it.
Thanks.

Express edition is not supported at all. That limit is bound to that version. You should go with Standard edition always

Enviado de meu E6633 usando Tapatalk

I looked again system documentations (OmniPCX Record version 2.3 Intallation manual) and there is support for the following sql:
- SQL server version - Microsoft SQL Server 2012 Express Edition
- SQL server version - Microsoft SQL Server 2014 Express Edition
- SQL server version - Microsoft SQL Server 2016 Express Edition

and in additional Hardware & Software Specification (Recomendation) in attached file.

link wrote:I looked again system documentations (OmniPCX Record version 2.3 Intallation manual) and there is support for the following sql:
- SQL server version - Microsoft SQL Server 2012 Express Edition
- SQL server version - Microsoft SQL Server 2014 Express Edition
- SQL server version - Microsoft SQL Server 2016 Express Edition

and in additional Hardware & Software Specification (Recomendation) in attached file.

Well...yes and no.
When you do the dimensioning of the software, units, you also have to do your job to dimension database size. If the DB size is higher than 1Gb and you don't do purge tasks to maintain it low (meaning to delete records and keep them available for a short time) Then you SQL express is not the solution.
You are facing a basic issue, the limit of a free product, so, if you do your homework on planning then you avoid this situation. By quoting documentation but without any context means nothing.
OXR supports it? Meaning you can do basic installation with it? Yes. Does it work for a production environment? Usually no.
It clearly states, without options and average delete tasks...now...what they don't mention is what is "average" ... Right? There comes the job of an expert. Who says, don't use that for production environment.
If you wanna find a solution for a well documented limitation of a free product by showing "it is supported" then good luck.
You have 2 options :
Delete all info until you reach a reasonable size of sql express
Upgrade to sql standard and live without problems

Also, read about all sql express limits, is not only size


Enviado de meu E6633 usando Tapatalk

I understand well about limits Express version. But I can't undestand why system work well before 2.3.1 version.

To fully understand you, what do you mean by that? That a recent upgrade made this increase of size?
Have you increased licenses? Users? Operation hours?


Enviado de meu E6633 usando Tapatalk

I have only made upgrade process from 2.2 to 2.3. Before several years we were used OXR 2.2 without any problems with SQL but after upgrade I should change SQL version edition to standard . It's not normal and raises doubts.
In additional a few weeks ago I installed OXR version 2.3 to new customer and have the same issue.

And on your sql server, what exactly is consuming that size?
The transaction log is configured how? Simple or Full?


Enviado de meu E6633 usando Tapatalk

And on your sql server, what exactly is consuming that size?
ServerStatus table
The transaction log is configured how? Simple or Full?
Simple

If you did install a new 2.3 several weeks ago, they should have SPS for it, I suppose.
Have you tried to contact ALE TS and create an eSR about that problem?