SQL Server Reviews

We primarily use the solution for our banking database.

Overall, it's a very good device.

The solution has proven to be very stable.

The scalability potential is very high.

The initial setup is very straightforward and the deployment happens very quickly.

The solution could offer more integration with other platforms.

I've been using the solution for about ten years or so. It's been about a decade. It's been a while. 

The product is very stable, from my experience. It doesn't crash or freeze. There are no bugs or glitches. I've used it for ten years with very few issues. The performance and reliability are very good.

The solution can scale quite well. If your company needs to expand it, it can do so pretty easily. It's not hard.

We currently have 5,000 users on the solution.

We do plan to increase usage in the future.

We've dealt with Microsoft technical support in the past and we were very satisfied with the level of service provided to us. They are knowledgeable and responsive. 

The initial setup is straightforward. I wouldn't describe it as difficult or complex. It's actually very simple. A company shouldn't have too much trouble with the implementation.

The deployment was fast and barely took two days.

We have five people on staff who can handle the deployment and maintenance for us. They are administrators and engineers.

We had a consultant that assisted us with the implementation. They were very helpful and made the implementation very simple.

We pay a yearly license to Microsoft. I can't speak of the exact cost, however.

We're likely using the latest version of the solution.

I'd rate the product at a nine out of ten. We have been very satisfied with its capabilities over the last decade.

I'd recommend the solution to other users and companies.

The solution can be used for a host of applications.

The maintenance and tasks should be improved so as to reduce database files.

The complexity of the database should also be reduced, so that its size can be diminished. 

I have been using SQL Server for around ten years. 

The solution from the 2008 version is stable. I like the defined database and the ease with which it can be used and that enquiries can be made. 

I believe the solution to be scalable and plan to increase our usage. 

Installation is relatively easy, although I do not recall how long it took. 

We made use of an integrator.

There is not much technical team required for the deployment and maintenance. It consists solely of engineers.

The licensing is on an annual basis. 

Prior to going with SQL Server I utilized the Oracle Database.

There are around 15 people making use of the solution in our organization. Every computer processing unit has its own license. 

I would recommend the solution to other users. 

I rate SQL Server as an eight out of ten. 

SQL Server is enterprise database software. It provides the back end for any number of different applications, including web applications, and other types of internal applications, and software-based applications. It also provides a back end for enterprise backup tools. It's incredibly diverse in terms of its use case.

Scalability, cluster ability, ease of use, ease of implementation — these are all great. 

In terms of exceptionally large databases, it doesn't scale as well as Oracle. It scales excellently and it's flexible and it can provide a solution for exceptionally large databases, but it doesn't work as well as Oracle does for this particular use case. The performance starts to drag in the case of exceptionally large databases; especially where there's a lot more feature functionality. With Oracle, there's a lot more tunability.

I have been working with this product for 20 years. 

It's exceptionally stable. The ease of implementation and the ease of use can't be beaten. I think it's outstanding overall.

Scalability-wise, it's outstanding. The one limitation it has is that at the very, very high end of petabytes-sized databases, it doesn't scale as well as Oracle. Still, you're not going to run into very many exceptionally large databases. Almost 100% of the use cases for it scale very well.

Technical support is available for a separate cost. If you don't have a subscription or a support contract, then you don't get support. You'll be stuck with online forums — that's how you'll have to get answers to questions. Assuming you have a support contract with Microsoft, it's outstanding.

The initial setup was straightforward. 

This solution is available at a much lower price point than Oracle. Plus, it includes 99% of the same feature functionality. I'd say it knocks ROI out of the park.

If you're interested in using this product, make sure that you have a good understanding of best practices for database implementation. Make sure to incorporate them in your deployment right off the bat. You won't want to have to go back and have to take production databases down because you have to change the configuration, post-implementation. Make sure you get all of these things done, pre-production implementation.

They've come a long, long way in the 20 years I've been working with them. Overall, on a scale from one to ten, I would give SQL Server a rating of nine.

We develop software for another company. We mainly develop on-premises solutions.

