Deploying Database Developments. When a team is developing a database application, it is a mistake to believe that deployment is a simple task.
It isn’t. It has to be planned, and scripted. Alexander Karmanov describes many of the problems you’re likely to meet, and provides an example solution that aims to save the DBA from the nightmare complexity of an unplanned deployment. After the initial deployment of a database in an IT project, there is often insufficient thought given to subsequently deploying the inevitable changes in the database’s structure, configuration, fixes and so on. It is not uncommon to find a development in which only one copy of the database exists. For larger-scale developments, database objects are stored in form of a script which is lodged in a source control system such as Visual Source Safe, Team Foundation Server or SVN/Subversion.
In both cases, the build process assumes that the database is created from scratch, from the scripts. Goals We also needed to Incremental vs. A Full database build. Multi-line SQL String Literals in C# Multi-line SQL String Literals in C# Back in September there were a couple of unrelated blog posts that used literal multi-line SQL strings as examples to illustrate two different points.
The first by David Cumps investigated the performance aspects of string concatenation vs. memory allocation. The second by Chinh Do presented a number of Visual Studio 2005 IDE tips and tricks, one of which was the use of regular expressions in the find and replace dialog. In both cases, the syntax they chose to initialize their C# string variables with literal multi-line SQL statements were, in my opinion, more cumbersome than necessary.
This may be due to their primary points being about something other than string initialization syntax; however, it seemed like something worth pointing out. David Cumps uses the following syntax samples in his (very thorough) investigation of string concatenation performance: you are luck,never encountered and ADO.Net Provider that had a problem with it. x16man, Thanks. SQL Query Optimization FAQ Part 1 (The SQL Plan) SQL Query Optimization FAQ Part 1 (The SQL Plan) Introduction and Goal In this article we will first try to understand what is a SQL plan, how is it created and then we will move towards understanding how to read the SQL plan.
As we read the SQL plan we will try to understand different operators like table scan, index seek scan, clustered scan, RID lookup etc. We will also look in to the best practices associated with clustered and non-clustered indexes and how they function internally. We will practically see how indexed views increase performance and in what scenarios we should use the same. Here’s my small gift for all my .NET friends, a complete 400 pages FAQ Ebook which covers various .NET technologies like Azure, WCF, WWF, Silverlight, WPF, SharePoint and lots more from here Quick video to jump start SQL Server performance tuning What is a SQL execution Plan?
Sqlite. MySQL. Linq. Entity Framework.