Overall Satisfaction with Microsoft SQL Server
I use SQL Server for 7 years.
I currently work in the Database Administrators department, we mainly use SQL every day. We use SQL for various needs, some examples: the management of corporate databases, for ETL processes (extract, transform, load) for data warehousing, data historicizing, reporting, OLAP cubes, dashboards, maintenance plans, monitoring and alert, the management of integration services packages and more.
- Management of very large volumes of data such as bulk loading
- Is one of the best (if not the best) relational database
- It brings you great ETL tools and data warehousing such as SSIS and SSAS
- Data indexing
- The management of VLDB (Very Large Databases) requires a lot of maintenance and preventive work to avoid falling into uncomfortable issues.
- The introduction of In-Memory (sql 2014) has opened up new prospects but still has many limitations (data types, functions and various restrictions)
- Table partitioning is as useful as awkward to handle.
- Data always accessible and available
- data history and previous analyzes (even many years back)
- development and maintenance of the data warehouse directly in-house
I started working with databases many years ago with Access, which allows you to create relational database and provide an old-fashioned desktop interface. I had a look at Oracle but I never had the opportunity to get to the bottom (also because of the budget that had the company where I worked at the time). SQL is an enterprise solution that allows professional management of DBs and DWHs in maximum safety and allows it to be applied in countless situations.
SQL Server is suitable for any company, anyone who has the need to keep and maintain sensitive data, can safely rely on SQL (available in different versions depending on your budget and needs).
Is less appropriate, however, if you want to handle a small amount of data, or if you use want to cache data (for sites) or data that don't need to be static and maintained for a long time, in these cases you can take into account of commonly said DB No-Sql.
Using Microsoft SQL Server
50 - It is not easy to determine how many resources actually uses sql server, this because the use of sql server is of various kinds, from those who simply makes queries via the sql management studio, who uses the various business reports or dashboards, users of the sites, up to our DBAs department that directly manages the databases and data warehouses.
4 - To use SQL Server are required detailed knowledge of relational databases, data warehousing concepts, notions and management of ETL (if you intend to use a corporate data warehouse), maintenance of databases, data management, data quality, high reliability of the data, indexing, queries optimization, management of a large amount of data and more.
- Data management
- Reporting and Dashboard
- High Availability
I think it is unlikely that sql server has disappointed someone, it is likely that someone will come initially discouraged if the needs and problems that occur are very challenging, but definitely have a SQL oriented system means having a solid base to work and on which maintain the their data securely.
Evaluating Microsoft SQL Server and Competitors
- Product Features
- Product Usability
- Prior Experience with the Product
- Analyst Reports
I personally have not taken the decision to use SQL Server, but the reason why I specialized in SQL systems is because I think it definitely one of the best RDBMS in circulation, the support is great as well as his strength and for his great effectiveness, is chosen to secure by many companies to these factors and results.
If I had to choose whether to use an RDBMS the first question that I would do it if I really need a SQL db oriented or if I could draw benefit from a no-sql db, if my need is to have an RDBMS, the only choice that I should make is between Oracle and SQL, due to my experience in SQL would repeat this choice, if I'll have the opportunity to deepen Oracle will also evaluate this hypothesis (prices permitting) .
Microsoft SQL Server Implementation
As mentioned before, the implementation of SQL Server in a company that is beginning to use a new structure, which does not require any type of data migration, do not requires particular comment to make.
If you must to do a porting of databases from a different platform, definitely you need to consider the situation in detail depending on your needs.
Change management was minimal -
Has no organizational change management needed.
However, if you are thinking of definitely migrate your data structure on sql server, you have to do several observations , you need to plan in detail every single operation, each database step by step and evaluate all the compatibility between your structure and the version of SQL on which you will migrate. This definitely requires a lot of time and tests.
Microsoft SQL Server Support
In my previous work experience I happened to have asked for assistance to the Microsoft support, they are very professional and the service is immediate, if necessary they can intervene remotely or onsite.
Alternatively you can of course refer to the microsoft guides, the forums and of course the now famous msdn.
Problems get solved
Kept well informed
No escalation required
Support understands my problem
Support cares about my success
No - Fortunately we do not need premium or paid support because, fortunately for us, our team is well mixed and every time there is a problem to solve, we trying to reach a solution as soon as possible in the most constructive way possible by sharing the experiences and our know-how.
As I said before, fortunately it has never been necessary to seek assistance from Microsoft support regarding SQL Server, many of the answers you seek are on the MSDN Microsoft, alternatively you can open a ticket with microsoft and in the short term you will have solution to your problem .
Very useful are the Unleashed books (in your sql version) that have all the basics you need to manage sql servers.
Using Microsoft SQL Server
Once you have gained adequate experience to manage autonomously SQL Server sql server usability it is excellent, the fact remains that the SQL Server platform has a variety of very wide use, are so many variables to consider in a sql oriented system. Usability (mean maintainability) becomes more complicated if it is larger the amount of data to manage (with large I mean some TBs for each databases)
Like to use
Technical support not required
Feel confident using
Difficult to use
Slow to learn