The Query Optimizer gets it right most of the time, but occasionally it chooses a plan that isn't the best possible. You can give the Query Optimiser a better idea by using Table, Join and Query hints. These come with a risk: Any choices you force on the Optimizer by using hints can turn out to be entirely wrong as the database changes with the addition of data over time.
This article introduces the concept of creating a Model within the Master Data Manager front-end, which will be the beginning of an example solution that will run for the rest of the article. Each of the different objects within the MDS object hierarchy will be covered, guiding the reader on how to build a model up step-by-step.
With a number of clients, I have been provided a sample format for a transactions along with instructions to develop a process to load it into a database as quickly and painlessly as possible. This usually comes with the requirements that the XML data file can have any number of records from 1 to n. This example demonstrates the most efficent and scalable way that I have found to solve this. Not to mention that it can be maintained without rebuilding the solutions each time the data format changes.
The purpose of a Database Properties Health Check is to determine what your database’s properties are currently set to for each of your SQL Server instances and to determine if the settings are appropriate for your particular environment.
In this article we will see how easy it is to use NHibernate in a real world application. We will create, with minimal effort, a fully working sample that allows us to write to and subsequently, read data from a database.