![]() It also features the powerful In-Memory Column Store (IM column store), that allows you to store columns, tables, partitions and materialized views in memory in a columnar format, rather than the typical row format. Oracle 12C EE provides powerful SQL advisors (like SQL Tuning Advisor and SQL Access Advisor) and memory advisors that you can use to help improve database performance. Sorry if my english it’s not understandable… i’m writting this with the help of Google Translate haha Reply ![]() I’m waiting for the CTP of SQL Server on Linux, to try it… I dont have anything against PostgreSQL… but this time, even the SQL Server Standard Edition was good… ![]() Some things don’t work the same way, or needed some hacks to make it work, like, implementing some analytical functions that exists in Oracle for our Datamining team and certaing UDF functions in SQLCLR, for exampleīut, we are full at SQL Server right now… sometimes we discover some things Oracle managed best than SQL Server (Oracle MVCC & SQL Server RCSI dont work the same way for us), but, hey, the savings, going even to 2 Enterprise Edition Clusters, were big enough to justify the effortĪnd we are glad to have choosen SQL Server… We even dropped one of our Enterprise Edition Clusters for one Standard Edition Cluster… we just needed to fix the things that only work on Enterprise Edition and optimize the querys to run on a more constrained server… you need to distribute your data in the right way to obtain performance improvements), going to SQL Server we obtained great performance gains over Oracle (query response time dropped like 500% in some cases, without the need to rewrite the sentence, thanks to their columnstore indexes… remember, its a Dataware House)… even rewriting the code for SQL Server was a lot more painless than trying to do the same for Postgre… By fun I mean “use Postgres instead”.Īt my work, we choose SQL Server 2014 over PostgreSQL for a DatawareHouse Migration from our Oracle 11g Cluster (with 2 instances)… If license is your problem, prepare yourself for a journey full of pain trying to obtain the same or more performance and efficiency in PostgreSQL… with SQL Server, their clustered columnstore index, their space savings, the query parallelization options (hint, Postgre right now don’t have parallelization natively… only in custom dists like Postgre-XL, but, limited to 1 thread for every nodes in your cluster… aaaaaand. That’s what these change-databases projects usually involve – as soon as you take even a cursory look at the database queries, they’re written in a way that ties them to a specific database platform.ĭon’t get me wrong – I’m not saying SQL Server is the best answer for every app.īut I *am* saying that rewriting the entire app almost never is.Įrik says: If you use common table expressions, re-writing your code for MySQL will be fun. Those projects are usually way cheaper and faster than trying to rewrite the entire application’s back end. Can we implement a free/cheap caching layer like hosted Redis?.Can we move non-relational data out of the database? (Like full text search, XML/JSON storage).Can we drop from Enterprise Edition to Standard Edition?. ![]() Can we performance tune the database to run on a smaller instance size?.I usually hear this goal from companies renting their licensing from their hosting provider (like Rackspace or AWS), in which case we’ve got a few options: If you want lower SQL Server licensing costs, then we take a step back and look at how you’re buying SQL Server today. This usually buys the company a year’s worth of runway time, at which point they can either knock out another round of low-hanging fruit, or reconsider the database back end decisions. If you don’t have a full time database administrator, then it’s easy to implement a round of quick fixes in just a few days that take care of the low-hanging fruit. Remove the bottlenecks by tuning indexes, queries, SQL Server config settings, or hardware.Find the queries causing those bottlenecks (like with sp_BlitzCache = ‘reads’).Measure the SQL Server’s current bottleneck with wait stats (like with sp_BlitzFirst = 1).They’ve built a software-as-a-service application, and they’re hitting performance issues. Usually, I get these kinds of calls from teams of developers that don’t have a full time DBA. If you’re doing it to get easier scalability, we start by taking a step back and looking at the performance problems in the current setup. “We’re considering migrating our application from SQL Server to a cheaper, easier-to-scale database. I’m getting an increasing number of requests these days that say:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |