MS SQL Technology Business Software Primer for MS SQL ...

By Sheldon Needle

Evolution of Construction Software Platforms

Construction software was first developed for non mainframe hardware in the 1970?s.? At that time programs were written in cobol, business basic, or a programming language? specific to the hardware manufacturer. There were compiled languages that translated code as they ran on the computer. These languages ran in a Unix (or Unix like) environment on mini computers, then micro computers (now called PCs) in what was called a ?dumb terminal? environment. All program code resided on the mainframe?s hard drive and the terminal simply sent instructions and then received data from the hard disk ?server.?? What we call operating systems were developed by the hardware manufacturer and were specific to that hardware.

In the 1980s, construction software vendors were able to take advantage of newer operating systems like MS DOS (which originally only ran on the IBM PC). MS DOS became the standard operating system for all PCs ?and allowed vendor software to become hardware independent.. This simplified hardware and software purchases for consumers except those who insisted on Apple or other closed systems.

Network software, which allowed individual PCs to share files and programs, was introduced in 1984 but was unreliable at first. Several companies competed in this arena including Novell, IBM and Microsoft.

New databases evolved in the 1980s such as Pervasive SQL, Foxpro, Filemaker and others.? These relational databases represented a great leap forward from flat file data bases which relied on many separate tables to function. Visual Basic and C++?? were the standard programming languages in the 1990s.

In the early to middle 1990?s, Microsoft introduced MS SQL Server which was originally an offshoot of Sybase SQL.? Microsoft developed it into the most reliable and powerful PC based database? on the market. A software vendor who wants to be compatible with the latest Microsoft technology should run under the MS SQL Server database.

But bear in mind, SQL is not the same for everyone. There are systems which employ a SQL database but are not native SQL meaning that data is read by SQL for purposes of using SQL Query language for ?its stability and speed. But to use all the Microsoft toolset for reporting, query, import and user interface functions requires a native SQL database and use of the Microsoft Visual Basic .NET programming language.

What are the MS SQL Server Components?

SQL Server Reporting Services (SSRS)

SQL Server Reporting Services (SSRS) is a server-based report generation software system from Microsoft.? This component does not require a programmer to build reports. This ease of use is achieved because the Report Builder and the database tables are synchronized under one common system.

SSRS has support for building and extending management reporting where end users have tools to build their own queries and dashboard reports.? In addition, application programs can embed necessary reporting with Reporting Services saving the user from having to create SQL queries.

Reporting Services can supplant the need for Crystal Reports which is the defacto standard for custom reporting for mid-market products. But many users are not able to master Crystal Report for anything beyond very simple reports.

SQL Server Integration Services (SSIS)

SQL Server Integration Services (SSIS) is a component of the Microsoft SQL Server database software that can be used to perform a broad range of data migration tasks.? SSIS has the ability to take data from any external system text file by using a built in mapping function that can be modified or extended to handle any external program data.

Examples of using SSIS might be for field people to enter their time and materials usage for a contract and have it feed into a payroll system or to import time and materials data entered to Excel. Another example would be for a contractor to take data from a weigh scale system and import it ?to their ERP software for billing the customer.

Visual Basic .NET (pronounced dot net)

Visual Basic .NET is an object-oriented programming language that can be viewed as an evolution of the classic Visual Basic (VB).? .NET greatly extends the power of users to expand and enhance the user interface along with the ability to interact with the system and configure various capabilities. These capabilities used to require heavy duty programming. Examples include creating user tables and linking them to standard reporting functions, changing field labeling, adding user defined fields, data filtering, grouping menu items and data, and removing columns from queries by users. It also facilitates configuring the user interface to create user-based menu workflows.

Cloud computing

With a true cloud application all data and programs reside with the software vendor and a PC is used to run the applications over? the web. All that is necessary to run any function of the program is a PC with an internet connection.

A hosted cloud solution is different. The program and data resides on a dedicated remote host computer.? Remote PC connections to the host computer is done over the internet using either a Citrix or Terminal Server which is vendor-hosted. This eliminates the need for a local network installation and all the hardware and technical support to keep it running smoothly.

Some construction vendors have functional applications that are web-based, while other applications require the traditional client server installation. This client server installation can be self-hosted (server is on premise) or vendor-hosted (cloud).? Thus, depending on what?s needed, some users will access data from their locally installed software and others will use the internet (web-based or cloud users).? Web-based applications offer a user experience based on a web entry screen, while a hosted (either self or cloud) solution offers WinForm (based on .NET Framework) entry screen.? Some specific applications, e.g. construction project management software, may run entirely over the web. Even though an integrated solution is preferable, provisions can made for these applications to be linked and integrated as needed (especially using SSIS).

Conclusion
In light of this historical review, you may be wondering what this means to you as a software buyer. Should you only evaluate solutions using a SQL database and .Net platform? Not necessarily. Older technologies are alive and well in the construction software space and continue to adequately serve the market because many contracting firms haven?t yet realized the need for the most cutting edge developments. But some construction software vendors have already begun looking to the future for development inspiration, choosing to migrate their applications to a .Net platform and cloud computing environment. The big take-away here is this: when evaluating new construction software, be sure to least consider the solution?s current technology platform while gaining an understanding of the vendor?s plans for future development.

quadrantid meteor shower osu football osu football oklahoma state santonio holmes raheem morris winter classic