Syteline is a powerful enterprise tool that can be used to great advantage. However, even valuable tools like Syteline have their limitations. While all basic administrative and operational functions can be performed though the Syteline interface, when used in conjunction with a Microsoft SQL Server, even more highly beneficial results are easily accomplished.
When tuned to work together, the combination of Syteline and a Microsoft SQL Server form a powerful duo. Better performance is achieved through more capability and higher efficiency.
Optimized Syteline Data Retrieval
Data retrieval can be streamlined using SQL along with Syteline. By default, Syteline displays the first 200 rows of a form. It can be customized to show more, but the more rows displayed the longer it takes to retrieve them. Other factors like the total number of transactions and the number of users making queries also affect retrieval time.
Using Microsoft SQL Server to carry out regular database tasks, data retrieval becomes more efficient. By de-fragmenting the indexes, queries run faster and archiving lessens the number of transactions being processed. Running scripts to check for idle or deadlocked user queries frees up memory.
Robust Syteline Data Management
Certain purged data, like material and accounting transactions, can be deleted from history because the data can be found in other forms, such as purchase orders or the general ledger. The preservation of this data, however, is critical, but letting it accumulate consumes space that could be allotted for new transactions.
Applying proper retention periods, a Microsoft SQL Server can play an important role in the archiving of historical data. Plus, it allows regular, automatic backups of the database, and it runs stored procedures at scheduled times of the day.
Gain More Syteline Customization
Syteline’s data and process flow is based on generalized standard business practices. Most organizations will have specific practices and processes that vary from Syteline’s application design. Customization of the user interface, however, is limited to superficial modifications, additional fields, and shallow scripts.
Stored procedures, triggers, and functions accessible through the Microsoft SQL Server allow for more powerful customization. However, be sure to verify that customizations will not breach any service contracts that may be in place.
Improved Administrative Transparency
The form editing functions in Syteline were structured to suit ordinary users and programmers. The object-oriented design is meant to be simple and user-friendly.
However, the gains in simplicity can at times mean a sacrifice in higher-level administrative functions. Â Database administrators can have difficulty monitoring where data came from and where it went. With a Microsoft SQL Server, you can check the scripts of a stored procedure, the functions initiated by a trigger, and all the triggers assigned to a table. Data transparency does not have to be forfeited at the administrative level.
Create Highly Tailored Reports
Syteline’s Crystal Reports is used to customize printouts and periodical reports, however, they are not practical for ad hoc reports because of the effort required to set the parameters and create the appearance. Copying and pasting the collection grid data in a filtered form to Excel only works for reports that are limited to one table.
By executing a SQL script, you can retrieve the data you need and then save it in Excel. Plus, you can link to as many tables as needed. Now you have flexibility to create professionally formatted reports as well as charts and graphs to display the data.
Get Faster Report Retrieval
Long reports can be a problem with Syteline since data is transferred through several different channels to achieve the end result. When a user creates the parameters for a report, the request is first passed to the Utility Manager and then to Crystal Reports. Finally, the data is retrieved from the Microsoft SQL Server – then it has to move back through the same channels again before becoming the desired output report.
For long reports, it’s better to go directly to the source to create and run the query. By avoiding having to transfer of large amounts of data through several layers of processing, longer reports are created more efficiently. Virtual and page memory is saved as well.
The Ultimate Goal: Happy Customers and Efficient Operations
These are just a few ways that tuning Syteline to work in conjunction with a Microsoft SQL Server creates higher performance. However, the advantage of coordinating these powerful tools doesn’t stop there. For example, you can set up a replication system, monitor query locks and blocks, and even use it as a medium to retrieve data using different software applications.
When your business can use information more effectively, production runs smoothly and on schedule – resulting in higher throughput and on-time delivery.
If you are not getting the most out of the powerful pairing of Syteline and a Microsoft SQL Server, you may want to get help from an expert. Onepax specializes in helping enterprises get the most out of their investment in Syteline, including tuning Syteline with the Microsoft SQL Server to achieve positive results.
September 4, 2011 
