So, in my organization, SQL Server is used as the back end. This means all the work related to storing the date (e.g. using tables), retrieving the data (e.g. using procedures and functions provided by SQL Server) and manipulating the data (e.g. necessary update and alter statements) are all tasks performed by SQL Server and some helpful programming language.
It is being used not just by any one department, but by the whole organization. Proper functioning of a website highly relies on its back end, so SQL Server is solving this business problem for us, in addition to generating visual reports using services like SSIS and SSRS, which are provided by SQL Server.
- It can store large amounts of data. Moreover, it doesn't just store the data, but performs important operations with it. Things like backup, restore, etc., are all handled pretty well by SQL Server.
- It is equipped with different tools like SQL Profiler (for visualizing what's going on), SQL Tuning Advisor (for better suggestion of indexes, etc.) and also third party tools like SQL Search and SQL Code Guard. This really makes life easier for us.
- SQL Server integrates to almost all the programming languages that work as front end for SQL Server, such as asp.net, C++, etc.
- Services provided by SQL Server do solve some high business level problems using SSIS and SSRS.
- Support and service from a company like Microsoft is another big advantage.
- The above mentioned points are all strengths of SQL Server, as this one RDBMS does a lot of jobs, and with relative ease and efficiency compared to any other software in this sector.
- In terms of resource utilization, there is room for improvement for SQL Server, so that it can cost less CPU usage.
- There are lot of third party services like SQL Search and SQL Code Guard. Why is there a need for these if SQL itself can implement these necessary functionalities inbuilt?
Current use cases are order management, vendor performance metric building and maintenance, supply/demand views.
- Group and count data
- Join multiple data sets together across entire organization rather than a single site view
- Monitor exception cases at scale
- Intellisense won’t turn back on
- Enhance object explorer to help find tables previously unknown
- Easier note taking
- Support is a major factor. Day-to-day functionality is reliable, but for those times when there are issues support is available.
- Security is key, and Microsoft SQL Server has clearly put this concern in its design.
- Perhaps not a strength of SQL Server itself, but the pool of professionals with SQL Server experience ensures the ability for growth.
- User setup should be allowed to be copied from other users
- It's fairly quick to manipulate large sets of data
- Quick and easy to learn
- Cost efficient
- Implement features to process unstructured data easier
- Increase performance speed
- Add multiple results table in the same window
- SQL Server is really good at working with large structured datasets
- Great customer support and online resources available
- One of the most intuitive and easy to learn a programming language for data analysts
- Add more built-in functions
- Having the ability to work with unstructured data would be useful
- Having an in build data visualization would also be very helpful
- it has a lot of security feature, no one can access if they have no credentials.
- easy to use and maintain the database
- very flexible and easy to install and for new users it very easy to learn and implement.
- it has little bit performance issue
- output window panel is single if we run multiple select commands it shows all results in one after that so that is more clumsy
- it goes hang in low System RAM configurations.
- Faster in performance.
- The concept of CTE(Common table expressions) is really great.
- Temp tables works well and easy to use.
- We need to always use BEGIN TRAN to start a transaction which adds an additional step each time.
- Runs on LINUX
- Job and Task schedule and Email Notification
- Distribution Transaction
- RDMS Database backend for Web Site Application
- RDMS Database backend for Reporting Services
- RMS Database backend for ERP, CRM etc Software Tool Project
- If configured correctly with the proper hardware, SQL Server can be incredibly powerful, delivering millions of data points in the blink of an eye
- If you're just starting with relational databases, you would probably be fine with opting for an open source solution. However, if you need a solution that can handle an enormous number of requests and return results with considerable speed, SQL is worth researching to see if it fits your needs.
- Managing database using SQL Server Management studio provides very good flexibility
- There isn't as much that I dislike with SQL Server. It will be good to have features where we have fine grain control over internal things. For example, it would have been a good feature to have historical tracking of the metrics as opposed to setting up custom metrics. Overall SQL Server made my life easy to manage a lot of databases and ease of use while migration projects.
- The database is the target of many attacks from it's SA account, this must come disabled by default and just after the instalation, some of 30 seconds, the attacks start, with many requests per second, it needs to improve the firewall to prevent these attacks, or put the SQL Server inside of a VPN and local network to avoid these attacks.
- It requires knowledge and in-depth technical skills to make complex processes truly performing, especially if we are in very complex infrastructures
- Integration of the R programming language and its eco-system.
- Transact-SQL is quite expressive and allows implementing complex application logic.
- MS Excel can be used as front-end.
- OLAP queries on non-aggregated POS data can be very slow. Hence, it is required to persist aggregated views on the data.
- Debugging R-Code is not convenient.
- Versioning of SQL procedures.
MS SQL Server is an appropriate choice if the data foundation is not very large. The integrated R support allows you to deploy analytical applications (e.g. machine learning models) directly in the database.
However, if the data foundation is very large or real-time queries SQL Server reaches its limits and might not be the right choice.
Microsoft SQL Server Review: "SQL server pivot function and automatic data table name pop up are awesome"
- Tables in database automatically pop up in writing SQL, makes it easier to navigate
- Has pivot functionality, so I can query pivot tables instead of making them in Excel
- Great connection to Excel in terms of exporting queries
- Windows set up time takes longer than other DB software
- Does not allow numbers in "group by" clause, users need to write the column names explicitly
- SSMS provides useful tools such as the database tuning advisor - providing recommendations for missing indexes.
- SSMS provides useful tools such as the SQL Profiler - Providing in-depth trace files of queries currently executing in your database.
- SSMS provides useful tools such as the Activity Monitor allowing you to find expensive queries, resource waits, processes, and I/O.
- Would prefer more built in queries for DB optimization rather than having to find scripts on the internet.
It allows me to write efficient, fast queries that export nicely to Excel.
- Error logging and indicators
- Colors keywords
- Allows for easy formatting
- Allows for multiple tabs
- Allows for multiple subqueries
- Needs more specific error messages
- Sometimes it seems "buggy" with the predictive text
- Needs an in application help resource that is easier to understand
It smoothly incorporates subqueries that allow large pieces of data to be joined together without bogging down resources. It can also easily be used in other applications.
For fancy visual effects or pictures it is not well suited. It is a very "bare bones" application.
- Strengths of Microsoft SQL Server creating an ease even for a newcomer who just knows basics of the database. Creates an easy adoption for any other database programmer who is working on another platform (Oracle, MySQL etc.) to get migrated over to Microsoft SQL server version with minimal efforts.
- Primarily when the application data to be hosted is very less there is less complexity involved in the creation of databases, securing access to a database table, schema and role wise. Much of the functionality of DML, DDL operations can be achieved through user interface called SQL management studio - best tool for any programmer to senior DBA.
- SQL Server integration services, analysis services, and reporting services which are included in BI pack will definitely help enterprise customers save a lot of revenue spent on the additional BI stack Reporting products like Cognos, Crystal Reports, Informatica etc.
- SQL Server has certain limitations in terms of functionality of SQL management studio. But there are a lot of third party programming tools which are available in the market which is powerful enough to overcome these limitations.
- Database comparison tool - Lack of a tool where you can compare entities of database like tables, views, indexes between 2 databases of the same application (like comparing production to stage sites).
- Version control management system (to maintain different versions of code checked in / checked out). Had to be driven using 3rd party tools.
- SQL replication - coverage for all 3rd party databases has been withdrawn in recent editions which are a limitation especially while migrating from previous SQL server editions. This is a gray area of SQL Server often challenged to due to limitations of integration to 3rd party software's like Oracle, MySQL etc.
- Performance management tools - even though there are built-in reports like "Activity Monitor", they are existing to monitor the performance of SQL Server. It's better to have an individual console to connect to SQL server instead of depending on Windows or other 3rd party tools like APEX SQL console, IDERA tool to monitor SQL server performance.
- Automated jobs on schedule
- Easy integration with the Com Components (Assemblies Integration)
- History of the jobs executed, gives the failure and the success email alerts after executing
- Database file partition for the large databases
- Log Shipping is a very easy to implement and very useful feature
- Better GUI for inbuilt functionalities. For example, I would like to have the Database email services have a good interactive GUI instead of the current one.
- It would be nice to have a Start Ups Guide for SQL Server which explains all the basic and necessary services needed for a start up company to use SQL Server.
- In a single package, you get a data base/OLAP/reporting.
- Ease in using the best documentation and books are available for anyone to start working on it and use tons of features.
- Columnstore indexes need to be improved further even after many limitations were removed in SQL 2016.
- Pricing of the SQL Server license should be made more simple to be understand easily.
- Backing up databases both full and differential as well as transaction logs so data recovery is simple.
- Database cleanup and maintenance tools that can be scheduled to keep the database running at optimal performance.
- The performance monitor allows you to track query performance so you can maintain the best user experience and tune the server for optimal usage.
- A better way to remotely connect to the database to maintain and review current transactions is needed.
- SSRS report designer needs better tools to build the reports you need. Too many workarounds due to limitations in SSRS.
- Logs need to be less cryptic and more meaningful at times so that diagnosing problems can be done quicker.
- SQL Server is a whole package that usually connects well with other Microsoft products.
- SQL Server has a large community of users for tips and advice on SQL programming.
- SQL Server works fairly seamlessly with Power BI, Power Query.
- One glaring example is importing spreadsheets through SSIS, SQL Server only seems to sample the first few rows and generates errors if larger text cells are further down the rows.
- SQL Server tends to be a bit more touchy with database object names than MySQL.
- The good - SQL Server has a lot of ways to get at the data, the bad - finding particular settings is often buried in dialogs.
- Fast and efficient compression on backups. Typically we see about a 65% reduction in size compared to the data file.
- It just "works". We say this very little in IT but it really does just work. Almost every enterprise application out there works with it and the downtime is very minimal.
- You have the opportunity to cluster servers. You can easily create a cluster of SQL servers to share resources instead of buying all new equipment and scattering the database footprint.
- The patching has sometimes been an issue for us. It either doesn't work or the process isn't explained well for the different SQL instances on one engine.
- I wish they would design a way to allow SQL backups to go somewhere other than a local drive. A UNC path would be best. This would allow us to rotate off the backups to a longer term storage device.
- It takes up a huge amount of memory and space on a server.
- There is no benefit to running it in VMWare. We typically find that servers run better in VMWare for our use cases but SQL seems to run just the same and you don't save on licensing so there really is no benefit.
- Handle large amounts of data. SQL can process thousands of rows of data in a pinch when given the correct hardware to utilize. SQL likes memory and it will utilize it very efficiently when given the chance.
- SQL provides at least 2 methods to do everything. You can write simple SQL query scripts or you can use the built-in GUI (which coincidentally just runs SQL scripts behind the scenes).
- Allows for jobs to be setup that can do simple tasks such as database backups, database restores, export and import data and even send out notifications when SQL Server encounters a problem.
- Integrates with a lot of other programs and software. Microsoft allows SQL Server to integrate with Visual Studio and you can utilize SQL tools with SSIS, SSMS, SSAS, and SSRS to get deep into integration tools, Analyzing data, and reporting on various data in each database. You can also integrate with third party tools such as the suite of products from RedGate.
- Speed up installation times. A manual installation of SQL server can take up a good chunk of time. You can be forced to go through an installation wizard screen by screen and it can take a lot of time waiting for each screen to load.
- Allow for easier integration with GUI's. SQL has the capability to use a visual query builder where you can drag and drop fields, tables, etc to build a query but it is not as user friendly as you would imagine.
- Make the permissions more stream lined. Users can have permissions to a SQL Server but not a particular database and trying to find the right spot to add the correct permissions can be painful for someone who is new to SQL Admin work.
- SQL Server handles a relational database very well. The fundamental logic for Extract, Transform and Load (ETL) hasn't changed much for a long time, so there is no learning curve if you upgrade from older versions to new ones.
- One of the strong advantages of using SQL Server is its better compatibility with Microsoft product suites. Choosing Microsoft SQL server is the first choice if your organization relies on other Microsoft products.
- It is very stable, fast, affordable, and extremely popular. There is an easy learning curve to acquire SQL Server skills. Microsoft SQL Server Management Studio is very graphical and requires very little programming to achieve basic tasks.
- SQL Server is only operable on the Windows platform. It should support the Unix platform too.
- There are a few object types missing in SQL Server, e.g. no packages (collection of procedures and functions), no "before" event triggers.
- SQL Server doesn't support partitioning.
- Data accessing via Excel or Access is very easy.
- Reporting services are a really good example to present and analyze the data to management.
- We do have an analytics team which does a lot of data modeling and also uses lots of integration services.
- Definitely room for improvement in SQL server reporting services.
- Missing the functionality to purge/archive/delete the reports from the server. We have to do it one at a time.
- Great catalog of online support
- Intuitive interface
- Very useful functions and methods not available on other platforms
- SQL Server Integration Services, in my experience, is very buggy and crashes often. Needs improvement
- I wish it was easier to retrieve current instance settings and configurations without going through much of the installation process again
- Compatibility with Power BI suite is not intuitive and is less than robust
Almost every department in our company uses SQL Server in some sense, and we find that it is very easy to develop both our software and internal applications on the SQL Server platform. The tight integration with .NET tools and our staff expertise means that we can quickly and easily work on the platform.
The extent of our use of the comprehensive platform is limited. We primarily use it as a relational database, with some of the SSIS/SSAS features used by various departments. Our sales and marketing groups certainly do like the SSAS cubes as they get quick information on large amounts of aggregated data.
- Administration is fairly easy. A SQL Server can be setup quickly and run without much management from a DBA. Some work is needed to configure the instances, but the platform tends to run very smoothly for us. Backups, index maintenance, and security are smooth and easy to set up, and with the GUI, we can make adjustments quickly, while still saving the underlying code.
- Development is very easy for our staff of .NET professionals. The integration between .NET in Visual Studio and SQL Server means that there is little time spent working out how to build an application and we can focus on adding business value. Our work with Oracle and MySQL has required a bit more effort to understand the APIs.
- Reliable. We use all versions of SQL Server, and we find that they are very stable. The systems backing SQLServerCentral, for example, are rebooted about once a year, usually to apply some security patches from Microsoft. We tend to stick to Service Packs as a means of updating our systems
- Value. We receive a good amount of value for our use of SQL Server for the price we pay. We might pay less in initial costs for MySQL, but time loss, support costs to understand how the system works, and potential administrative issues may overwhelm that. It's a hard choice to make, but we do find our SQL Server costs to be reasonable.
- One of the weaknesses of SQL Server is the lack of tooling in places. That sounds strange as Microsoft has been known for easy to use GUI tools, but a number of features in the last 4-5 versions of SQL Server (Service Broken, replication, Extended Events, and more) haven't received much help in the tooling areas.
- Scalability. While SQL Server scales up nicely, and new hardware platforms have dramatically increased the power of a single instance, there are still issues with larger scale applications built on SQL Server that might require more than one instance. Or that could benefit from additional hardware machines of the same size. SQL Server hasn't scaled out well across machines.
- Licensing. While SQL Server is reasonably priced (to me), it is still expensive as cores grow and there are limits to the small scales of some applications. The complexity of licensing also means that it becomes complex to manage this across time, as well as more expensive than I would like.
- Tuning. While there are a wealth of ways to tune systems, it feels more complex inside of SQL Server at times than it needs to be, especially for less experienced users. The platform should do more to help users understand where issues occur and give them guidance. I think the SQL Server 2016 Query Store will help here.
- Maturity of some features. I think that some of the features have been a bit neglected, apart from tooling, in the last few versions. It seems like Spatial data, the Availability Groups, Service Broker, and more haven't gotten enough work to mature them to be more useful and helpful features.
However on balance, if you are not approaching edges of a workload scenario, Microsoft SQL Server is the best choice, in my opinion, for a platform.
Microsoft SQL Server Scorecard Summary
About Microsoft SQL Server
Microsoft SQL Server Integrations
Microsoft SQL Server Technical Details