Overall Satisfaction with Microsoft SQL Server
We use Microsoft SQL Server as the DB option for the commercial back-office modules of our MLFF (Multi-Lane - Free Flow) Tolling solution. All the commercial back-office (from Customer registration to involvement and payment handling) relies on Microsoft SQL Server databases. Other vital components of the entire solution, like Security and Vehicle Management, and the Reporting environment also utilize Microsoft SQL Server.
- Microsoft SQL Server is simple to install and configure.
- Many advanced options like Compression and Partitioning are available with no extra cost, thus reducing the overall TCO.
- Partitioning does not provide as many options as Oracle (like Foreign Key partitioning, list partitions, hash partitioning and sub partitions)
- The default READ COMMITED isolation level block readers, so it is important to use the READ_COMMITTED_SNAPSHOT option, that should be default right now...
- Customers know and trust the product, so it is easier to implement our solutions.
- Licence cost are usually lower than other products if all advanced options are used.
We use both Oracle and Microsoft SQL Server for our entire product line, using the best features of each of them to solve different business requirements and technical challenges. Microsoft SQL Server is simpler to install and use, but lacks some advanced features and has fewer configuration options than Oracle, so we use each of them based on each module requirements.
Do you think Microsoft SQL Server delivers good value for the price?
Yes
Are you happy with Microsoft SQL Server's feature set?
Yes
Did Microsoft SQL Server live up to sales and marketing promises?
Yes
Did implementation of Microsoft SQL Server go as expected?
Yes
Would you buy Microsoft SQL Server again?
Yes
Using Microsoft SQL Server
100 - About 70% of our Multi-Lane Free-Flow (MLFF) tolling software, including all of the commercial back offices, is designed on the Microsoft SQL Server database engine. Software Architects and Developers design and create the data model and develop data processing procedures (like invoicing, notifications) while testers use SQL Server to validate the features of our system.
3 - Since we do not host real production data, we try to keep our environments as simple as possible. We have source code repositories where all data model and stored code (views, procedures, functions, etc.) are kept. We keep a simple backup policy to be able to recover for accidental data loss on testing and customer acceptance environments.
- It is a central piece of software in our MLFF product.
- Besides using Microsoft SQL Server for our product, many support tasks (like customers legacy systems migration mapping information) are stored on Microsoft SQL Server databases.
Evaluating Microsoft SQL Server and Competitors
- Price
- Product Features
- Product Usability
- Prior Experience with the Product
We chose Microsoft SQL Server as a good cost/feature product, that provides a robust backbone to our Multi-Lane Free Flow software product. The ability to use features like compression and partitioning with no extra cost made Microsoft SQL Server a good choice.
Microsoft SQL Server Implementation
- Implemented in-house
Change management was minimal - As a software center we have been using SQL Server for many years, so there were no actual issues implementing the latest versions of the product.
Using Microsoft SQL Server
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Convenient Feel confident using Familiar | None |
- SQL dialect is simple to use and usually very easy to understand
- Installation is really simple