SQL Stored Procedures for Stone Edge Enterprise Edition

Contents of this Topic: Show

Overview

The SEOM Enterprise Edition uses several SQL scripts to obtain data for the purpose of auto-generating purchase orders that are sent to a supplier or suppliers to replenish a merchant's inventory. The scripts are located in a folder named SQL in the program installation directory, which is typically c:\StoneEdge.

These scripts become stored procedures in SEOM's SQL store data file as part of upgrading the application, or when converting an MS Access store file to an SQL database. If the scripts are not stored successfully at that time due to runtime errors or insufficient authority but the remainder of the program installation or conversion completes successfully, the user will need to manually install the scripts as stored procedures.

The individual performing this operation should be assigned the db_owner role on the SEOM database, but it is imperative that the database Owner is an SQL "sysadmin" Logon ID, rather than a domain Login ID.

How to Manually Install the SQL Server Scripts as Stored Procedures

  1. Open the SQL Server Management Studio (SSMS) software, which normally resides on a server in the Local Area Network (LAN).

Figure 1: SQL Server Management Studio - Object Explorer pane

  1. Select the SEOM store data file from the expanded list of databases. In this example, the database is called OM Data File, which is shown as selected in the figure below.

Figure 2: SQL Server Management Studio - expanded list of databases

  1. When the appropriate database is selected, go to File > Open > File... and navigate to the location of the SEOM SQL scripts. The scripts are in a sub-folder named SQL in the program installation directory, which is typically c:\StoneEdge.

  1. Open one of the scripts and click !Execute to run the script.

In this example, the GetSingleUnitSKU script has been opened and executed in the database, OM Data File.

If the outcome is successful, the response, "Command Executed", is seen at the bottom of the screen.

Figure 5: SQL Server Management Studio - successful completion of creating the stored procedure

If this process is run when the scripts are already installed, an error message is displayed instead, as shown in the figure below.

  1. Repeat steps 3 & 4, for each of the other remaining scripts in the SQL folder.   

  2. When all of the scripts have been added as stored procedures in the selected database, exit the SSMS software by clicking X in the upper right-hand corner or selecting File > Close.

 

Created: 3/18/11

Revised: 12/4/14

Published: 04/13/16