Forwarded records in SQL Server can cause performance issues on heap tables because the record outgrows the page and the database engine uses pointers to reference the data. The best practice is to have a clustered index on every table, however, sometimes there are cases when a clustered index is not needed.
How you examine and approach a problem might have a large impact on how you solve it. Steve Jones notes that it's important that all of us look at the problem from the point of view of the customer, as well as our own view.
The continuing drop in the price of memory has made fast in-memory OLTP increasingly viable. SQL Server 2014 allows you to migrate the most-used tables in an existing database to memory-optimized 'Hekaton' technology, but how you balance between disk tables and in-memory tables for optimum performance requires judgement and experiment.
This metric returns the number of check constraints that have their is_not_trusted flag set to 1 in the sys.check_constraints table. Untrusted constraints force SQL Server to construct less efficient query plans, because it doesn’t know enough about the kind of data contained in the table. This can point to a data integrity issue which should be investigated.
Is there a better way to put together a conference or event? Today Steve Jones speculates on how events are run and how we might change things.
A comprehensive list of trace flags for SQL Server that you can use to configure your server instance.
SQL Server 2012 Integration Services introduces an innovative approach to deploying SSIS projects, known as Project Deployment Model. However, the traditional, package-based methodology remains available and supported, and, in some scenarios, it might be considered more viable, since it allows for separation of SQL Server Database Engine and SQL Server Integration Services.
While AlwaysOn and Columnar lookup are good enough reasons to migrate to SQL Server 2012, you need to be aware of the problems associated with certain virtualize environments.
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