New answers tagged

0

Much data can be moved between tables quickly using partition switching. Even if you haven't defined partitioning explicitly this will work. From the documentation, each table has a default partition If a heap or index is not partitioned, it is made up of one partition This requires three tables: Working, which has the values currently being consumed by ...


0

There's a lot to digest / address here based on your description and responses so far, but I'll try to address the main things: You should almost always have a clustered index on your tables. The clustered index itself doesn't add any meaningful overhead in space usage, because it is the data of your table itself, sorted on the fields you define it on, ...


0

Azure sql Database is versionless. The version number that you get from @@version variable is 12.x (like sql server 2014 on prem) but it is not related to the engine and features. Versionless means that microsoft does not release major versions of SQL Server in Azure SQL. They are continuously updating the software that powers Azure SQL to give us the latest ...


0

What is the equivalent of each of the above in the azure cloud PaaS There aren't equivalents. Azure SQL PaaS has built-in HA and DR, with a few optional additions. But it's all managed by the service without you having to plan and implement solutions similar to what you would use with on-prem or IaaS SQL Server. Read: High availability for Azure SQL ...


1

I ran across this recently and it is a way of speeding up access to json with index like speeds: https://bertwagner.com/posts/one-sql-cheat-code-for-amazingly-fast-json-queries/ Not sure if this is allowed but I'll copy and paste some of the blog here: Recently I've been working with JSON in SQL Server 2016 a lot . One of the hesitations many people have ...


Top 50 recent answers are included