We use this solution with our accounting ERP software. Our product is called Orchida ERP and we have many clients in Egypt who are using this software. Its database is SQL Server.

We mainly work in ERP. 

We currently have a small project in SharePoint for Microsoft, but 80% of our work is with Orchida ERP

We have our software with SQL server for 20 years. Our software will not work without SQL Server. 

We provide consultancy in installing this solution for our clients.

It is easy to maintain, and it's easy to set up.

It is also easy to develop. Overall, it's easy.

It can work with many different sizes of data, anywhere from 10 to 50 gigs of data.

The performance of SQL Server is perfect. It does not need to be enhanced.

If you work with more than 50 gigs of data, it will run slower than Oracle.

Security is an area that can be improved. It could be more secure; more security is needed.

We have some clients who have been exposed to the SQL injection virus. 

We would like SQL to be able to manage this problem or to come up with an alerting system to alert the user that the server has been exposed. This has become more of an issue because of the Corona Virus and people are working from home.

Some have been infected by the SQL injection Virus and will lose their data.

I have been using  SQL Server for 20 years.

Most of our clients work with version 14 and version 19, which is the latest.

It's a stable solution.

SQL Server is scalable. Our clients are medium-sized companies, not large. They don't have professional IT.

We have 20 people in our organization who are using this solution, but we have many clients who are using it. We sell our consultancy service to more than 200 clients every year.

If we have any issues, we search Google and the internet to resolve them.

Our company has not used Microsoft Support. 

We have tried many versions of Oracle, including Oracle 11, Oracle 12, and the latest version, which is easy to maintain and similar to Microsoft.

Some of our clients are also using Express SQL. It is not good, but also not bad. If you have small amounts of data then it will meet the requirements.

The installation is straightforward. It is easy, you continuously click the next button until you are done.

It takes 20 to 25 minutes to install. There are no issues with the installation, it is very basic.

We did not use an integrator, we have an in-house team to install and implement this solution.

Some of our clients purchase the license and others do not; they use Express SQL Server.

One of our clients is using an SQL Server on Linux. We don't use it but it is a very interesting product. It's a good trend, the Linux environment has become a market share that is growing in Egypt.

I would recommend this solution to others who are interested in using it.

We can't compare this solution with other databases, as we do not have enough experience with other similar tools. 

Overall, SQL Server is good. I would rate SQL Server an eight out of ten.

There are many applications between Microsoft and SQL. Most are in the legacy direction, but some are more modern databases with those application requirements. We have used it for multi-purposes such as back-office products applications and cloud office environments.

The solution is easy to use, has rich feature sets, and is business-oriented. 

They could improve the solution by allowing more portability between on-premise and the cloud.

More improvements can be brought around hyper-threading. Like we see in work engines of hyper-threading. It is very complex in terms of the way they do it. If it was via CPU or something else, it would be much easier.

In a future release, they could improve by expanding their form base capabilities.

I have been using the solution for a couple of years.

I have found the solution to be very stable.

The solution is scalable.

The support is good for the solution.

We used Oracle and DB2 in the past.

Initially, the installation took a while. We have started deploying configurations that are now standardized. We have automated it, but it can still be problematic. For the most part, the installation is now quite easy. Additionally, The way they have many configurable parameters that influence performance is in a way problematic.

We did the deployment of the solution and we have a team of 15 people doing the deployment and maintenance.

The licenses are really expensive. Their licensing model should be more simplistic.

I would recommend this solution to others and we plan to keep using it in the future.

I rate SQL Server a nine out of ten.

SQL Server is used to establish secure storage and protect databases from potential vulnerabilities, including those originating from Slack.

The most valuable aspect is the ability to use jobs and various functions to accomplish specific tasks, which cannot be achieved with standard procedures alone. This allows for a combination of features and functionalities to be employed.

I have experience working with SQL Server 2016 and older versions, including handling JSON data. Initially, I found the JSON capabilities to be less helpful, but over time, they have greatly improved. 

SQL Server now offers extensive capabilities for working with various forms of data, particularly when communicating with text, such as in JSON format. 

