Join top business intelligence and analytics experts in Chicago April 10-12 for 60+ sessions on the best practices, prescriptive guidance, and strategic vision you need to get the most from your data. Use code BACSSC to save $250 today!
Normally, the query Optimiser won't consider 'bushy' plans, where both operands to a join operator could be intermediate results from other joins. This means that it won't produce good query plans for some types of query. Hints, by themselves won't do it. More powerful magic is required.
The goal of this article to show how to get unique transactions per client per month from the data set containing multiple transactions per client per month.
The release of an extensive salary report for Information Technology shows some good trends in it for 2013.
Join us at SQL Saturday Boston on April 6th. SQL Saturday is a free training event for SQL Server Professionals and those wanting to learn more about SQL Server.
n a database I currently support, the application makes use of db_datareader and db_datawriter to give permissions to the tables. In a different database, it's even worse as the application uses db_owner. We're adding new tables to both databases and we don't want the application to have access to these tables. How can I deal with the use of these three roles?
A new idea from a small startup may revolutionize the way that you search for data.
Before adopting NoSQL for a commercial application that needs consistency and durability, you need to be satisfied that the product actually provides all those niceties that the user of relational database systems take for granted.
Resource Governor provides a great mechanism for throttling resources, but it doesn't always allow granular control. Read about this trace flag that allows you to dynamically alter the resource usage of a query.
If you’re involved in the database world it’s hard to have missed the rise of the “no-sql” database products, designed to – depending on your view or the product I suppose – make databases simpler, break out of the transaction database paradigm, scale out across hundreds of machines, make it easy to change the db design (or not require one). I think some of the problems no-sql tries to solve are real, others reflect a lack of awareness/training/tools on how and why relational databases could not just solve the problem, but solve it better.
By James Serra
What problem is Fabric Ontology trying to solve? For years, most data conversations have...
By Steve Jones
Recently I ran across some code that used a lot of QUOTENAME() calls. A...
By ChrisJenkins
There are some telltale signs that your growing business has outgrown Excel for your...
Comments posted to this topic are about the item Stairway to Reliable Database Deployment...
Comments posted to this topic are about the item QUOTENAME Quote Parameters
Comments posted to this topic are about the item Limit the Blast Radius
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