SQL Server Reviews

SQL Server is our main database solution. For example, we use it for our contact center software.

In Poland, SQL Server is the most popular database engine, and overall, our customers like it.

For small-scale businesses, Microsoft could improve by removing some limits in SQL Express.

In the future, it would be a benefit to have web-based management capabilities.

I have been using this solution for approximately five years.

Five years ago there were some stability issues but in the current version, the stability is good.

The solution is scalable.

We use the documentation provided online by Microsoft that has been helpful. We do not need to use technical support because we have many high-level technical staff who know how to use the solution.

The initial setup is very simple.

For smaller companies, they find this solution expensive.

I rate SQL Server an eight out of ten.

The database is primarily used as back-end storage.

As an engineer working for multiple organisations, MS SQL has proven stability and operational power.

The additional tools, like SSIS and reporting services, make this solution useful.

Improvements to the indexing, columnstore indexing, and high availability groups are good improvements for future versions.

MS SQL is constantly improving their products. New options, such as managing with PowerShell, are good improvements.

We primarily use SQL Server for reporting.

I love SQL Server's Common Table Expression. In addition to that, I like its lead and lag functions. That helped us reduce a lot of code when comparing rows in SQL Server.

The way SQL Server pivots data could be improved. For example, I would like built-in comma-separated pivot and unpivot functions. 

I've been working with SQL Server for the past seven years. 

SQL Server is stable.

SQL Server is scalable. I can't say if we'll increase usage in the future because I'm only working here as an analyst. It's a company decision. If necessary, then I can make a recommendation. I can go for that if the client wants, so it depends entirely on our client. If the client wants Oracle instead of Microsoft, I don't have an option.

I never contacted Microsoft support about SQL Server, but I have called about Power BI one or two times. It was great support.

I rate SQL Server eight out of 10. 

We manage backups for our customers, so we are not developers and we don't use SQL to provide a service. We are a managed service provider focused more on IT support and SQL configuration. So we don't use SQL as a product by ourselves. Instead, we provide instructions for how to back up SQL and do maintenance on it for our customers who need a SQL server for their CRM and ERP products. Their products need to have a SQL server to use in order to use their services. So we handle the maintenance for our customers.

Microsoft has a very broad landscape of products that they provide—almost everything that you need. SQL Server is widely used and it's simple. You cannot do without Microsoft if you want to manage IT for a business customer. And even if you don't like Microsoft, you should know how to use it because just about every customer uses Microsoft, so you have to use it. So it doesn't matter if I like it. It's everywhere, so you have to know how to use it.

I've been using Microsoft SQL Server for 25 years now.

We are a reseller of Microsoft. We also signed the SPLA agreement, which stands for Services Provider License Agreement. So we are able to use Microsoft products in our data center in order to provide cloud services to our customers.

I rate SQL Server nine out of 10.

It is a typical database solution, and it is working well so far. It is easy to use, and it is also very common and popular, which makes it easy to find a support partner.

It will be very useful to have high-level database monitoring. It should also have built-in business intelligence reporting.

I have been using this solution for more than ten years.

We have around approximately 600 or 700 users of this solution. Currently, everybody is using this solution, and we don't have a plan to increase its usage.

We don't have a direct connection with Microsoft support. We have a support partner who is in contact with the official Microsoft support.

Its initial setup is easy.

I would recommend this solution. I would rate SQL Server an eight out of ten.

We use SQL Server for database integration as we sometimes use queries to take information from the database. For example, if I need a couple of information that is archived or not indexed, I will inform the SQL Server team to help.

I use the menu on the management view credit section to get information from the database.

I have been using SQL Server for eight to ten years, but I still check Google for things that aren't clear to me. For service delivery, we use on-premises solutions for our customers.

We don't use SQL Server as our primary product. Our focus is on safe customer SQL admin as we don't want problems with customer data in our system.

I think we consulted once for support in the active directory. We requested the support of Integration Engineers for installation, and their service was very good. However, in the last eight years, we have also used Microsoft support with satisfaction.

For the initial installation process, I did an installation for database testing using SQL Server Express. Sometimes, the trials for the samplers are not allowing the SQL Server Express. So, when I was doing the installation, I just selected database management because it isn't the default and it has helped me not to fill out the same details for future use.

I cannot answer that question concerning pricing and licensing because I'm just a technical staff member. However, we are just a customer of Microsoft and some of our clients say SQL Server is very high in price.

SQL Server is a very good product and we use Microsoft SQL Server software that runs on Windows as most of our clients make use of the Windows operating system. But I don't have a hundred percent trust in Microsoft products. Why am I saying that? This is not a security issue. I am just... We are hitting this kind of issue because, as you know, Windows servers sometimes get corrupted or we need to restart them.

The customer's MES system  use it.  The database system desgin as always on architecture.

Like Data guard in Oracle , always on contain double data and sync data by using transactions store in transaction log

It is easy to establish, and the license price is lower than that of Oracle.  

Otherwise, our customer could can replace primary databases from Oracle into MSSQL AG

Base on  windows cluster,  the always on no needs complicated config process.

Just click and click following  GUI interface.

table partition options,  that is very useful to separate unnecessary cost. 

For legacy data,  we can do partition swith out and store into flat files or old tables.

When it necessary, we can switch in back.

Horizontal partitioning.  

In that case,  cold , warm and hot data can be distributed into different database not only table partition located on different FGs .

Sometimes , when windows server suddently failed, the database still can be turn on when DB server started.

When do "sp_rename" or "table rebuild" , the cluster index or non-cluster index no needs to rebuild at same time

Customer always comes out many questions

I have no choice. our customer choose MS SQL 

 initial setup straightforward

ordinary level

database administrator

Migration local database into cloud

No, I  have to accepted it 

subpartition is necessary

The most valuable feature is the easy installation. The user just needs to know how to read.

The SQL Server is helping us with the most feared corporate problem: Excel spreadsheets. The individual user can perform an integration and share the same results with others without the necessity to "share" the file. This reduces the data traffic on my company network.

Table partition and memory management. The performance could be better.

I have used it for more than 10 years.

The SQL Server has a big issue when some systems use Java as a primary software interface. This database loses the ability to manage memory, consequently locking the processes and losing performance in the execution of some robust queries.

Unfortunately, this database doesn't have a good concept of partition table. If you need to create monthly (Jan. to Dec.) partitions in one table, this action creates 12 different files for the same table. In others databases, this process is more transparent and capable to create partitions inside the same database.

The technical support team for the SQL Server is very friendly, if we compare with others commercial database products. Not only with Microsoft, but this database has more technical information published on the internet, books, and self-taught users to help.

I am still using other commercial solutions, but the price of this database is much less expensive than others. It is about four times less expensive.

The initial setup is one of the good things about MS SQL. It is very easy to do and start the development that you need to use after the installation.

In my point of view, the MS SQL is the most inexpensive database commercial solution. If do you need to build a consistent ERP for example, with a medium to hard capability, and don't have much budget to spend it, this is your solution.

Of course, I evaluated other options! I never choose the first option and I always try to look around to find competitive vendor options. I already know and have expertise with IBM/DB2 and Oracle solutions. For this new architecture, MS SQL was the best option at the moment for being a pilot project.

I suggest that you are first familiar with the bundle functions and plan some of the functions before starting the project. Find more information about the routines and how easy or hard it might be to start the development when you are thinking about cascade and constraints.