https://theoracle.magentaretail.com.au/api.php?action=feedcontributions&feedformat=atom&user=NivinEnablerWiki - User contributions [en]2026-10-22T01:10:45ZUser contributionsMediaWiki 1.46.2https://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1647EEE Software Requirements2026-03-31T22:40:18Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .NET Framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| .NET<br/>Framework<br/>version<br />
!| .NET<br/>version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.98.x<br />
|| 2026 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''10.0'''</span><br />
|| 2016<br />
|| 2016<br />
|| 2016<br />
|| <br />
|-<br />
|| 1.96.x<br />
|| 2025 Q1<br />
|| 4.8<br />
|| 8.0<br />
|| <span style="color: blue;>'''2016'''</span><br />
|| <span style="color: blue;>'''2016'''</span><br />
|| <span style="color: blue;>'''2016'''</span><br />
|| Several SQL Server and Windows Server versions that have reached end of life are no longer supported<br />
|-<br />
|| 1.94.09<br />
|| 2025 Q1<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.04<br />
|| 2024 Q3<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0, 6.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.01<br />
|| 2024 Q1<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''6.0'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''Core 3.1'''</span><br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''Core 3.1, Core 2.1'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| <span style="color: blue;>'''Core 2.2, Core 2.1'''</span><br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1646EEE Software Requirements2026-03-31T22:36:06Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .NET Framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| .NET<br/>Framework<br/>version<br />
!| .NET<br/>version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|| 1.98.x<br />
|| 2026 Q2<br />
|| 4.8<br />
|| 10.0<br />
|| 2016<br />
|| 2016<br />
|| 2016<br />
|| <br />
|-<br />
|| 1.96.x<br />
|| 2025 Q1<br />
|| 4.8<br />
|| 8.0<br />
|| <span style="color: blue;>'''2016'''</span><br />
|| <span style="color: blue;>'''2016'''</span><br />
|| <span style="color: blue;>'''2016'''</span><br />
|| Several SQL Server and Windows Server versions that have reached end of life are no longer supported<br />
|-<br />
|| 1.94.09<br />
|| 2025 Q1<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.04<br />
|| 2024 Q3<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0, 6.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.01<br />
|| 2024 Q1<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''6.0'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''Core 3.1'''</span><br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''Core 3.1, Core 2.1'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| <span style="color: blue;>'''Core 2.2, Core 2.1'''</span><br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1645EEE Software Requirements2025-03-25T05:42:33Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .NET Framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| .NET<br/>Framework<br/>version<br />
!| .NET<br/>version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.96.x<br />
|| 2025 Q1<br />
|| 4.8<br />
|| 8.0<br />
|| <span style="color: blue;>'''2016'''</span><br />
|| <span style="color: blue;>'''2016'''</span><br />
|| <span style="color: blue;>'''2016'''</span><br />
|| Several SQL Server and Windows Server versions that have reached end of life are no longer supported<br />
|-<br />
|| 1.94.09<br />
|| 2025 Q1<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.04<br />
|| 2024 Q3<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0, 6.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.01<br />
|| 2024 Q1<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''6.0'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''Core 3.1'''</span><br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''Core 3.1, Core 2.1'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| <span style="color: blue;>'''Core 2.2, Core 2.1'''</span><br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1644EEE Software Requirements2025-02-27T04:34:06Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .NET Framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| .NET<br/>Framework<br/>version<br />
!| .NET<br/>version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.96.x<br />
|| 2025 Q1 (planned)<br />
|| 4.8<br />
|| 8.0<br />
|| <span style="color: blue;>'''2016'''</span><br />
|| <span style="color: blue;>'''2016'''</span><br />
|| <span style="color: blue;>'''2016'''</span><br />
|| Several SQL Server and Windows Server versions that have reached end of life are no longer supported<br />
|-<br />
|| 1.94.09<br />
|| 2025 Q1<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.04<br />
|| 2024 Q3<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0, 6.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.01<br />
|| 2024 Q1<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''6.0'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''Core 3.1'''</span><br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''Core 3.1, Core 2.1'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| <span style="color: blue;>'''Core 2.2, Core 2.1'''</span><br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1643EEE Software Requirements2025-02-27T02:01:18Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .NET Framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| .NET<br/>Framework<br/>version<br />
!| .NET<br/>version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.96.x<br />
|| 2025 Q1 (est)<br />
|| 4.8<br />
|| 8.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.09<br />
|| 2025 Q1<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.04<br />
|| 2024 Q3<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0, 6.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.01<br />
|| 2024 Q1<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''6.0'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''Core 3.1'''</span><br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''Core 3.1, Core 2.1'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| <span style="color: blue;>'''Core 2.2, Core 2.1'''</span><br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1642EEE Software Requirements2025-02-27T01:49:31Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .NET Framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| .NET<br/>Framework<br/>version<br />
!| .NET<br/>version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.94.09<br />
|| 2025 Q1<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.04<br />
|| 2024 Q3<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0, 6.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.01<br />
|| 2024 Q1<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''6.0'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''Core 3.1'''</span><br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''Core 3.1, Core 2.1'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| <span style="color: blue;>'''Core 2.2, Core 2.1'''</span><br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| -<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1641EEE Software Requirements2025-02-27T01:36:12Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| .NET<br/>Framework<br/>version<br />
!| .NET<br/>version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.94.09<br />
|| 2025 Q1<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.04<br />
|| 2024 Q3<br />
|| 4.8<br />
|| <span style="color: blue;>'''8.0, 6.0'''</span><br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.94.01<br />
|| 2024 Q1<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 6.0<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| <br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| <br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| <br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| <br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=Browsers_supported_by_EEE&diff=1640Browsers supported by EEE2024-10-31T05:04:48Z<p>Nivin: </p>
<hr />
<div>Created: 05 July 2012. Last Reviewed: 31 October 2024<br />
<br />
We recommend using modern, supported browsers with latest versions of EEE.<br />
<br />
EEE is regularly tested with latest versions of Chromium-based browsers (e.g. Google Chrome, Microsoft Edge). Although no longer in active support, we try to keep EEE compatible with Internet Explorer 11. Latest versions of EEE will not work with older versions of Internet Explorer.<br />
<br />
For Integrated Logins, we recommend using the Edge WebView2 control where possible. Alternatively, using the legacy WebBrowser control with recent versions of Enabler or EEPOS will automatically emulate Internet Explorer 11 in integrated logins, provided IE11 is installed and available on the machine.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=Browsers_supported_by_EEE&diff=1639Browsers supported by EEE2024-10-31T05:03:40Z<p>Nivin: </p>
<hr />
<div>Created: 05 July 2012. Last Reviewed: 31 October 2024<br />
<br />
We recommend using modern, supported browsers with latest versions of EEE.<br />
<br />
EEE is regularly tested with latest versions of Chromium-based browsers (e.g. Google Chrome, Microsoft Edge). Although no longer in active support, as of EEE 1.94 we try to keep EEE compatible with Internet Explorer 11. Latest versions of EEE will not work with older versions of Internet Explorer.<br />
<br />
For Integrated Logins, we recommend using the Edge WebView2 control where possible. Alternatively, using the legacy WebBrowser control with recent versions of Enabler or EEPOS will automatically emulate Internet Explorer 11 in integrated logins.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1638EEE Software Requirements2024-04-09T04:31:57Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| Minimum<br/>.Net version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.94.x<br />
|| 2024 Q1<br />
|| 4.8<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1635EEE Software Requirements2024-01-16T05:00:25Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| Minimum<br/>.Net version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.92.x<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1634EEE SQL Query Executor2023-12-20T23:18:47Z<p>Nivin: </p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from executing queries against other databases. e.g. creating a database user john_doe in the EEE database mapped to the SQL login of the same name:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe;<br />
</nowiki><br />
<br />
=== Querying tables ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants *read-only* permissions to all non-system tables and views, which can be used for this purpose. e.g. Adding the EEE database user john_doe as a member of the role:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
=====Use only if required=====<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it direct to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
The built-in db_datawriter role can be used to allow insert/update/delete of data from all non-system tables in the database - '''if required'''. Use with extreme caution!<br />
<br />
=== Executing Stored procedures ===<br />
<br />
=====Use only if required=====<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
=====Use only if required=====<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1633EEE SQL Query Executor2023-12-20T23:18:26Z<p>Nivin: /* Querying tables */</p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from executing queries against other databases. e.g. creating a database user john_doe in the EEE database mapped to the SQL login of the same name:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe;<br />
</nowiki><br />
<br />
=== Querying tables ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants *read-only* permissions to all non-system tables and views, which can be used for this purpose. e.g. Adding the EEE database user john_doe as a member of the role:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
=====Use only if required=====<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it direct to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
The built-in db_datawriter role can be used to allow insert/update/delete of data from all non-system tables in the database - '''if required'''. Use with extreme caution!<br />
<br />
=== Executing Stored procedures ===<br />
<br />
'''Use only if required'''<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
'''Use only if required'''<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1632EEE SQL Query Executor2023-12-20T23:16:46Z<p>Nivin: </p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from executing queries against other databases. e.g. creating a database user john_doe in the EEE database mapped to the SQL login of the same name:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe;<br />
</nowiki><br />
<br />
=== Querying tables ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants *read-only* permissions to all non-system tables and views, which can be used for this purpose. e.g. Adding the EEE database user john_doe as a member of the role:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Use only if required'''<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it direct to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
The built-in db_datawriter role can be used to allow insert/update/delete of data from all non-system tables in the database - '''if required'''. Use with extreme caution!<br />
<br />
=== Executing Stored procedures ===<br />
<br />
'''Use only if required'''<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
'''Use only if required'''<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1631EEE SQL Query Executor2023-12-20T23:15:24Z<p>Nivin: /* Querying tables */</p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from executing queries against other databases. e.g. creating a database user john_doe in the EEE database mapped to the SQL login of the same name:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe;<br />
</nowiki><br />
<br />
=== Querying tables ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants *read-only* permissions to all non-system tables and views, which can be used for this purpose. e.g. Adding the EEE database user john_doe as a member of the role:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Use only if required'''<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it direct to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
The built-in db_datawriter role can be used to allow insert/update/delete of data from all non-system tables in the database - '''if required'''. Use with extreme caution!<br />
<br />
=== Executing Stored procedures ===<br />
<br />
'''Use only if required'''<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1630EEE SQL Query Executor2023-12-20T23:14:39Z<p>Nivin: /* Database role membership */</p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from executing queries against other databases. e.g. creating a database user john_doe in the EEE database mapped to the SQL login of the same name:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe;<br />
</nowiki><br />
<br />
=== Querying tables ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants *read-only* permissions to all non-system tables and views, which can be used for this purpose. e.g. Adding the EEE database user john_doe as a member of the role:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Use only if required'''<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it direct to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
The built-in db_datawriter role can be used to allow insert/update/delete of data from all non-system tables in the database - *if required*. Use with extreme caution!<br />
<br />
=== Executing Stored procedures ===<br />
<br />
'''Use only if required'''<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1629EEE SQL Query Executor2023-12-20T23:11:32Z<p>Nivin: /* User Mapping */</p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from executing queries against other databases. e.g. creating a database user john_doe in the EEE database mapped to the SQL login of the same name:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe;<br />
</nowiki><br />
<br />
=== Database role membership ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants read-only permissions to all non-system tables and views, which can be used for this purpose. e.g. Adding the EEE database user john_doe as a member of the role:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Use only if required'''<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it direct to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
=== Executing Stored procedures ===<br />
<br />
'''Use only if required'''<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1628EEE SQL Query Executor2023-12-20T23:11:18Z<p>Nivin: /* Database role membership */</p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from executing queries against other databases. e.g. creating a database user john_doe in the EEE database mapped to the SQL login of the same name:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe;<br />
</nowiki><br />
<br />
<br />
=== Database role membership ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants read-only permissions to all non-system tables and views, which can be used for this purpose. e.g. Adding the EEE database user john_doe as a member of the role:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Use only if required'''<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it direct to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
=== Executing Stored procedures ===<br />
<br />
'''Use only if required'''<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1627EEE SQL Query Executor2023-12-20T23:10:45Z<p>Nivin: </p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from executing queries against other databases. e.g. creating a database user john_doe in the EEE database mapped to the SQL login of the same name:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe;<br />
</nowiki><br />
<br />
<br />
=== Database role membership ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants read-only permissions to all non-system tables and views, which can be used for this purpose. e.g. Adding the EEE database user john_doe as a member of the role:<br />
<br />
<nowiki>USE EEE<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder ADD MEMBER john_doe;<br />
GO<br />
</nowiki><br />
<br />
'''Use only if required'''<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it direct to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
=== Executing Stored procedures ===<br />
<br />
'''Use only if required'''<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_SQL_Query_Executor&diff=1626EEE SQL Query Executor2023-12-20T23:06:36Z<p>Nivin: </p>
<hr />
<div>As of EEE version 1.84.09 a new SQL Query Executor function is available within EEE.<br />
<br />
This screen allows users to run ad-hoc T-SQL queries against the EEE database using an appropriate SQL authentication credential.<br />
<br />
Although EEE issue warnings if the query text contains specific keywords, EEE does not analyse the syntax of the query nor attempt to prevent execution of destructible queries.<br />
<br />
As such, the following security considerations are recommended:<br />
<br />
* Disable the screen for all but specific users who have knowledge of creating and running T-SQL queries. This can be done via user privileges.<br />
* Set up the SQL authentication login with the minimum permissions required (see below).<br />
* Use a complex password for the SQL login in order to improve security.<br />
* Create separate SQL logins for different EEE databases to further compartmentalise access.<br />
<br />
A new user privilege, "Allow executing ad-hoc queries against this EEE database" is also required for the user to be able to access the screen in EEE.<br />
<br />
== SQL Login Permissions ==<br />
<br />
How to restrict access to the SQL login via permissions<br />
<br />
=== Deny visibility of other databases ===<br />
<br />
Initially run the following to hide other database names to logins using the public server role.<br />
<br />
<nowiki>USE MASTER<br />
GO<br />
DENY VIEW ANY DATABASE TO PUBLIC<br />
GO</nowiki><br />
<br />
<br />
=== Server roles ===<br />
<br />
'''Never''' grant the sysadmin server role to an SQL login intended for use with the SQL Query Executor page. This would yield unrestricted access on the SQL server to the login.<br />
<br />
Only the default (public) server role is recommended.<br />
<br />
=== User Mapping ===<br />
<br />
The SQL login must only be mapped to a user on the required EEE database(s). This will restrict the user from accessing other databases.<br />
<br />
=== Database role membership ===<br />
<br />
We recommend only granting the minimum permissions required for the user. EEE databases now have an EEESQLQueryBuilder role that automatically grants read-only permissions to all non-system tables and views, which can be used for this purpose.<br />
<br />
'''Use only if required'''<br />
<br />
If write permissions to specific tables are required, you'll need to manually choose to grant X permission (insert, update, delete) to Y table. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
grant insert on dbo.Product to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': If the role has multiple members, granting permission to the role will grant permission to all its members. To only grant it to specific users, grant it to the user rather than the role. i.e.<br />
<br />
<nowiki><br />
grant insert on dbo.Product to john_doe;<br />
GO</nowiki><br />
<br />
=== Executing Stored procedures ===<br />
<br />
'''Use only if required'''<br />
<br />
In order to only allow executions of specific stored procedures, you'll need to manually grant the execute permission. e.g.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
GRANT EXECUTE on usp_Article_Get to EEESQLQueryBuilder;<br />
GO</nowiki><br />
<br />
'''Warning''': Execute permissions are lost if the stored procedure is deleted and re-created.<br />
<br />
For permissions to execute '''all''' stored procedures, create a new role for the dbo schema and grant execute permissions there.<br />
<br />
<nowiki>USE EEE<br />
GO<br />
CREATE ROLE EEESQLQueryBuilder_dbo<br />
GO<br />
GRANT EXECUTE ON SCHEMA::dbo to EEESQLQueryBuilder_dbo<br />
GO<br />
ALTER ROLE EEESQLQueryBuilder_dbo ADD MEMBER john_doe;<br />
</nowiki><br />
<br />
'''Warning''': Use this permission with extreme caution. Incorrect usage of EEE stored procedures can have unintended consequences and may cause irreparable damage or loss of data<br />
<br />
=== Database Mail ===<br />
<br />
To allow the SQL login to send emails via SQL Server Database Mail, create and map the login to a user on the msdb database, and grant the DatabaseMailUserRole role.<br />
<br />
<nowiki>USE msdb<br />
GO<br />
CREATE USER john_doe FOR LOGIN john_doe<br />
GO<br />
ALTER ROLE DatabaseMailUserRole ADD MEMBER john_doe<br />
GO<br />
</nowiki></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1625EEE Software Requirements2023-07-14T07:09:20Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| Minimum<br/>.Net version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.92.x (planned)<br />
|| 2023 Q3<br />
|| 4.8<br />
|| 2012<br />
|| 2012<br />
|| 2012<br />
|| <br />
|-<br />
|| 1.90.x<br />
|| 2023 Q2<br />
|| 4.8<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1624EEE Software Requirements2021-08-17T22:37:44Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| Minimum<br/>.Net version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.90.x (planned)<br />
|| 2022 H1<br />
|| 4.8<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached [https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2008-r2 end of life] and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1623EEE Software Requirements2021-08-17T22:34:18Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| Minimum<br/>.Net version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.90.x (planned)<br />
|| 2022 H1<br />
|| 4.8<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached end of life and is no longer supported<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1622EEE Software Requirements2021-08-17T22:32:53Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| Minimum<br/>.Net version<br />
!| Minimum<br/>Windows Server<br/>version<br/><br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.90.x (planned)<br />
|| 2022 H1<br />
|| 4.8<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| 2012<br />
|| 2012<br />
|| Windows Server 2008 R2 SP1 has reached end of life and is no longer supported by Microsoft<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1621EEE Software Requirements2021-05-17T22:33:55Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| Minimum<br/>.Net version<br />
!| Minimum<br/>Windows Server<br/>version<br/>(limited by .Net<br/>support)<br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.88.x<br />
|| 2021 Q2<br />
|| 4.8<br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&diff=1620EEE WebService2021-04-11T22:13:59Z<p>Nivin: /* EEE WebService */</p>
<hr />
<div>Created: 05 July 2012. Last Reviewed: 24 January 2018<br />
<br />
===EEE WebService===<br />
<br />
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.<br />
<br />
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au<br />
<br />
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities->Configuration->Configuration Settings->Licensed Plugins tab.<br />
<br />
Magenta Retail provide EEE Web Service documentation which can be viewed from here:<br />
<br />
[https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEEWebService.htm EEE Web Service Documentation]<br />
<br />
or downloaded as a PDF from here:-<br />
<br />
[https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]<br />
<br />
Recommendations / Processes<br />
<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/GiftCardsOrderFulfilledAtWebsiteScenarios.pdf Gift Cards Scenarios - Order Fulfilled at Website]<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/GiftCardsOrderFulfilledInEEEScenarios.pdf EEE Gift Cards Scenarios - Order Fulfilled at EEE]<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/GiftCardsSalesNotSentScenarios.pdf EEE Gift Cards Scenarios - Sales Not Sent to EEE]<br />
* [https://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]<br />
* [https://theoracle.magentaretail.com.au/images/c/cf/EEE_Customer_Communications_-_Email_Verification_Process.pdf EEE Email Verification Process]<br />
* [https://theoracle.magentaretail.com.au/images/b/b5/EEE_Customer_Communications.pdf EEE Customer Communications]<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/E-Commerce_Integration_Scenarios.pdf E-Commerce Integration Scenarios]<br />
<br />
<br />
Example XML and XSD files and PHP code can be downloaded using the links below<br />
<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip XSD files]<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip XML Sample files]<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/CSharpSample.zip C# sample code]<br />
* [https://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/PhpSample.zip PHP sample code]<br />
<br />
== See Also: ==</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Software_Requirements&diff=1617EEE Software Requirements2021-03-04T00:16:26Z<p>Nivin: </p>
<hr />
<div>EEE leverages the Microsoft .Net framework, SQL Server and SQL Server Reporting Services software components and as such, specific versions of EEE have explicit dependencies on a certain versions these components.<br />
<br />
While there is no explicit block or requirement on operating system enforced by EEE, this may be limited by the version of the software components (e.g. .Net framework) available for your Operating System. We recommend running current, regularly updated and supported operating systems.<br />
<br />
See [https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies here] for more information about the .Net framework requirements.<br />
<br />
Please refer to the table below for minimum requirements for EEE.<br />
<br />
{|class="wikitable"<br />
|-<br />
!| EEE Version<br />
!| Release Year<br />
!| Minimum<br/>.Net version<br />
!| Minimum<br/>Windows Server<br/>version<br/>(limited by .Net<br/>support)<br />
!| Minimum<br/>SQL Server<br/><br />
!| Minimum<br/>SQL Server<br/>Reporting<br/>Services<br/>version<br />
!|Comments<br />
|-<br />
|| 1.88.x<br />
|| 2021 H1 (Planned)<br />
|| 4.8<br />
|| 2008 R2 SP1<br />
|| <span style="color: blue;>'''2012'''</span><br />
|| <span style="color: blue;>'''2012'''</span><br />
|| EEE SQLCLR Integration now uses .Net 4.8 which is only supported on SQL Server 2012 and later<br />
|-<br />
|| 1.86.x<br />
|| 2020 Q2<br />
|| <span style="color: blue;>'''4.8'''</span><br />
|| <span style="color: blue;>'''2008 R2 SP1'''</span><br />
|| 2008<br />
|| 2008<br />
|| .Net 4.8 is not supported on Windows Server 2008 / Windows Vista<br />
|-<br />
|| 1.84.x<br />
|| 2019 Q1<br />
|| 4.5.2<br />
|| 2008 SP2<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| 2008<br />
|| SQL Server 2005 is no longer supported by EEE<br />
|-<br />
|| 1.82.x<br />
|| 2018 Q3<br />
|| <span style="color: blue;>'''4.5.2'''</span><br />
|| 2008 SP2<br />
|| 2005<br />
|| <span style="color: blue;>'''2008'''</span><br />
|| New Microsoft Report Viewer control (2016) used by EEE requires reports to be hosted on Reporting Services 2008 or later<br />
|-<br />
|| 1.80.x<br />
|| 2017 Q2<br />
|| 4.5<br />
|| 2008 SP2<br />
|| 2005<br />
|| 2005<br />
||<br />
|}</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1616EEE Excel Templates: Use Updated OLEDB Driver2020-09-17T01:31:34Z<p>Nivin: /* Updated OLEDB Driver */</p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disabled. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2.<br />
<br />
In order to support our customers who still use the classic EEE Excel Templates, all of them have been updated with support for this new driver as of EEE v1.86 SR6. The recommendation is to use the new driver for connections where possible.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit [https://aka.ms/downloadmsoledbsql aka.ms/downloadmsoledbsql].<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be used.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver.<br />
** 64-bit systems will require the x64 version of the driver. This contains both the 32- and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''. Then continue to use the template as per normal.<br />
<br />
[[File:Excel_Updated_OLEDB_Driver_Support.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Monitoring&diff=1615EEE Monitoring2020-08-26T05:52:32Z<p>Nivin: /* Data Loader Error Log */</p>
<hr />
<div>Created: 28 September 2007. Last Reviewed: 27 January 2009<br />
<br />
<br />
'''EEE Monitoring2'''<br />
<br />
== EEE Monitoring ==<br />
=== Overview ===<br />
The intention of the EEE monitoring is to ensure that all transactions occurring in stores are correctly processed in EEE with no errors, and also to provide an alert of problems that may have occurred. EEE monitoring is an ongoing function that should be performed each day to ensure any problems that occur are not compounded by a lack of immediate action.<br />
<br />
<br />
'''If you are performing your own EEE Monitoring, it is essential that these procedures be followed to ensure your EEE environment contains accurate data. Failure to perform the monitoring procedures could leave you in a situation where your EEE data is not correct or a hardware/software failure occurs and you are unable to recover your data!'''<br />
<br />
<br />
All the examples shown in this document relate to SQL Server 2005.<br />
<br />
<br />
The alerts and weekly reports can be automatically emailed to one or more email addresses, and it is recommended that a minimum of 2 email addresses are alerted to provide coverage in the event of staff being absent.<br />
<br />
<br />
Alert email addresses need to be configured in both EEE and SQL Server.<br />
<br />
<br />
''EEE''<br />
<br />
<br />
The email addresses can be configured from within EEE from the Utilities->Company Preferences menu as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure1.JPG]]<br />
<br />
<br />
''SQL Server''<br />
<br />
<br />
For each EEE database in your SQL Server, you will have a EEE operator, as shown on the screen below<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure2.JPG]]<br />
<br />
<br />
To change the email address for the EEE Operators, highlight the operator (in the example above it is EEE_Operator), and then click on Properties. You will see a screen similar to the one below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure3.JPG]]<br />
<br />
<br />
You can change email addresses by adjusting the E-Mail name field as shown above. Email addresses should be separated by a semi colon (;).<br />
<br />
<br />
The main components providing the EEE Monitoring function are:-<br />
<br />
<br />
* Weekly reports. These reports provide various statistics on the EEE environment.<br />
* EEE Error logs. Whenever more than 10 errors are logged in the EEE errorlog, and alert email will be generated which will include a file detailing all the errors that have occurred. These should be attended to immediately.<br />
* EEE Data Loader. Various circumstances can cause the EEE dataloader to suspend processing, and when this occurs an email alert is generated.<br />
* Disk space Alerts. EEE can be configured to generate email alerts when the free space on nominated disk drives falls below a specified level.<br />
* Unacknowledged Data threshold. – When data has been exported to stores and EEE hasn’t received an acknowledgement for that data within 7 days, an alert email is generated.<br />
<br />
=== Data Loader errors ===<br />
Probably the most important area of EEE Monitoring is checking the EEE Error log for any records that have been rejected by EEE. Failure to monitor the EEE Error Log and fix any rejected records will lead to inaccurate data in EEE, resulting in incorrect sales information, etc.<br />
<br />
<br />
'''''It is most important that the EEE Error Log is monitored on a regular basis.'''''<br />
<br />
<br />
The EEE Web application is used to access the EEE Error Logs. They can be found from Utilities->Data Interchange Management->Data Loader Error Log and also Utilities->Data Interchange Management->Data Loader Activity Log, as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure4.JPG]]<br />
<br />
==== Data Loader Activity Log ====<br />
The Data Loader Activity Log shows the details of every file processed by Data Loader. The defaults for this screen are shown below. You can also filter the activity log so that only files containing errors are shown.<br />
<br />
[[Image:EEE_Monitoring_Figure5.JPG]]<br />
<br />
<br />
A record that has a Y in the “Contains errors” column allows you to drill through to the error log records associated with the activity record.<br />
<br />
<br />
==== Data Loader Error Log ====<br />
There are many types of data loader errors that can appear in the error log. It is not possible to discuss resolutions for all error types, so the most common errors have been addressed below.<br />
<br />
<br />
'''It is extremely important that errorlog records are investigated ASAP. If the problem can’t be resolved, it should be referred to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for assistance in resolving the problem.'''<br />
<br />
<br />
''Timeout Expired''<br />
<br />
<br />
The example below shows a number of timeout errors. These can occur when the SQL Server is very busy with other tasks such as running queries etc, and the timeout period for a transaction to occur is exceeded, so the transaction is aborted and the details of the record being inserted is added to the EEE errorlog table. To fix these types of errors you simple need to reprocess the records.<br />
<br />
<br />
* Click on the 1<sup>st</sup> record to be re-processed. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen. In the example below, the ID number is 26539.<br />
* Replace the number in the To ID box with the record ID number of the last record to be re-processed. In the example below, type 26553<br />
* Click on the REPROCESS button in the bottom right corner of the screen. A file will be created containing all these records in the Reprocess sub-folder of the data loader import folder (something like d:\eeedata\import\reprocess.<br />
* The records written to the reprocess file will then be flagged in the errorlog table as re-processed<br />
<br />
[[Image:EEE_Monitoring_Figure7.JPG]]<br />
<br />
<br />
* After the reprocess button is clicked, and the errorlog records updated, the above records will be removed from the screen as shown below.<br />
<br />
[[Image:EEE_Monitoring_Figure8.JPG]]<br />
<br />
<br />
''Transaction Deadlocked''<br />
<br />
<br />
Deadlocked transactions occur when an attempt is made to update the same record by 2 or more SQL processes as the same time. One of the updates will be selected as the deadlocked record, and the record will be written to the errorlog. <br />
<br />
<br />
Deadlocked transactions should be reprocessed as with timed out records above.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure9.JPG]]<br />
<br />
<br />
''Foreign Key Constraint errors''<br />
<br />
<br />
Foreign Key constraint errors occur when a record contains key values such as product code, customer code, branch code, etc, that do not exist in EEE. Under normal circumstances, these shouldn’t occur so further investigation is required. Some instances that may cause these errors include:-<br />
<br />
<br />
* Product code created in EEE and then deleted after it had been exported to stores. The store performs a transaction with that product code before it received the deletion.<br />
* Customer code is missing. Customer was created in Enabler, but a communications failure prevented the file containing the new customer being correctly sent to Head Office. The customer then makes a purchase in the store and that transaction is sent to Head Office causing a Foreign Key error as the customer is not in EEE.<br />
<br />
The screen below is an example of a number of Foreign Key Constraint error records.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure10.JPG]]<br />
<br />
<br />
If you click on an error record so it is highlighted, and then click on the DETAIL button, you are given further information on the error as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure11.JPG]]<br />
<br />
<br />
In the example above, you can see that the record hasn’t been processed because of a conflict in the productcode column of the Product table. This means that the product code in this record (93281355156943) is not in the product table. <br />
<br />
This may have occurred because the product code was created in store instead of in EEE or the code may have been created in EEE and then deleted, and the deletion hasn’t been sent to the store as yet.<br />
<br />
<br />
This record could be processed by replacing the invalid product code with the correct product code.<br />
<br />
<br />
* ESC from the above screen, and then click on EDIT.<br />
* You are then shown the original record, with the highlighted area of the screen to make any changes as shown below.<br />
* Replace the product code with the correct code and then click Resubmit.<br />
* The record is then re-processed and removed from the error log screen.<br />
<br />
[[Image:EEE_Monitoring_Figure12.JPG]]<br />
<br />
<br />
''Primary Key Constraint errors''<br />
<br />
<br />
Primary Key constraint errors occur because the data that is being inserted violates a primary key setting for the table. Primary key violations stop duplicate data being processed by EEE, and also prevent duplicate items such as duplicate gift voucher numbers being entered.<br />
<br />
<br />
In the example below, a gift voucher transaction has generated a Primary Key violation<br />
<br />
[[Image:EEE_Monitoring_Figure13.JPG]]<br />
<br />
<br />
Clicking on the Detail button gives the information about the error as shown below. This indicates that EEE cannot insert a duplicate key (voucher number) in the Voucher table<br />
<br />
[[Image:EEE_Monitoring_Figure14.JPG]]<br />
<br />
The above situation can occur if Enabler is configured to issue manual gift voucher numbers and the same number is issued twice. A common scenario for this is the store redeems part of a gift voucher, and issues a gift voucher as change, but they reissue the same gift voucher number.<br />
<br />
<br />
The Primary Key violation example below relates to duplicate transactions being rejected by EEE. If you look at the Error Record column on the right hand side, you will see the transactions occurred on 20/02/2007 but the Date column indicates that these errors were generated on 5/03/2007. These types of primary key errors generally indicate that something unusual such as database corruption, has occurred in Enabler on the store computer.<br />
<br />
<br />
Primary Keys prevent the same record being processed more than once. As an example, on the Saleline table, primary keys exist on the fields saledate, saleline, reference2, and kititemnumber. As Enabler can’t generate duplicate combinations of these fields in one transaction, if a combination of these fields already exists in EEE, this will be a duplicate record and EEE will not process the duplicate record and will insert the record in the errorlog table.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure15.JPG]]<br />
<br />
<br />
With the above error records, you should first attempt to send acknowledgements back to the store which will hopefully stop these records being resent by Enabler. If the same records appear in the errorlog a few days later, you will need to contact Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for further assistance.<br />
<br />
To acknowledge these records, do the following.<br />
<br />
<br />
* Click on the 1<sup>st</sup> record to be acknowledged. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen.<br />
* Replace the number in the To ID box with the record ID number of the last record to be acknowledged. Use the arrows to move between screens if there is more than one screen of errors.<br />
* Click on the ACKNOWLEDGE button. Acknowledgement files are then created for sending back to the stores. Acknowledgement records when processed by Enabler, indicate that the record has been processed by EEE, so doesn’t need to be sent again by Enabler. After these records have been acknowledged, you need to flag them as ignored so they don’t appear in the errorlog.<br />
* Click on the 1<sup>st</sup> record to be ignored. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen.<br />
* Replace the number in the To ID box with the record ID number of the last record to be ignored. Use the arrows to move between screens if there is more than one screen of errors.<br />
* Click on the IGNORE button. The records will all be flagged as ignored and not shown on the errorlog screen.<br />
<br />
''Timeout error Inserting Activity Log''<br />
<br />
Note that Timeouts Inserting Activity Log cannot be reprocessed as they don't contain any data. Activity Log is written by Data Loader as a list of activities that it performs. If the Activity Log table is locked by another process (e.g. during nightly purging), Data Loader cannot write the log and the error shows up in the Error Log. These must be ignored.<br />
<br />
=== Weekly emails ===<br />
Each week, a scheduled task is run that produces a number of reports. These reports are emailed to the configured email addresses. The subject of these emails is “SQL Server Report”, and they will usually contain a zip file called WeeklyReportFiles.zip. Contained in this zip file will be:-<br />
<br />
<br />
* dbcc_out.txt<br />
* dbmaint.txt<br />
* errorlog.txt<br />
* mag_erlg.dat<br />
* sqlbackup.txt<br />
<br />
The text of the email will look like:-<br />
<br />
<br />
The email should contain the<br />
<br />
drive sizes,<br />
<br />
database sizes and<br />
<br />
the latest errorlog.<br />
<br />
<br />
companyname <br />
<br />
<nowiki>--------------------------------------------------</nowiki><br />
<br />
Your Company - New Zealand <br />
<br />
<br />
(1 rows affected)<br />
<br />
<br />
The contents of each file is explained below.<br />
<br />
<br />
==== dbcc_out.txt ====<br />
This document is usually very large and contains information about performing an indexdefrag on all table indexes in EEE. This report is mainly for informational purposes only.<br />
<br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
2 0 0 Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
301 159 135 Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
-------------------- -------------------- -------------------- Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
<br />
<br />
<br />
==== dbmaint.txt ====<br />
This report provides information about the free space on all drives on the SQL Server, information about the file that each database/log uses, together with growth statistics, and also the total size and free space in each database and transaction log. This document is extremely useful for monitoring the changing size of your database and log files, and should be examined each month.<br />
<br />
drive MB free <br />
<br />
<nowiki>----- ----------- </nowiki><br />
<br />
C 63036 <br />
<br />
D 2968 <br />
<br />
E 376335 <br />
<br />
<br />
(3 rows affected)<br />
<br />
DBCC execution completed. If DBCC printed error messages, contact your system administrator.<br />
<br />
DBCC execution completed. If DBCC printed error messages, contact your system administrator.<br />
<br />
Name Fileid Filename Filegroup Size Maxsize Growth Usage <br />
<br />
<nowiki>------------------------------ ----------- --------------------------------------------------------------------------- ---------- ------------- ------------- ---------- ---------- </nowiki><br />
<br />
bedb_dat 1 C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf PRIMARY 9536 KB Unlimited 80 KB data only <br />
<br />
bedb_log 2 C:\Program Files\Symantec\Backup Exec\Data\BEDB_Log.ldf NULL 1024 KB Unlimited 10% log only <br />
<br />
EEEData1 1 e:\eeedata\hongkong\data\EEEData1.mdf PRIMARY 5120000 KB Unlimited 512000 KB data only <br />
<br />
EEEData1 1 e:\eeedata\NewZealand\data\EEEData1.mdf PRIMARY 5120000 KB Unlimited 512000 KB data only <br />
<br />
EEEData1 1 e:\eeedata\production\data\EEEData1.mdf PRIMARY 10238976 KB Unlimited 512000 KB data only <br />
<br />
EEEData1 1 e:\eeedata\test\data\EEEData1.mdf PRIMARY 3072000 KB Unlimited 512000 KB data only <br />
<br />
EEELog1 2 e:\eeedata\test\data\EEELog1.ldf NULL 1024000 KB 2147483648 KB 512000 KB log only <br />
<br />
EEELog1 2 e:\eeedata\production\data\EEELog1.ldf NULL 5120000 KB 2147483648 KB 512000 KB log only <br />
<br />
EEELog1 2 e:\eeedata\NewZealand\data\EEELog1.ldf NULL 1024000 KB 2147483648 KB 102400 KB log only <br />
<br />
EEELog1 2 e:\eeedata\hongkong\data\EEELog1.ldf NULL 1126400 KB 2147483648 KB 102400 KB log only <br />
<br />
master 1 E:\sqldata\MSSQL.1\MSSQL\DATA\master.mdf PRIMARY 4096 KB Unlimited 10% data only <br />
<br />
mastlog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\mastlog.ldf NULL 1280 KB Unlimited 10% log only <br />
<br />
modeldev 1 E:\sqldata\MSSQL.1\MSSQL\DATA\model.mdf PRIMARY 2240 KB Unlimited 1024 KB data only <br />
<br />
modellog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\modellog.ldf NULL 26816 KB Unlimited 10% log only <br />
<br />
MSDBData 1 E:\sqldata\MSSQL.1\MSSQL\DATA\MSDBData.mdf PRIMARY 83072 KB Unlimited 10% data only <br />
<br />
MSDBLog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\MSDBLog.ldf NULL 35712 KB 2147483648 KB 10% log only <br />
<br />
ReportServer 1 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServer.mdf PRIMARY 69824 KB Unlimited 1024 KB data only <br />
<br />
ReportServer_log 2 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServer_log.LDF NULL 2624 KB 2147483648 KB 10% log only <br />
<br />
ReportServerTempDB 1 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf PRIMARY 11456 KB Unlimited 1024 KB data only <br />
<br />
ReportServerTempDB_log 2 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServerTempDB_log.LDF NULL 3520 KB 2147483648 KB 10% log only <br />
<br />
tempdev 1 E:\sqldata\MSSQL.1\MSSQL\DATA\tempdb.mdf PRIMARY 38208 KB Unlimited 10% data only <br />
<br />
templog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\templog.ldf NULL 15040 KB Unlimited 10% log only <br />
<br />
<br />
LNm Tot Mb Used Mb Free MbData %Log DB Typ EntryDt <br />
<br />
<nowiki>------------------------- --------------- --------------- ---------------- ------------------------- ----- ----------------------- </nowiki><br />
<br />
ReportServerTempDB 11.1875 1.6250 9.5625 ReportServerTempDB Data 2007-09-03 05:00:01.020 <br />
<br />
ReportServer 68.1875 68.0625 .1250 ReportServer Data 2007-09-03 05:00:01.020 <br />
<br />
EEEData1 5000.0000 15.4375 4984.5625 NewZealand Data 2007-09-03 05:00:01.020 <br />
<br />
MSDBData 81.1250 74.9375 6.1875 msdb Data 2007-09-03 05:00:01.020 <br />
<br />
master 4.0000 2.9375 1.0625 master Data 2007-09-03 05:00:01.003 <br />
<br />
EEEData1 5000.0000 225.8125 4774.1875 HongKong Data 2007-09-03 05:00:01.020 <br />
<br />
EEEData1 3000.0000 207.7500 2792.2500 eeetest Data 2007-09-03 05:00:01.020 <br />
<br />
EEEData1 9999.0000 381.7500 9617.2500 eee Data 2007-09-03 05:00:01.020 <br />
<br />
bedb_dat 9.3125 9.1875 .1250 BEDB Data 2007-09-03 05:00:01.020 <br />
<br />
ReportServerTempDB 3.4297 1.0366 69.7751 ReportServerTempDB Log 2007-09-03 05:00:01.003 <br />
<br />
ReportServer 2.5547 .9551 62.6147 ReportServer Log 2007-09-03 05:00:01.003 <br />
<br />
NewZealand 999.9922 30.7939 96.9206 NewZealand Log 2007-09-03 05:00:01.003 <br />
<br />
msdb 34.8672 7.0820 79.6886 msdb Log 2007-09-03 05:00:01.003 <br />
<br />
master 1.2422 .6094 50.9434 master Log 2007-09-03 05:00:01.003 <br />
<br />
HongKong 1099.9922 53.8052 95.1086 HongKong Log 2007-09-03 05:00:01.003 <br />
<br />
eeetest 999.9922 505.6001 49.4396 eeetest Log 2007-09-03 05:00:01.003 <br />
<br />
eee 4999.9922 27.6509 99.4470 eee Log 2007-09-03 05:00:01.003 <br />
<br />
BEDB .9922 .5776 41.7815 BEDB Log 2007-09-03 05:00:01.003 <br />
<br />
<br />
==== errorlog.txt ====<br />
The errorlog.txt contains the latest SQL Server log. Each week when the weekly reports are run, a new SQL Server error log is started and the previous log is included in this email.<br />
<br />
<br />
==== mag_erlg.dat ====<br />
This document contains outstanding error log records for the past week, so since the last EEE Errorlog alert was generated. Records in this file should be attended to immediately. Refer the section on “Data Loader Errors” for more information.<br />
<br />
<br />
Id !ErrDate !ErrSource !ErrDescription !ErrData1 !ErrData2 !ErrRecord !ErrReprocessCount!EditedRecord !ErrIgnored!ActivityNumber!AddDate <br />
<br />
<nowiki>-----------!-----------------------!------------------------------------------------------------!--------------------------------------</nowiki><br />
<br />
26180!2007-06-27 23:13:39.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098481|00|20070627|5932","GL",19,"00",04,"20070627","11:20:58","6688","00000400014881",2,1,24.3,48.6,"9319868102841","8924B00","0009",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:13:40.233<br />
<br />
26181!2007-06-27 23:14:24.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098483|00|20070627|5914","GL",20,"00",04,"20070627","11:20:58","6688","00000400014881",1,1,24.3,24.3,"9319868102858","8924B00","0010",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:14:24.293<br />
<br />
26182!2007-06-27 23:15:55.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098597|00|20070627|5710","GL",1,"00",04,"20070627","13:07:02","6688","00000400014882",1,1,70,70,"93281355163283","6971B00","0011",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:15:55.077<br />
<br />
<br />
==== sqlbackup.txt ====<br />
This report provides a snapshot of the last database backup date for every database on your SQL Server. This report should be examined each week to make sure that your databases are being backed up regularly.<br />
<br />
<br />
Databases and backups on server NBSQLSVR <br />
<br />
<br />
Database Backup Date Comment <br />
<br />
<nowiki>---------------------------------------- ------------- ------------------------------- </nowiki><br />
<br />
BEDB Sep 3 2007 Backup is current within a day <br />
<br />
eee Sep 2 2007 Backup is current within a day <br />
<br />
eee Sep 2 2007 Backup is current within a day <br />
<br />
eeetest Sep 2 2007 Backup is current within a day <br />
<br />
HongKong Sep 2 2007 Backup is current within a day <br />
<br />
master Sep 3 2007 Backup is current within a day <br />
<br />
model Sep 3 2007 Backup is current within a day <br />
<br />
msdb Sep 3 2007 Backup is current within a day <br />
<br />
NewZealand Sep 3 2007 Backup is current within a day <br />
<br />
ReportServer Aug 31 2007 Backup is current within a week <br />
<br />
ReportServerTempDB Aug 31 2007 Backup is current within a week<br />
<br />
<br />
=== Alert emails ===<br />
Alert emails are intended to assist you with monitoring your EEE environment. Do not rely on them as the only means of notifying you of problems. Various conditions external to EEE can prevent alert emails being delivered.<br />
<br />
There are many circumstances that will cause EEE to generate an alert email. The most common have been explained in the section below. If you receive any other alerts, please advise Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) immediately so you can be advised of what action to take.<br />
<br />
==== Disk Space Alerts ====<br />
EEE has a scheduled task where you can configure alerts to be received when the disk space on nominated drives falls below a set threshold. This task is called Magenta DBM Monitor Disk Space and is scheduled to run via SQL Agent. By default, this job runs every hour, so if you receive a disk space alert email, the emails will continue every hour until the free disk space is above the specified threshold.<br />
<br />
This scheduled task will look similar to the script below, with one line for each disk being monitored.<br />
<br />
<br />
exec usp_dbm_diskspace_monitor @drivename = c, @spacelimit = 5000<br />
<br />
exec usp_dbm_diskspace_monitor @drivename = d, @spacelimit = 15000<br />
<br />
exec usp_dbm_diskspace_monitor @drivename = e, @spacelimit = 25000<br />
<br />
<br />
''When an alert email is generated, the email will have the subject of:-''<br />
<br />
<br />
SQL Server Job System: 'EEE_Magenta DBM Monitor Disk Space' completed on [//MACHINE \\MACHINE]<br />
<br />
where [//machine \\machine] is the name of the computer the alert is for.<br />
<br />
<br />
''The email will contain information similar to:-''<br />
<br />
<br />
JOB RUN:'EEE_Magenta DBM Monitor Disk Space' was run on 6/09/2007 at 12:28:30 PM<br />
<br />
DURATION:0 hours, 0 minutes, 0 seconds<br />
<br />
STATUS: Failed<br />
<br />
MESSAGES:The job failed. The Job was invoked by User MACHINE\Trevor. The last step to run was step 1 (step1).<br />
<br />
<br />
To get further information on the failure, you need to go to Microsoft SQL Server Management Studio, and under SQL Agent, expand Jobs as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure16.JPG]]<br />
<br />
<br />
Right click on the Magenta DBM Monitor Disk Space job, and then select “View History”. You will see a screen similar to below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure17.JPG]]<br />
<br />
<br />
To get further information on the failed job, click on the + beside the job with the [[Image:EEE_Monitoring_Figure18.JPG]] beside it. Click on the next line which will also have a [[Image:EEE_Monitoring_Figure18.JPG]] on it, and you will see a screen similar to below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure19.JPG]]<br />
<br />
The screen above shows that C: drive is less than the specified limit of 13000MB, and the available space is 12634MB. This indicates that you need free space on C: drive so the available space is > the specified limit.<br />
<br />
<br />
==== Data Loader Alerts ====<br />
Whenever data loader encounters a situation that causes 50 errors within 5 seconds, a Data Loader alert email is generated with the subject of “Data Loader Error Count Exceeded”. This email will contain the following text.<br />
<br />
<br />
Data Loader has exceeded 50 server errors within 5 seconds and it is suspending operations. Please review the Windows Application Event Log and take whatever steps are necessary to resolve the problem, then stop and restart the EEE Data Loader Service. <br />
<br />
<br />
Data Loader will not process any data for any company/database until this problem has been resolved. Data flowing in from stores will be queued until Data Loader is restarted.<br />
<br />
<br />
'''It is very important to realize that when you receive this email, if you take no action, then data loader will not process any further transactions into EEE!'''<br />
<br />
<br />
Usually, when the above alert is received, the first action you should take is from the Services icon, in Administrative Tools, highlight the EEE Data Loader service and restart it. In the majority of cases this will fix the problem.<br />
<br />
<br />
If data loader immediately generates another alert, then further investigation is usually required. To find the details of what is causing Data Loader to stop, go to the Windows Application Event Log where you will see a number of error messages relating to EEE Data Loader.<br />
<br />
<br />
There can be many causes of these errors, so if you are unsure of what action to take, this should be escalated to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) as a matter of urgency.<br />
<br />
<br />
==== EEE Error Log Alerts ====<br />
When data loader inserts 10 or more records in the EEE errorlog table, an alert email is sent as a warning that this has occurred. The subject of the email will be:-<br />
<br />
<br />
SQL Server Report for EEE Errorlog for ''Your Company''<br />
<br />
<br />
and the email will have text of:-<br />
<br />
<br />
Threshold for Errorlog reached. This email should contain the<br />
<br />
the latest errorlog.<br />
<br />
There have been 17 errors from limit of 10.<br />
<br />
companyname <br />
<br />
<nowiki>--------------------------------------------------</nowiki><br />
<br />
Your Company <br />
<br />
<br />
(1 rows affected)<br />
<br />
<br />
This email will also contain an attachment called “mag_erlg.dat” which is a text file containing all the errors. These errors need to be immediately investigated to determine the cause. The problem maybe as simple as time outs where you need to re-process the records, or there maybe more serious issues. For further information on the types of errors you may find, see the section titled “Data Loader Errors” earlier in this document.<br />
<br />
<br />
==== EEE Export Maintenance Threshold Alerts ====<br />
EEE Exporter is the program that extracts data from your EEE database and creates an isl-file.dat to be imported at each store. The EEE Exporter is usually configured to export new and unacknowledged data and unacknowledged data is resent if an acknowledgement hasn’t been received from the store within a predefined time period.<br />
<br />
<br />
When exporter extracts each record to be exporter to stores, a record is created in the exportmaintenance table in EEE. When an isl-file.dat is processed in each store, an acknowledgement record is generated for each record processed, and this acknowledgment record then removes the corresponding record from the exportmaintenance table.<br />
<br />
<br />
Exporting unacknowledged records involves resending all records from exportmaintenance that our outside the resend time period.<br />
<br />
<br />
When records have been in exportmaintenance for more than 7 days, an export maintenance threshold email alert is generated.<br />
<br />
<br />
This email will have a subject of:-<br />
<br />
<br />
SQL Server Alert System: 'UnAcknowledged Data Exceeded Threshold' occurred on \\MACHINE<br />
<br />
<br />
And will contain text of:-<br />
<br />
<br />
DATE/TIME:30/08/2007 8:00:00 AM<br />
<br />
<br />
DESCRIPTION:Error: 60005 Severity: 16 State: 1 Branch 203 has 41 unacknowledged maintenance records > 7 days old.<br />
<br />
<br />
COMMENT:Please Investigate.<br />
<br />
<br />
JOB RUN:(None)<br />
<br />
<br />
In addition to the above information, all export maintenance threshold alerts are also written to the SQL log as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure20.JPG]]<br />
<br />
<br />
When these alerts occur, you need to determine why these alerts are being generated. Possible causes include:-<br />
<br />
<br />
* Isl-file.zip (or isl-file.dat) is still in the stores export directory. Possible communications failure.<br />
* Enabler is configured to only process import maintenance as a scheduled task, and Enabler is being shutdown at night preventing the Enabler scheduled tasks from running.<br />
* Isl-file.zip’s are not configured to append the date to the name and are overwriting existing files in the store. Use EEE Enterprise Configurator to turn on option to “Append date to export filenames” as shown below.<br />
<br />
[[Image:EEE_Monitoring_Figure21.JPG]]<br />
<br />
<br />
* Error occurring during import of host maintenance preventing acknowledgement records being created. Investigate cause of error.<br />
* Acknowledgement records being created by Enabler but not being sent to EEE. Possible communications problem or Enabler configuration issue.<br />
<br />
While these errors persist, stores are most likely not receiving product maintenance, so these need to be investigate ASAP. If the reason cannot be determined, please forward details to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for further investigation.<br />
<br />
<br />
==== Database Backup Alerts ====<br />
EEE has scheduled tasks which are used to perform database and transaction log backups. The backups can be configured to run on a 2 day cycle or a 7 day cycle. When one of these backups fails, an alert email is generated with a subject similar to:-<br />
<br />
<br />
SQL Server Job System: 'eeehk_MWFSDBBackup' completed on [//DELL-TT \\DELL-TT]<br />
<br />
<br />
And containing text similar to what is shown below.<br />
<br />
<br />
JOB RUN:'eeehk_MWFSDBBackup' was run on 6/09/2007 at 4:37:23 PM<br />
<br />
DURATION:0 hours, 0 minutes, 3 seconds<br />
<br />
STATUS: Failed<br />
<br />
MESSAGES:The job failed. The Job was invoked by User DELL-TT\Trevor. The last step to run was step 1 (Step1_RunBackup).<br />
<br />
<br />
The above information indicates that the backup has failed, but you need to look at the scheduled task within Microsoft SQL Server Management Studio, and under SQL Agent, expand Jobs as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure22.JPG]]<br />
<br />
<br />
Right click on the failed database backup job, and then select “View History”. You will see a screen similar to below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure23.JPG]]<br />
<br />
<br />
To get further information on the failed job, click on the + beside the job with the [[Image:EEE_Monitoring_Figure18.JPG]] beside it. Click on the next line which will also have a [[Image:EEE_Monitoring_Figure18.JPG]] on it, and you will see a screen similar to below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure24.JPG]]<br />
<br />
<br />
The message shown above will then assist you in determining why the backup failed. If you are backing up to a network location, a network error can result in a corrupt backup device. The easiest fix for a corrupt backup device is to delete the file MWFSDB.BAK or TTSDB.BAK, as these devices get re-created when the job is next run. If you have deleted a backup device, you should run another backup ASAP.<br />
<br />
<br />
==== Log Backup Alerts ====<br />
EEE has scheduled tasks which are used to perform database and transaction log backups. The backups can be configured to run on a 2 day cycle or a 7 day cycle. When one of these backups fails, an alert email is generated with a subject similar to:-<br />
<br />
<br />
SQL Server Job System: 'eeehk_MWFSLogBackup' completed on [//DELL-TT \\DELL-TT]<br />
<br />
<br />
And containing text similar to what is shown below.<br />
<br />
<br />
JOB RUN:'eeehk_MWFSLogBackup' was run on 6/09/2007 at 4:52:02 PM<br />
<br />
DURATION:0 hours, 0 minutes, 0 seconds<br />
<br />
STATUS: Failed<br />
<br />
MESSAGES:The job failed. The Job was invoked by User DELL-TT\Trevor. The last step to run was step 1 (Step1_RunBackup).<br />
<br />
<br />
The procedure for investigating a log backup failure is the same as for a database backup failure detailed earlier.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Monitoring&diff=1614EEE Monitoring2020-08-26T05:51:44Z<p>Nivin: /* Data Loader Error Log */</p>
<hr />
<div>Created: 28 September 2007. Last Reviewed: 27 January 2009<br />
<br />
<br />
'''EEE Monitoring2'''<br />
<br />
== EEE Monitoring ==<br />
=== Overview ===<br />
The intention of the EEE monitoring is to ensure that all transactions occurring in stores are correctly processed in EEE with no errors, and also to provide an alert of problems that may have occurred. EEE monitoring is an ongoing function that should be performed each day to ensure any problems that occur are not compounded by a lack of immediate action.<br />
<br />
<br />
'''If you are performing your own EEE Monitoring, it is essential that these procedures be followed to ensure your EEE environment contains accurate data. Failure to perform the monitoring procedures could leave you in a situation where your EEE data is not correct or a hardware/software failure occurs and you are unable to recover your data!'''<br />
<br />
<br />
All the examples shown in this document relate to SQL Server 2005.<br />
<br />
<br />
The alerts and weekly reports can be automatically emailed to one or more email addresses, and it is recommended that a minimum of 2 email addresses are alerted to provide coverage in the event of staff being absent.<br />
<br />
<br />
Alert email addresses need to be configured in both EEE and SQL Server.<br />
<br />
<br />
''EEE''<br />
<br />
<br />
The email addresses can be configured from within EEE from the Utilities->Company Preferences menu as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure1.JPG]]<br />
<br />
<br />
''SQL Server''<br />
<br />
<br />
For each EEE database in your SQL Server, you will have a EEE operator, as shown on the screen below<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure2.JPG]]<br />
<br />
<br />
To change the email address for the EEE Operators, highlight the operator (in the example above it is EEE_Operator), and then click on Properties. You will see a screen similar to the one below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure3.JPG]]<br />
<br />
<br />
You can change email addresses by adjusting the E-Mail name field as shown above. Email addresses should be separated by a semi colon (;).<br />
<br />
<br />
The main components providing the EEE Monitoring function are:-<br />
<br />
<br />
* Weekly reports. These reports provide various statistics on the EEE environment.<br />
* EEE Error logs. Whenever more than 10 errors are logged in the EEE errorlog, and alert email will be generated which will include a file detailing all the errors that have occurred. These should be attended to immediately.<br />
* EEE Data Loader. Various circumstances can cause the EEE dataloader to suspend processing, and when this occurs an email alert is generated.<br />
* Disk space Alerts. EEE can be configured to generate email alerts when the free space on nominated disk drives falls below a specified level.<br />
* Unacknowledged Data threshold. – When data has been exported to stores and EEE hasn’t received an acknowledgement for that data within 7 days, an alert email is generated.<br />
<br />
=== Data Loader errors ===<br />
Probably the most important area of EEE Monitoring is checking the EEE Error log for any records that have been rejected by EEE. Failure to monitor the EEE Error Log and fix any rejected records will lead to inaccurate data in EEE, resulting in incorrect sales information, etc.<br />
<br />
<br />
'''''It is most important that the EEE Error Log is monitored on a regular basis.'''''<br />
<br />
<br />
The EEE Web application is used to access the EEE Error Logs. They can be found from Utilities->Data Interchange Management->Data Loader Error Log and also Utilities->Data Interchange Management->Data Loader Activity Log, as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure4.JPG]]<br />
<br />
==== Data Loader Activity Log ====<br />
The Data Loader Activity Log shows the details of every file processed by Data Loader. The defaults for this screen are shown below. You can also filter the activity log so that only files containing errors are shown.<br />
<br />
[[Image:EEE_Monitoring_Figure5.JPG]]<br />
<br />
<br />
A record that has a Y in the “Contains errors” column allows you to drill through to the error log records associated with the activity record.<br />
<br />
<br />
==== Data Loader Error Log ====<br />
There are many types of data loader errors that can appear in the error log. It is not possible to discuss resolutions for all error types, so the most common errors have been addressed below.<br />
<br />
<br />
'''It is extremely important that errorlog records are investigated ASAP. If the problem can’t be resolved, it should be referred to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for assistance in resolving the problem.'''<br />
<br />
<br />
''Timeout Expired''<br />
<br />
<br />
The example below shows a number of timeout errors. These can occur when the SQL Server is very busy with other tasks such as running queries etc, and the timeout period for a transaction to occur is exceeded, so the transaction is aborted and the details of the record being inserted is added to the EEE errorlog table. To fix these types of errors you simple need to reprocess the records.<br />
<br />
<br />
* Click on the 1<sup>st</sup> record to be re-processed. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen. In the example below, the ID number is 26539.<br />
* Replace the number in the To ID box with the record ID number of the last record to be re-processed. In the example below, type 26553<br />
* Click on the REPROCESS button in the bottom right corner of the screen. A file will be created containing all these records in the Reprocess sub-folder of the data loader import folder (something like d:\eeedata\import\reprocess.<br />
* The records written to the reprocess file will then be flagged in the errorlog table as re-processed<br />
<br />
[[Image:EEE_Monitoring_Figure7.JPG]]<br />
<br />
<br />
* After the reprocess button is clicked, and the errorlog records updated, the above records will be removed from the screen as shown below.<br />
<br />
[[Image:EEE_Monitoring_Figure8.JPG]]<br />
<br />
<br />
''Transaction Deadlocked''<br />
<br />
<br />
Deadlocked transactions occur when an attempt is made to update the same record by 2 or more SQL processes as the same time. One of the updates will be selected as the deadlocked record, and the record will be written to the errorlog. <br />
<br />
<br />
Deadlocked transactions should be reprocessed as with timed out records above.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure9.JPG]]<br />
<br />
<br />
''Foreign Key Constraint errors''<br />
<br />
<br />
Foreign Key constraint errors occur when a record contains key values such as product code, customer code, branch code, etc, that do not exist in EEE. Under normal circumstances, these shouldn’t occur so further investigation is required. Some instances that may cause these errors include:-<br />
<br />
<br />
* Product code created in EEE and then deleted after it had been exported to stores. The store performs a transaction with that product code before it received the deletion.<br />
* Customer code is missing. Customer was created in Enabler, but a communications failure prevented the file containing the new customer being correctly sent to Head Office. The customer then makes a purchase in the store and that transaction is sent to Head Office causing a Foreign Key error as the customer is not in EEE.<br />
<br />
The screen below is an example of a number of Foreign Key Constraint error records.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure10.JPG]]<br />
<br />
<br />
If you click on an error record so it is highlighted, and then click on the DETAIL button, you are given further information on the error as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure11.JPG]]<br />
<br />
<br />
In the example above, you can see that the record hasn’t been processed because of a conflict in the productcode column of the Product table. This means that the product code in this record (93281355156943) is not in the product table. <br />
<br />
This may have occurred because the product code was created in store instead of in EEE or the code may have been created in EEE and then deleted, and the deletion hasn’t been sent to the store as yet.<br />
<br />
<br />
This record could be processed by replacing the invalid product code with the correct product code.<br />
<br />
<br />
* ESC from the above screen, and then click on EDIT.<br />
* You are then shown the original record, with the highlighted area of the screen to make any changes as shown below.<br />
* Replace the product code with the correct code and then click Resubmit.<br />
* The record is then re-processed and removed from the error log screen.<br />
<br />
[[Image:EEE_Monitoring_Figure12.JPG]]<br />
<br />
<br />
''Primary Key Constraint errors''<br />
<br />
<br />
Primary Key constraint errors occur because the data that is being inserted violates a primary key setting for the table. Primary key violations stop duplicate data being processed by EEE, and also prevent duplicate items such as duplicate gift voucher numbers being entered.<br />
<br />
<br />
In the example below, a gift voucher transaction has generated a Primary Key violation<br />
<br />
[[Image:EEE_Monitoring_Figure13.JPG]]<br />
<br />
<br />
Clicking on the Detail button gives the information about the error as shown below. This indicates that EEE cannot insert a duplicate key (voucher number) in the Voucher table<br />
<br />
[[Image:EEE_Monitoring_Figure14.JPG]]<br />
<br />
The above situation can occur if Enabler is configured to issue manual gift voucher numbers and the same number is issued twice. A common scenario for this is the store redeems part of a gift voucher, and issues a gift voucher as change, but they reissue the same gift voucher number.<br />
<br />
<br />
The Primary Key violation example below relates to duplicate transactions being rejected by EEE. If you look at the Error Record column on the right hand side, you will see the transactions occurred on 20/02/2007 but the Date column indicates that these errors were generated on 5/03/2007. These types of primary key errors generally indicate that something unusual such as database corruption, has occurred in Enabler on the store computer.<br />
<br />
<br />
Primary Keys prevent the same record being processed more than once. As an example, on the Saleline table, primary keys exist on the fields saledate, saleline, reference2, and kititemnumber. As Enabler can’t generate duplicate combinations of these fields in one transaction, if a combination of these fields already exists in EEE, this will be a duplicate record and EEE will not process the duplicate record and will insert the record in the errorlog table.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure15.JPG]]<br />
<br />
<br />
With the above error records, you should first attempt to send acknowledgements back to the store which will hopefully stop these records being resent by Enabler. If the same records appear in the errorlog a few days later, you will need to contact Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for further assistance.<br />
<br />
To acknowledge these records, do the following.<br />
<br />
<br />
* Click on the 1<sup>st</sup> record to be acknowledged. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen.<br />
* Replace the number in the To ID box with the record ID number of the last record to be acknowledged. Use the arrows to move between screens if there is more than one screen of errors.<br />
* Click on the ACKNOWLEDGE button. Acknowledgement files are then created for sending back to the stores. Acknowledgement records when processed by Enabler, indicate that the record has been processed by EEE, so doesn’t need to be sent again by Enabler. After these records have been acknowledged, you need to flag them as ignored so they don’t appear in the errorlog.<br />
* Click on the 1<sup>st</sup> record to be ignored. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen.<br />
* Replace the number in the To ID box with the record ID number of the last record to be ignored. Use the arrows to move between screens if there is more than one screen of errors.<br />
* Click on the IGNORE button. The records will all be flagged as ignored and not shown on the errorlog screen.<br />
<br />
''Timeout error Inserting Activity Log''<br />
Note that Timeouts Inserting Activity Log cannot be reprocessed as they don't contain any data. Activity Log is written by Data Loader as a list of activities that it performs. If the Activity Log table is locked by another process (e.g. during nightly purging), Data Loader cannot write the log and the error shows up in the Error Log. These must be ignored.<br />
<br />
=== Weekly emails ===<br />
Each week, a scheduled task is run that produces a number of reports. These reports are emailed to the configured email addresses. The subject of these emails is “SQL Server Report”, and they will usually contain a zip file called WeeklyReportFiles.zip. Contained in this zip file will be:-<br />
<br />
<br />
* dbcc_out.txt<br />
* dbmaint.txt<br />
* errorlog.txt<br />
* mag_erlg.dat<br />
* sqlbackup.txt<br />
<br />
The text of the email will look like:-<br />
<br />
<br />
The email should contain the<br />
<br />
drive sizes,<br />
<br />
database sizes and<br />
<br />
the latest errorlog.<br />
<br />
<br />
companyname <br />
<br />
<nowiki>--------------------------------------------------</nowiki><br />
<br />
Your Company - New Zealand <br />
<br />
<br />
(1 rows affected)<br />
<br />
<br />
The contents of each file is explained below.<br />
<br />
<br />
==== dbcc_out.txt ====<br />
This document is usually very large and contains information about performing an indexdefrag on all table indexes in EEE. This report is mainly for informational purposes only.<br />
<br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
2 0 0 Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
301 159 135 Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037 <br />
<br />
-------------------- -------------------- -------------------- Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0% <br />
<br />
<br />
<br />
<br />
==== dbmaint.txt ====<br />
This report provides information about the free space on all drives on the SQL Server, information about the file that each database/log uses, together with growth statistics, and also the total size and free space in each database and transaction log. This document is extremely useful for monitoring the changing size of your database and log files, and should be examined each month.<br />
<br />
drive MB free <br />
<br />
<nowiki>----- ----------- </nowiki><br />
<br />
C 63036 <br />
<br />
D 2968 <br />
<br />
E 376335 <br />
<br />
<br />
(3 rows affected)<br />
<br />
DBCC execution completed. If DBCC printed error messages, contact your system administrator.<br />
<br />
DBCC execution completed. If DBCC printed error messages, contact your system administrator.<br />
<br />
Name Fileid Filename Filegroup Size Maxsize Growth Usage <br />
<br />
<nowiki>------------------------------ ----------- --------------------------------------------------------------------------- ---------- ------------- ------------- ---------- ---------- </nowiki><br />
<br />
bedb_dat 1 C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf PRIMARY 9536 KB Unlimited 80 KB data only <br />
<br />
bedb_log 2 C:\Program Files\Symantec\Backup Exec\Data\BEDB_Log.ldf NULL 1024 KB Unlimited 10% log only <br />
<br />
EEEData1 1 e:\eeedata\hongkong\data\EEEData1.mdf PRIMARY 5120000 KB Unlimited 512000 KB data only <br />
<br />
EEEData1 1 e:\eeedata\NewZealand\data\EEEData1.mdf PRIMARY 5120000 KB Unlimited 512000 KB data only <br />
<br />
EEEData1 1 e:\eeedata\production\data\EEEData1.mdf PRIMARY 10238976 KB Unlimited 512000 KB data only <br />
<br />
EEEData1 1 e:\eeedata\test\data\EEEData1.mdf PRIMARY 3072000 KB Unlimited 512000 KB data only <br />
<br />
EEELog1 2 e:\eeedata\test\data\EEELog1.ldf NULL 1024000 KB 2147483648 KB 512000 KB log only <br />
<br />
EEELog1 2 e:\eeedata\production\data\EEELog1.ldf NULL 5120000 KB 2147483648 KB 512000 KB log only <br />
<br />
EEELog1 2 e:\eeedata\NewZealand\data\EEELog1.ldf NULL 1024000 KB 2147483648 KB 102400 KB log only <br />
<br />
EEELog1 2 e:\eeedata\hongkong\data\EEELog1.ldf NULL 1126400 KB 2147483648 KB 102400 KB log only <br />
<br />
master 1 E:\sqldata\MSSQL.1\MSSQL\DATA\master.mdf PRIMARY 4096 KB Unlimited 10% data only <br />
<br />
mastlog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\mastlog.ldf NULL 1280 KB Unlimited 10% log only <br />
<br />
modeldev 1 E:\sqldata\MSSQL.1\MSSQL\DATA\model.mdf PRIMARY 2240 KB Unlimited 1024 KB data only <br />
<br />
modellog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\modellog.ldf NULL 26816 KB Unlimited 10% log only <br />
<br />
MSDBData 1 E:\sqldata\MSSQL.1\MSSQL\DATA\MSDBData.mdf PRIMARY 83072 KB Unlimited 10% data only <br />
<br />
MSDBLog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\MSDBLog.ldf NULL 35712 KB 2147483648 KB 10% log only <br />
<br />
ReportServer 1 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServer.mdf PRIMARY 69824 KB Unlimited 1024 KB data only <br />
<br />
ReportServer_log 2 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServer_log.LDF NULL 2624 KB 2147483648 KB 10% log only <br />
<br />
ReportServerTempDB 1 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf PRIMARY 11456 KB Unlimited 1024 KB data only <br />
<br />
ReportServerTempDB_log 2 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServerTempDB_log.LDF NULL 3520 KB 2147483648 KB 10% log only <br />
<br />
tempdev 1 E:\sqldata\MSSQL.1\MSSQL\DATA\tempdb.mdf PRIMARY 38208 KB Unlimited 10% data only <br />
<br />
templog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\templog.ldf NULL 15040 KB Unlimited 10% log only <br />
<br />
<br />
LNm Tot Mb Used Mb Free MbData %Log DB Typ EntryDt <br />
<br />
<nowiki>------------------------- --------------- --------------- ---------------- ------------------------- ----- ----------------------- </nowiki><br />
<br />
ReportServerTempDB 11.1875 1.6250 9.5625 ReportServerTempDB Data 2007-09-03 05:00:01.020 <br />
<br />
ReportServer 68.1875 68.0625 .1250 ReportServer Data 2007-09-03 05:00:01.020 <br />
<br />
EEEData1 5000.0000 15.4375 4984.5625 NewZealand Data 2007-09-03 05:00:01.020 <br />
<br />
MSDBData 81.1250 74.9375 6.1875 msdb Data 2007-09-03 05:00:01.020 <br />
<br />
master 4.0000 2.9375 1.0625 master Data 2007-09-03 05:00:01.003 <br />
<br />
EEEData1 5000.0000 225.8125 4774.1875 HongKong Data 2007-09-03 05:00:01.020 <br />
<br />
EEEData1 3000.0000 207.7500 2792.2500 eeetest Data 2007-09-03 05:00:01.020 <br />
<br />
EEEData1 9999.0000 381.7500 9617.2500 eee Data 2007-09-03 05:00:01.020 <br />
<br />
bedb_dat 9.3125 9.1875 .1250 BEDB Data 2007-09-03 05:00:01.020 <br />
<br />
ReportServerTempDB 3.4297 1.0366 69.7751 ReportServerTempDB Log 2007-09-03 05:00:01.003 <br />
<br />
ReportServer 2.5547 .9551 62.6147 ReportServer Log 2007-09-03 05:00:01.003 <br />
<br />
NewZealand 999.9922 30.7939 96.9206 NewZealand Log 2007-09-03 05:00:01.003 <br />
<br />
msdb 34.8672 7.0820 79.6886 msdb Log 2007-09-03 05:00:01.003 <br />
<br />
master 1.2422 .6094 50.9434 master Log 2007-09-03 05:00:01.003 <br />
<br />
HongKong 1099.9922 53.8052 95.1086 HongKong Log 2007-09-03 05:00:01.003 <br />
<br />
eeetest 999.9922 505.6001 49.4396 eeetest Log 2007-09-03 05:00:01.003 <br />
<br />
eee 4999.9922 27.6509 99.4470 eee Log 2007-09-03 05:00:01.003 <br />
<br />
BEDB .9922 .5776 41.7815 BEDB Log 2007-09-03 05:00:01.003 <br />
<br />
<br />
==== errorlog.txt ====<br />
The errorlog.txt contains the latest SQL Server log. Each week when the weekly reports are run, a new SQL Server error log is started and the previous log is included in this email.<br />
<br />
<br />
==== mag_erlg.dat ====<br />
This document contains outstanding error log records for the past week, so since the last EEE Errorlog alert was generated. Records in this file should be attended to immediately. Refer the section on “Data Loader Errors” for more information.<br />
<br />
<br />
Id !ErrDate !ErrSource !ErrDescription !ErrData1 !ErrData2 !ErrRecord !ErrReprocessCount!EditedRecord !ErrIgnored!ActivityNumber!AddDate <br />
<br />
<nowiki>-----------!-----------------------!------------------------------------------------------------!--------------------------------------</nowiki><br />
<br />
26180!2007-06-27 23:13:39.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098481|00|20070627|5932","GL",19,"00",04,"20070627","11:20:58","6688","00000400014881",2,1,24.3,48.6,"9319868102841","8924B00","0009",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:13:40.233<br />
<br />
26181!2007-06-27 23:14:24.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098483|00|20070627|5914","GL",20,"00",04,"20070627","11:20:58","6688","00000400014881",1,1,24.3,24.3,"9319868102858","8924B00","0010",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:14:24.293<br />
<br />
26182!2007-06-27 23:15:55.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098597|00|20070627|5710","GL",1,"00",04,"20070627","13:07:02","6688","00000400014882",1,1,70,70,"93281355163283","6971B00","0011",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:15:55.077<br />
<br />
<br />
==== sqlbackup.txt ====<br />
This report provides a snapshot of the last database backup date for every database on your SQL Server. This report should be examined each week to make sure that your databases are being backed up regularly.<br />
<br />
<br />
Databases and backups on server NBSQLSVR <br />
<br />
<br />
Database Backup Date Comment <br />
<br />
<nowiki>---------------------------------------- ------------- ------------------------------- </nowiki><br />
<br />
BEDB Sep 3 2007 Backup is current within a day <br />
<br />
eee Sep 2 2007 Backup is current within a day <br />
<br />
eee Sep 2 2007 Backup is current within a day <br />
<br />
eeetest Sep 2 2007 Backup is current within a day <br />
<br />
HongKong Sep 2 2007 Backup is current within a day <br />
<br />
master Sep 3 2007 Backup is current within a day <br />
<br />
model Sep 3 2007 Backup is current within a day <br />
<br />
msdb Sep 3 2007 Backup is current within a day <br />
<br />
NewZealand Sep 3 2007 Backup is current within a day <br />
<br />
ReportServer Aug 31 2007 Backup is current within a week <br />
<br />
ReportServerTempDB Aug 31 2007 Backup is current within a week<br />
<br />
<br />
=== Alert emails ===<br />
Alert emails are intended to assist you with monitoring your EEE environment. Do not rely on them as the only means of notifying you of problems. Various conditions external to EEE can prevent alert emails being delivered.<br />
<br />
There are many circumstances that will cause EEE to generate an alert email. The most common have been explained in the section below. If you receive any other alerts, please advise Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) immediately so you can be advised of what action to take.<br />
<br />
==== Disk Space Alerts ====<br />
EEE has a scheduled task where you can configure alerts to be received when the disk space on nominated drives falls below a set threshold. This task is called Magenta DBM Monitor Disk Space and is scheduled to run via SQL Agent. By default, this job runs every hour, so if you receive a disk space alert email, the emails will continue every hour until the free disk space is above the specified threshold.<br />
<br />
This scheduled task will look similar to the script below, with one line for each disk being monitored.<br />
<br />
<br />
exec usp_dbm_diskspace_monitor @drivename = c, @spacelimit = 5000<br />
<br />
exec usp_dbm_diskspace_monitor @drivename = d, @spacelimit = 15000<br />
<br />
exec usp_dbm_diskspace_monitor @drivename = e, @spacelimit = 25000<br />
<br />
<br />
''When an alert email is generated, the email will have the subject of:-''<br />
<br />
<br />
SQL Server Job System: 'EEE_Magenta DBM Monitor Disk Space' completed on [//MACHINE \\MACHINE]<br />
<br />
where [//machine \\machine] is the name of the computer the alert is for.<br />
<br />
<br />
''The email will contain information similar to:-''<br />
<br />
<br />
JOB RUN:'EEE_Magenta DBM Monitor Disk Space' was run on 6/09/2007 at 12:28:30 PM<br />
<br />
DURATION:0 hours, 0 minutes, 0 seconds<br />
<br />
STATUS: Failed<br />
<br />
MESSAGES:The job failed. The Job was invoked by User MACHINE\Trevor. The last step to run was step 1 (step1).<br />
<br />
<br />
To get further information on the failure, you need to go to Microsoft SQL Server Management Studio, and under SQL Agent, expand Jobs as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure16.JPG]]<br />
<br />
<br />
Right click on the Magenta DBM Monitor Disk Space job, and then select “View History”. You will see a screen similar to below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure17.JPG]]<br />
<br />
<br />
To get further information on the failed job, click on the + beside the job with the [[Image:EEE_Monitoring_Figure18.JPG]] beside it. Click on the next line which will also have a [[Image:EEE_Monitoring_Figure18.JPG]] on it, and you will see a screen similar to below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure19.JPG]]<br />
<br />
The screen above shows that C: drive is less than the specified limit of 13000MB, and the available space is 12634MB. This indicates that you need free space on C: drive so the available space is > the specified limit.<br />
<br />
<br />
==== Data Loader Alerts ====<br />
Whenever data loader encounters a situation that causes 50 errors within 5 seconds, a Data Loader alert email is generated with the subject of “Data Loader Error Count Exceeded”. This email will contain the following text.<br />
<br />
<br />
Data Loader has exceeded 50 server errors within 5 seconds and it is suspending operations. Please review the Windows Application Event Log and take whatever steps are necessary to resolve the problem, then stop and restart the EEE Data Loader Service. <br />
<br />
<br />
Data Loader will not process any data for any company/database until this problem has been resolved. Data flowing in from stores will be queued until Data Loader is restarted.<br />
<br />
<br />
'''It is very important to realize that when you receive this email, if you take no action, then data loader will not process any further transactions into EEE!'''<br />
<br />
<br />
Usually, when the above alert is received, the first action you should take is from the Services icon, in Administrative Tools, highlight the EEE Data Loader service and restart it. In the majority of cases this will fix the problem.<br />
<br />
<br />
If data loader immediately generates another alert, then further investigation is usually required. To find the details of what is causing Data Loader to stop, go to the Windows Application Event Log where you will see a number of error messages relating to EEE Data Loader.<br />
<br />
<br />
There can be many causes of these errors, so if you are unsure of what action to take, this should be escalated to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) as a matter of urgency.<br />
<br />
<br />
==== EEE Error Log Alerts ====<br />
When data loader inserts 10 or more records in the EEE errorlog table, an alert email is sent as a warning that this has occurred. The subject of the email will be:-<br />
<br />
<br />
SQL Server Report for EEE Errorlog for ''Your Company''<br />
<br />
<br />
and the email will have text of:-<br />
<br />
<br />
Threshold for Errorlog reached. This email should contain the<br />
<br />
the latest errorlog.<br />
<br />
There have been 17 errors from limit of 10.<br />
<br />
companyname <br />
<br />
<nowiki>--------------------------------------------------</nowiki><br />
<br />
Your Company <br />
<br />
<br />
(1 rows affected)<br />
<br />
<br />
This email will also contain an attachment called “mag_erlg.dat” which is a text file containing all the errors. These errors need to be immediately investigated to determine the cause. The problem maybe as simple as time outs where you need to re-process the records, or there maybe more serious issues. For further information on the types of errors you may find, see the section titled “Data Loader Errors” earlier in this document.<br />
<br />
<br />
==== EEE Export Maintenance Threshold Alerts ====<br />
EEE Exporter is the program that extracts data from your EEE database and creates an isl-file.dat to be imported at each store. The EEE Exporter is usually configured to export new and unacknowledged data and unacknowledged data is resent if an acknowledgement hasn’t been received from the store within a predefined time period.<br />
<br />
<br />
When exporter extracts each record to be exporter to stores, a record is created in the exportmaintenance table in EEE. When an isl-file.dat is processed in each store, an acknowledgement record is generated for each record processed, and this acknowledgment record then removes the corresponding record from the exportmaintenance table.<br />
<br />
<br />
Exporting unacknowledged records involves resending all records from exportmaintenance that our outside the resend time period.<br />
<br />
<br />
When records have been in exportmaintenance for more than 7 days, an export maintenance threshold email alert is generated.<br />
<br />
<br />
This email will have a subject of:-<br />
<br />
<br />
SQL Server Alert System: 'UnAcknowledged Data Exceeded Threshold' occurred on \\MACHINE<br />
<br />
<br />
And will contain text of:-<br />
<br />
<br />
DATE/TIME:30/08/2007 8:00:00 AM<br />
<br />
<br />
DESCRIPTION:Error: 60005 Severity: 16 State: 1 Branch 203 has 41 unacknowledged maintenance records > 7 days old.<br />
<br />
<br />
COMMENT:Please Investigate.<br />
<br />
<br />
JOB RUN:(None)<br />
<br />
<br />
In addition to the above information, all export maintenance threshold alerts are also written to the SQL log as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure20.JPG]]<br />
<br />
<br />
When these alerts occur, you need to determine why these alerts are being generated. Possible causes include:-<br />
<br />
<br />
* Isl-file.zip (or isl-file.dat) is still in the stores export directory. Possible communications failure.<br />
* Enabler is configured to only process import maintenance as a scheduled task, and Enabler is being shutdown at night preventing the Enabler scheduled tasks from running.<br />
* Isl-file.zip’s are not configured to append the date to the name and are overwriting existing files in the store. Use EEE Enterprise Configurator to turn on option to “Append date to export filenames” as shown below.<br />
<br />
[[Image:EEE_Monitoring_Figure21.JPG]]<br />
<br />
<br />
* Error occurring during import of host maintenance preventing acknowledgement records being created. Investigate cause of error.<br />
* Acknowledgement records being created by Enabler but not being sent to EEE. Possible communications problem or Enabler configuration issue.<br />
<br />
While these errors persist, stores are most likely not receiving product maintenance, so these need to be investigate ASAP. If the reason cannot be determined, please forward details to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for further investigation.<br />
<br />
<br />
==== Database Backup Alerts ====<br />
EEE has scheduled tasks which are used to perform database and transaction log backups. The backups can be configured to run on a 2 day cycle or a 7 day cycle. When one of these backups fails, an alert email is generated with a subject similar to:-<br />
<br />
<br />
SQL Server Job System: 'eeehk_MWFSDBBackup' completed on [//DELL-TT \\DELL-TT]<br />
<br />
<br />
And containing text similar to what is shown below.<br />
<br />
<br />
JOB RUN:'eeehk_MWFSDBBackup' was run on 6/09/2007 at 4:37:23 PM<br />
<br />
DURATION:0 hours, 0 minutes, 3 seconds<br />
<br />
STATUS: Failed<br />
<br />
MESSAGES:The job failed. The Job was invoked by User DELL-TT\Trevor. The last step to run was step 1 (Step1_RunBackup).<br />
<br />
<br />
The above information indicates that the backup has failed, but you need to look at the scheduled task within Microsoft SQL Server Management Studio, and under SQL Agent, expand Jobs as shown below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure22.JPG]]<br />
<br />
<br />
Right click on the failed database backup job, and then select “View History”. You will see a screen similar to below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure23.JPG]]<br />
<br />
<br />
To get further information on the failed job, click on the + beside the job with the [[Image:EEE_Monitoring_Figure18.JPG]] beside it. Click on the next line which will also have a [[Image:EEE_Monitoring_Figure18.JPG]] on it, and you will see a screen similar to below.<br />
<br />
<br />
[[Image:EEE_Monitoring_Figure24.JPG]]<br />
<br />
<br />
The message shown above will then assist you in determining why the backup failed. If you are backing up to a network location, a network error can result in a corrupt backup device. The easiest fix for a corrupt backup device is to delete the file MWFSDB.BAK or TTSDB.BAK, as these devices get re-created when the job is next run. If you have deleted a backup device, you should run another backup ASAP.<br />
<br />
<br />
==== Log Backup Alerts ====<br />
EEE has scheduled tasks which are used to perform database and transaction log backups. The backups can be configured to run on a 2 day cycle or a 7 day cycle. When one of these backups fails, an alert email is generated with a subject similar to:-<br />
<br />
<br />
SQL Server Job System: 'eeehk_MWFSLogBackup' completed on [//DELL-TT \\DELL-TT]<br />
<br />
<br />
And containing text similar to what is shown below.<br />
<br />
<br />
JOB RUN:'eeehk_MWFSLogBackup' was run on 6/09/2007 at 4:52:02 PM<br />
<br />
DURATION:0 hours, 0 minutes, 0 seconds<br />
<br />
STATUS: Failed<br />
<br />
MESSAGES:The job failed. The Job was invoked by User DELL-TT\Trevor. The last step to run was step 1 (Step1_RunBackup).<br />
<br />
<br />
The procedure for investigating a log backup failure is the same as for a database backup failure detailed earlier.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_WMS_Service&diff=1613EEE WMS Service2020-07-14T02:06:04Z<p>Nivin: </p>
<hr />
<div>* The EEE WMS Service performs tasks relating to transmission of data between EEE and the 3rd party WMS.<br />
* This service is installed manually - there is no installer available - but it can be updated using the normal service release installer (EEEPatch)<br />
* The recommended location to install the service is beside existing EEE apps and services. E.g. C:\EEE\EEEWMSService.<br />
* Copy files to the target directory<br />
* The executable EEEWmsService.exe can be called with the following flags to install/uninstall the service.<br />
** '''EEEWmsService -i''' to install. Can also use '''-install''', or call without any parameters<br />
** '''EEEWmsService -u''' to uninstall. Can also use '''-uninstall'''<br />
* Please make sure you run with Administrative privileges so you have permissions to install a service (write to registry)<br />
* When installing, you will be prompted to provide the credentials for the user that the service will run as. Ensure you specify the full user name - i.e. MACHINE\User or DOMAIN\User<br />
* Service will need standard-level of access into the EEE database so the recommended user account is EEEServices<br />
* Once installed, the service can be started from the Windows service control panel (services.msc)<br />
* Grant the same user account permissions to write to the install directory. This is to enable the service to write logs, and working/archive files.<br />
<br />
[[File:Wms-service.png]]<br />
[[File:service-login.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_WMS_Service&diff=1612EEE WMS Service2020-07-14T02:04:41Z<p>Nivin: </p>
<hr />
<div>* The EEE WMS Service performs tasks relating to transmission of data between EEE and the 3rd party WMS.<br />
* This service is installed manually - there is no installer available - but it can be updated using the normal service release installer (EEEPatch)<br />
* The recommended location to install the service is beside existing EEE apps and services. E.g. C:\EEE\EEEWMSService.<br />
* Copy files to the target directory<br />
* The executable EEEWmsService.exe can be called with the following flags to install/uninstall the service.<br />
** '''EEEWmsService -i''' to install. Can also use '''-install''', or call without any parameters<br />
** '''EEEWmsService -u''' to uninstall. Can also use '''-uninstall'''<br />
* Please make sure you run with Administrative privileges so you have permissions to install a service (write to registry)<br />
* When installing, you will be prompted to provide the credentials for the user that the service will run as. Ensure you specify the full user name - i.e. MACHINE\User or DOMAIN\User<br />
* Service will need standard-level of access into the EEE database so the recommended user account is EEEServices<br />
* Grant the same user account permissions to write to the install directory. This is to enable the service to write logs, and working/archive files.<br />
<br />
[[File:Wms-service.png]]<br />
[[File:service-login.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_WMS_Service&diff=1611EEE WMS Service2020-07-14T02:04:26Z<p>Nivin: </p>
<hr />
<div>* The EEE WMS Service performs tasks relating to transmission of data between EEE and the 3rd party WMS.<br />
* This service is installed manually - there is no installer available - but it can be updated using the normal service release installer (EEEPatch)<br />
* The recommended location to install the service is beside existing EEE apps and services. E.g. C:\EEE\EEEWMSService.<br />
* Copy files to the target directory<br />
* The executable EEEWmsService.exe can be called with the following flags to install/uninstall the service.<br />
** '''EEEWmsService -i''' to install. Can also use '''-install''', or call without any parameters<br />
** '''EEEWmsService -u''' to uninstall. Can also use '''-uninstall'''<br />
* Please make sure you run with Administrative privileges so you have permissions to install a service (write to registry)<br />
* When installing, you will be prompted to provide the credentials for the user that the service will run as. Ensure you specify the full user name - i.e. MACHINE\User or DOMAIN\User<br />
* Service will need standard-level of access into the EEE database so the recommended user account is EEEServices<br />
* Grant the same user account permissions to write to the install directory. This is to enable the service to write logs, and working/archive files.<br />
<br />
[[File:service-login.png]]<br />
[[File:Wms-service.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_WMS_Service&diff=1610EEE WMS Service2020-07-14T02:04:14Z<p>Nivin: </p>
<hr />
<div>* The EEE WMS Service performs tasks relating to transmission of data between EEE and the 3rd party WMS.<br />
* This service is installed manually - there is no installer available - but it can be updated using the normal service release installer (EEEPatch)<br />
* The recommended location to install the service is beside existing EEE apps and services. E.g. C:\EEE\EEEWMSService.<br />
* Copy files to the target directory<br />
* The executable EEEWmsService.exe can be called with the following flags to install/uninstall the service.<br />
** '''EEEWmsService -i''' to install. Can also use '''-install''', or call without any parameters<br />
** '''EEEWmsService -u''' to uninstall. Can also use '''-uninstall'''<br />
* Please make sure you run with Administrative privileges so you have permissions to install a service (write to registry)<br />
* When installing, you will be prompted to provide the credentials for the user that the service will run as. Ensure you specify the full user name - i.e. MACHINE\User or DOMAIN\User<br />
* Service will need standard-level of access into the EEE database so the recommended user account is EEEServices<br />
* Grant the same user account permissions to write to the install directory. This is to enable the service to write logs, and working/archive files.<br />
<br />
[[File:service-login.png]]<br />
[[File:Wms-service.png.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=File:Wms-service.png&diff=1609File:Wms-service.png2020-07-14T02:03:49Z<p>Nivin: WMS Service install directory</p>
<hr />
<div>== Summary ==<br />
WMS Service install directory</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_WMS_Service&diff=1608EEE WMS Service2020-07-14T02:02:25Z<p>Nivin: </p>
<hr />
<div>* The EEE WMS Service performs tasks relating to transmission of data between EEE and the 3rd party WMS.<br />
* This service is installed manually - there is no installer available - but it can be updated using the normal service release installer (EEEPatch)<br />
* The recommended location to install the service is beside existing EEE apps and services. E.g. C:\EEE\EEEWMSService.<br />
* Copy files to the target directory<br />
* The executable EEEWmsService.exe can be called with the following flags to install/uninstall the service.<br />
** '''EEEWmsService -i''' to install. Can also use '''-install''', or call without any parameters<br />
** '''EEEWmsService -u''' to uninstall. Can also use '''-uninstall'''<br />
* Please make sure you run with Administrative privileges so you have permissions to install a service (write to registry)<br />
* When installing, you will be prompted to provide the credentials for the user that the service will run as. Ensure you specify the full user name - i.e. MACHINE\User or DOMAIN\User<br />
* Service will need standard-level of access into the EEE database so the recommended user account is EEEServices<br />
* Grant the same user account permissions to write to the install directory. This is to enable the service to write logs, and working/archive files.<br />
<br />
[[File:service-login.png]]<br />
[[File:WMS_Service.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=File:Service-login.png&diff=1607File:Service-login.png2020-07-14T01:56:30Z<p>Nivin: </p>
<hr />
<div></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=Wms-service&diff=1606Wms-service2020-07-14T01:55:43Z<p>Nivin: Nivin moved page Wms-service to EEE WMS Service</p>
<hr />
<div>#REDIRECT [[EEE WMS Service]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_WMS_Service&diff=1605EEE WMS Service2020-07-14T01:55:43Z<p>Nivin: Nivin moved page Wms-service to EEE WMS Service</p>
<hr />
<div>= EEE WMS Service =<br />
<br />
The EEE WMS Service performs tasks relating to transmission of data between EEE and the 3rd party WMS. This service is installed manually - there is no installer available - but it can be updated using the normal service release installer (EEEPatch)<br />
<br />
The recommended location to install the service is beside existing EEE apps and services. E.g. C:\EEE\EEEWMSService<br />
<br />
For convenience, the executable EEEWmsService.exe can be called with the following flags to install/uninstall the service.<br />
<br />
'''EEEWmsService -i''' to install. Can also use '''-install''', or call without any parameters<br />
<br />
'''EEEWmsService -u''' to uninstall. Can also use '''-uninstall'''<br />
<br />
* Please make sure you run with Administrative privileges so you have permissions to install a service (write to registry)<br />
* When installing, you will be prompted to provide the credentials for the user that the service will run as. Ensure you specify the full user name - i.e. MACHINE\User or DOMAIN\User<br />
* Service will need standard-level of access into the EEE database so the recommended user account is EEEServices<br />
* Grant the same user account permissions to write to the install directory. This is to enable the service to write logs, and working/archive files.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_WMS_Service&diff=1604EEE WMS Service2020-07-14T01:54:48Z<p>Nivin: EEE WMS Service</p>
<hr />
<div>= EEE WMS Service =<br />
<br />
The EEE WMS Service performs tasks relating to transmission of data between EEE and the 3rd party WMS. This service is installed manually - there is no installer available - but it can be updated using the normal service release installer (EEEPatch)<br />
<br />
The recommended location to install the service is beside existing EEE apps and services. E.g. C:\EEE\EEEWMSService<br />
<br />
For convenience, the executable EEEWmsService.exe can be called with the following flags to install/uninstall the service.<br />
<br />
'''EEEWmsService -i''' to install. Can also use '''-install''', or call without any parameters<br />
<br />
'''EEEWmsService -u''' to uninstall. Can also use '''-uninstall'''<br />
<br />
* Please make sure you run with Administrative privileges so you have permissions to install a service (write to registry)<br />
* When installing, you will be prompted to provide the credentials for the user that the service will run as. Ensure you specify the full user name - i.e. MACHINE\User or DOMAIN\User<br />
* Service will need standard-level of access into the EEE database so the recommended user account is EEEServices<br />
* Grant the same user account permissions to write to the install directory. This is to enable the service to write logs, and working/archive files.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1603EEE Excel Templates: Use Updated OLEDB Driver2020-06-04T05:48:01Z<p>Nivin: /* Updated OLEDB Driver */</p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disabled. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2.<br />
<br />
In order to support our customers who still use the classic EEE Excel Templates, they are gradually being updated with support for this driver. Please refer to the EEE release notes to see which Templates have been updated.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit [https://aka.ms/downloadmsoledbsql aka.ms/downloadmsoledbsql].<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be used.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver.<br />
** 64-bit systems will require the x64 version of the driver. This contains both the 32- and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''. Then continue to use the template as per normal.<br />
<br />
[[File:Excel_Updated_OLEDB_Driver_Support.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1602EEE Excel Templates: Use Updated OLEDB Driver2020-06-04T05:47:21Z<p>Nivin: /* Updated OLEDB Driver */</p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disabled. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2.<br />
<br />
In order to support our customers who still use the classic EEE Excel Templates, they are gradually being updated with support for this driver. Please refer to the EEE release notes to see which Templates have been updated.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit [https://aka.ms/downloadmsoledbsql aka.ms/downloadmsoledbsql].<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be used.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver.<br />
** 64-bit systems will require the x64 version of the driver. This contains both the 32-bit and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''. Then continue to use the template as per normal.<br />
<br />
[[File:Excel_Updated_OLEDB_Driver_Support.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1601EEE Excel Templates: Use Updated OLEDB Driver2020-06-04T05:45:07Z<p>Nivin: /* Background */</p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disabled. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2. The EEE Excel Templates are gradually being updated with support for this driver. Please refer to the EEE release notes to see which Templates have been updated.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit [https://aka.ms/downloadmsoledbsql aka.ms/downloadmsoledbsql] to download the drivers.<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be used.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver.<br />
** 64-bit systems will require the x64 version of the driver. This contains both the 32-bit and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''. Then continue to use the template as per normal.<br />
<br />
[[File:Excel_Updated_OLEDB_Driver_Support.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1600EEE Excel Templates: Use Updated OLEDB Driver2020-06-04T05:16:59Z<p>Nivin: /* Updated OLEDB Driver */</p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disables. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2. The EEE Excel Templates are gradually being updated with support for this driver. Please refer to the EEE release notes to see which Templates have been updated.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit [https://aka.ms/downloadmsoledbsql aka.ms/downloadmsoledbsql] to download the drivers.<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be used.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver.<br />
** 64-bit systems will require the x64 version of the driver. This contains both the 32-bit and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''. Then continue to use the template as per normal.<br />
<br />
[[File:Excel_Updated_OLEDB_Driver_Support.png]]</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=File:Test.png&diff=1599File:Test.png2020-06-04T04:57:02Z<p>Nivin: </p>
<hr />
<div></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=File:Excel_Updated_OLEDB_Driver_Support.png&diff=1598File:Excel Updated OLEDB Driver Support.png2020-06-04T04:39:49Z<p>Nivin: </p>
<hr />
<div></div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1597EEE Excel Templates: Use Updated OLEDB Driver2020-06-04T04:22:10Z<p>Nivin: /* Updated OLEDB Driver */</p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disables. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2. The EEE Excel Templates are gradually being updated with support for this driver. Please refer to the EEE release notes to see which Templates have been updated.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit [https://aka.ms/downloadmsoledbsql aka.ms/downloadmsoledbsql] to download the drivers.<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be used.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver.<br />
** 64-bit systems will require the x64 version of the driver. This contains both the 32-bit and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''. Then continue to use the template as per normal.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1596EEE Excel Templates: Use Updated OLEDB Driver2020-06-04T04:21:31Z<p>Nivin: /* Updated OLEDB Driver */</p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disables. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2. The EEE Excel Templates are gradually being updated with support for this driver. Please refer to the EEE release notes to see which Templates have been updated with this support.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit [https://aka.ms/downloadmsoledbsql aka.ms/downloadmsoledbsql] to download the drivers.<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be used.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver.<br />
** 64-bit systems will require the x64 version of the driver. This contains both the 32-bit and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''. Then continue to use the template as per normal.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1595EEE Excel Templates: Use Updated OLEDB Driver2020-06-04T04:18:07Z<p>Nivin: /* Updated OLEDB Driver */</p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disables. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2. The EEE Excel Templates are gradually being updated with support for this driver. Please refer to the EEE release notes to see which Templates have been updated with this support.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit https://aka.ms/downloadmsoledbsql to download the drivers.<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be run.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver<br />
** 64-bit systems will require the x64 version of the driver. This contains both the 32-bit and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''. Then continue to use the template as per normal.</div>Nivinhttps://theoracle.magentaretail.com.au/index.php?title=EEE_Excel_Templates:_Use_Updated_OLEDB_Driver&diff=1594EEE Excel Templates: Use Updated OLEDB Driver2020-06-04T04:17:07Z<p>Nivin: </p>
<hr />
<div>== Background ==<br />
EEE's classic Excel templates use the OLE DB Provider for SQL Server to establish connections with the EEE database. As of EEE v1.86, all the classic templates rely on the OLEDB driver in the Microsoft ActiveX Data Objects 2.8 Library that ships with Windows. This version of the OLEDB driver relies on TLS 1.0 to establish the connection.<br />
<br />
As TLS 1.0 is being deprecated by the industry, software and policies will require TLS1.0 connections to be disables. Once this happens, this driver can no longer be used to connect to the EEE database.<br />
<br />
== Recommendations ==<br />
=== API-based Templates ===<br />
<br />
Since v1.84, EEE has started the move towards an API-based approach for the Excel Templates. This means that a REST API sits at a EEE Head Office server which the Templates will then communicate with over HTTPS. This has the advantage of the latest security benefits, and customers have the option of making the API available over the internet which means the templates can be used without the need for a VPN. This is the recommended method going forward.<br />
<br />
Most of the standard EEE Excel Templates are available as API-based versions. Please contact Magenta Retail Support if you'd like to implement the API-based templates in your environment.<br />
<br />
=== Updated OLEDB Driver ===<br />
<br />
Microsoft has recently resurrected previously deprecated OLEDB drivers for SQL server and has made available a new version that supports TLS1.2. The EEE Excel Templates are gradually being updated with support for this driver. Please refer to the EEE release notes to see which Templates have been updated with this support.<br />
<br />
Note that the updated driver is not shipped with Windows and is available as a separate download from Microsoft. Please visit https://aka.ms/downloadmsoledbsql to download the drivers.<br />
<br />
* The driver needs to be installed on each client machine from where the EEE Excel Templates will be run.<br />
* Please download and install the version of the driver based on your operating system architecture.<br />
** 32-bit systems will require the x86 version of the driver<br />
** 64-bit systems will require the x64 version of the driver. That this contains both the 32-bit and 64-bit drivers.<br />
<br />
Once the correct driver is downloaded and installed, open a compatible EEE Excel Template, and under the Settings sheet, specify the Driver as '''MSOLEDBSQL'''</div>Nivin