Python-based platforms like Pandas or Spark are very good too at displaying data and do exploratory analysis. I definitely prefer them to SAS EG. It's just too slow, and doesn't let you peek into the data very easily. Lots of clicking, and I'd rather just write some code, …
Although not used in the enterprise, I have used Anaconda Python to shape and cleanse data from Excel reports that was too difficult for SAS to complete. The object oriented nature and the Pandas package made ingestion of the data and reshaping more useful in this use case. …
SAS EG has better Graphical User Interface to build project trees and help users to create data queries/calculations. SAS EG can handle bigger data sets compared to other programs. You can easily clean the data sets and manipulate the data. It is easier to send the project tree …
Why I prefer SAS EG: Data processing speed is much faster than that R Studio. It can load any amount of data and any type of data like structured or unstructured or semi-structured. Its output delivery system by which we have the output in PDF file makes it very comfortable to …
I haven't used SPSS myself but from what I was told, integration of data was much more limited and not easy to used. Also, the number of people with SPSS knowledge is less than the number of SAS users so finding workforce can be an issue. The whole SAS solution just made much …
You could consider i did use Mysql since i worked with some websites that were using a mysql database. I could not give a side by side comparision since i don't use those like i use the Microsoft SQL , but so far it worked well. I prefer Microsoft SQL due to support and info …
UI of the Microsoft SQL Server makes it easy to use and learn. The better technical support and documentation give it an extra edge over other databases. The Microsoft ecosystem provides additional advantages, as we can seamlessly use other Microsoft products, such as Power …
Microsoft SQL Server is faster and more compatible, but it does cost more, so you're paying for those features. I use the others in many other places where critical transaction processing time and compatibility aren't of great concern.
Microsoft SQL is slower than MySQL and Access but far more feature-rich and reliable. Access is almost obsolete nowadays, so not too many people are considering it, but unless budget or an open-source ethos is a factor, Microsoft SQL is superior in every way. Many commonly used …
Microsoft SQL Server providers a more user friendly experience when it comes to Microsoft SQL Server components management via its unique SQL Server management Studio. It is also a production ready, resilient, highly available and tested database management system (DBMS). The …
The first database application taught when I was in school was Microsoft SQL Server. Microsoft SQL Server was used where I first started, so I had the opportunity to improve myself in MySQL. SQL is also used in my current workplace. It is widely used in very large projects due …
We have a few different DB's in the organization, including: Pervasive, Oracle, Db2, MySQL. Many of them are of limited use for one specific application. These don't really compare to MS SQL server. Oracle is heavy and cumbersome and overkill for smaller apps. Pervasive - …
Microsoft SQL Server is a comprehensive solution as transactional database, data warehouse, analytics, reporting, and ETL. It also integrates with the cloud well (Azure). The ease of use and setup makes this better than Oracle Database because the query syntax is also different …
I think both tools are really powerful and close to each other but since I moved to Europe I realized that most of the companies have been using SQL Server which in my opinion means something. The support from Microsoft I also consider a bit better and you can also find more …
Microsoft was the original creator of the SQL database, and thus, they still rule the market and drive innovation when it comes to data warehousing systems. It's comparable in price and allows you to retain the structured datasets that you lose when you change to a NoSQL …
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
Microsoft SQL Server and Oracle are both extremely powerful and scalable enterprise relational database platforms. Microsoft SQL sets itself apart with its ease of use and licensing and support model. Microsoft is good company to work with and they provide clear and …
It just boils down to why learn anther product when you are going to run across it so seldom. Developers determine what database engine I am going to need so I just tend to pick products for implementation that use a well know product that has lots of support resources …
The most known and widely used competitor of Microsoft SQL is most probably the open-source MySQL. If given the choice I would personally choose MySQL over Microsoft's SQL Server, mainly because it is totally free and open source, but also because it integrates better with …
[Microsoft SQL Server] offers a full solution, Inhouse Applications and hosted application continue to use SQL as backend database. Allows easy creation of development environments and continuous feature release.
All of the platforms have their own benefit. I was not the decision maker in selecting Microsoft SQL Server, as it was already being utilized when I joined the company, 7 years ago. I can say that I feel more comfortable with utilizing this platform as opposed to the other ones.
The free version is very powerfull and easy to install and use for small companies. Going to Professional and Standard, gives you all the support and the flexibility needed. It is known within the Database Administrator crew, and you can get support very easily over the …
Native to Windows and being required for other MS apps puts it above others in terms of usage. If we were not heavily dependent on Microsoft applications or OS, we might have considered other database solutions. It's an expensive solutions but it is a solid reliable solution. …
I was not too impressed with Oracle. Following the manual prohibited installation. They did provide a phone number and explained the manual was wrong and provided me with the correct information with which I was able to install the product. This was awhile back and I do not …
Microsoft SQL Server is one of the fastest RDBMS systems available in the market. Pricing is a bit on the higher side but all the features it provides pretty much justifies it. It can be integrated with a large number of frameworks thus enabling to work on multiple frameworks …
Microsoft SQL Server is still the industry standard for the type of development we do, and the types of applications that we use. Almost every developer or analyst we hire has at least a reasonable grounding in the use of SQL servers, and it is almost universally compatible …
For writing out longer code creation for shaping data on complicated reports, the clean UI is helpful. If exploring data though, SAS Studio would be better suited given its easier interface for GUI graph building.
Microsoft SQL Server is ideal for highly available SQL workloads by using SQL Server Always On availability groups. Microsoft SQL Server might not be appropriate for solutions which require a very low resource footprint, since it requires significant CPU cores and RAM memory as well as high IOPS, always depending on the usage scenario.
I would like to see advance interactions with external databases to be able to kill ongoing queries from SAS. As of now, you can stop pretty much any ongoing process besides the one running on a remote database (killing SAS/EG doesn't stop the remote process)
When creating prompts for programs, it would be nice to be able to have conditional prompts (based on the selection of other prompts). The prompts are clearly a recent feature and constantly under development but I wish it would be more powerful.
More of a SAS metadata issue but when loading SAS/EG (first connection to the server), it takes a few seconds which feels like a long time. I really don't understand why the initialization of the session can take so long. Don't get me wrong, this has no real impact on productivity but that 10s delay just feels really like eternity when you want to run some code in a new session.
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
It's not all bad, but I don't believe that an enterprise purchase of SAS is worth the expense considering the widely available set of tools in the data analytics space at the moment. In my company, it's a good tool because others use it. Otherwise, I wouldn't purchase a new set of it because it doesn't have some of the better analytical functions in it.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
Although I use SAS support for information on functions, these are SAS related and haven't really come across anything that is specifically for SAS EG.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
I've not worked hands-on with the implementation team, but there were no escalations barring a few hiccups in the deployment due to change in requirement & adoption to our company's remote servers.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
Python-based platforms like Pandas or Spark are very good too at displaying data and do exploratory analysis. I definitely prefer them to SAS EG. It's just too slow, and doesn't let you peek into the data very easily. Lots of clicking, and I'd rather just write some code, rather do clicking.
Microsoft SQL is slower than MySQL and Access but far more feature-rich and reliable. Access is almost obsolete nowadays, so not too many people are considering it, but unless budget or an open-source ethos is a factor, Microsoft SQL is superior in every way. Many commonly used tools, like Crystal Reports, support it.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.