Over the years, Phil was struck by the problems of reading and writing JSON documents with SQL Server, and wrote several articles on ways of overcoming these problems. Now that SQL Server 2016 onwards has good JSON support, he thought that the articles would be forgotten. Not so, they continue to be popular, so he felt obliged to write about how you can use SQL Server's JSON support to speed the process up.
It is getting to be that time of year. Holiday parties are you for them or against
Brent Ozar shares a free script that that you can run to quickly produce a health check of your SQL Server.
Here's a data warehouse design pattern to speed up multi-value dimension creation.
In SQL Server 2017 consuming or providing JSON data is so efficient that you can implement effective microservices right from the database, argues Phil Factor.
In the real world of business or scientific reporting and analysis, data can prove to be awkward. It can be plain wrong or it can be altogether missing. Sure, we have the NULL to signify unknown, but that doesn't play well with regular business reporting. There are a number of ways of dealing with missing information, and methods of estimating data from existing data has a long and respectable history. Joe Celko gets to grips with a data topic that is often treated with some trepidation.
Build and Operationalize scalable Predictive models and intelligent applications using SQL and R.
This Friday Steve Jones wants to know about the lifetime of your instances. Do you have some idea on how long you'll run a particular version of a platform?
Your Agile developers want MongoDB, or a similar document database: your Ops people are concerned about security and backup, and Governance are muttering about transactionality and data transfer between systems. Do you restrict your developers from rapidly-evolving the data design for their domain or do you embrace the joys of NoSQL unconditionally? If you accept a polyglot database environment, where the NoSQL lambs coexist with the relational lions, how do you provide tools and common database concepts that everyone can use and understand?
Thank you to everyone who participated in T-SQL Tuesday #198! When I wrote the...
Efficient query performance in Amazon Redshift often comes down to how well you manage...
By gbargsley
Welcome back to PowerShell Strikes Back. We’re three weeks in, and the training is...
Comments posted to this topic are about the item QUOTENAME Quote Parameters
Recently, our dev teams approach me for advice on improving their huge heap table...
After upgrading 2 Merge Replicated databases to SQL 2022 and re-establishing the Merge Replication...
When I use QUOTENAME(), I can optionally provide the character used to surround the string in the result. Can I use any character?
See possible answers