I particularly prefer working with these features on Azure, as it provides numerous possibilities, especially in the field of business intelligence (BI). Additionally, the serverless platform offered by Azure is highly beneficial and makes tasks easier to manage.

I have not seen significant returns thus far, but I am eager to enhance my experience by transitioning to work in Azure. This shift to Azure is something I am motivated to improve upon.

I have been working with SQL Server since 2018.

We have not had any issues with the stability of SQL Server.

Scalability is dependent on memory.

The matter at hand pertains to whether we are discussing an issue in general or specifically in the context of on-premises environments. However, it is clear that memory and capacity are significant factors in both scenarios. 

Proper management of memory and capacity is essential to ensure smooth system operation and prevent any performance or stability issues. 

As a result, it is essential to handle these issues completely and appropriately in order to meet the system's requirements.

I have not contacted technical support.

The installation process is not complex, but it requires attention to detail in terms of selecting the necessary services and configuring the Cisco server. 

This ensures a proper setup and a tangible model for effective management. While it may not be complicated, it is important to choose the appropriate features during installation. 

Working with ID was not my primary focus; however, I have had the opportunity to work with it for several companies.

It can take an hour to an hour and a half to deploy.

Maintaining it is more challenging than the initial setup. One of the main concerns is ensuring sufficient memory allocation. The default capacity is typically set around sixty, but it can be increased if needed. If there is insufficient memory, it can lead to server downtime and cancellation of transactions, as exceeding the memory limit poses a risk. Therefore, it becomes crucial to address this issue by allocating more memory resources. Additionally, backups and restores play a significant role in ensuring data safety and recovery in case of any issues.

For a brief period, approximately one year before 2018, I had experience working with the open-source version of SQL Server. During that time, I found SQL Server to be the preferred choice, in my opinion.

I developed an application for specific purposes related to McDonough. Using Microsoft SQL Server, I constructed the entire database and implemented supporting stored procedures. This application was commissioned by the European Union to enhance government institutions and similar entities.

Additionally, I worked on financial-related stored procedures specifically related to Serbia Card, as part of a project for the USA.

We acted as a subcontractor for S&P within your company. I have extensive experience in SQL Server, particularly within the Microsoft environment.

They should think twice before they do anything and double-check. Definitely.

I have explored different options such as SonicWall and open-source solutions, but my preference lies with SQL Server. I find SQL Server to be fantastic, as it provides comprehensive functionality and makes tasks incredibly easy. 

Working with Postgres is also simpler compared to other databases like Oracle. Perhaps my familiarity with Excel has made SQL Server more intuitive for me. While I understand that Oracle is known for its complexity, I appreciate that its code and syntax bear similarities. 

Overall, I have a strong affinity for Microsoft products.

I would rate SQL Server a ten out of ten.

Performance-wise, SQL cannot handle large amounts of data. In the next release, I would like them to commission SQL Server on Linux, as has been announced in the past but has not yet happened.

I've been using SQL Server for thirteen to fourteen years.

SQL is a highly unstable server - there are patch updates on the Windows server every week, which is why we only use it for non-critical systems. 

The initial setup was very easy - much, much easier than Oracle - and took about a day to complete. Microsoft is less demanding because everything is GUI, unlike Oracle, where you need to use command lines.

This is a very cheap product.

SQL's performance is good enough if you have a low amount of data. For those looking into implementing SQL Server, I would advise first analyzing your requirements and whether your system is critical or non-critical. If it is non-critical, go for SQL as it will save you in terms of cost, but if it is critical, avoid SQL as it will bring you down in one day. I would rate this solution as eight out of ten.

This is the main database for our financial system. I'm the IT manager and we are customers of SQL server. 

We've been using this solution for many years.

We're satisfied with the stability.

We have around 100 users. The database isn't used directly, so users are not even aware that there is a SQL Server underneath. 

There are some local companies that have direct relations with Microsoft. We use them regularly when we need some support.

I don't recall, it's been many years since we implemented this product. 

We pay a license fee, it could always be cheaper.

I recommend this solution and rate it 10 out of 10.