|
|
-
|
|
Developer training is essential for the mutual benefit of both - the employee & the employer. Employees who effectively use the trainings provided to them make the workplace more efficient & productive – resulting in a happier employees and efficient teams. In this follow-up post to Pinal Dave's recent series on the subject, I share some of my tips to get your share of the required trainings....
|
|
-
|
|
As Microsoft SQL Server evolves and matures over time, using non-ANSI compliant code will result in rework. One such example is the use of OUTER JOIN operators (*= and *=), which are no longer available with SQL Server 2012. Use the ANSI compliant, SQL-92 syntax instead....
|
|
-
|
|
Do you need to register a remote SQL Server instance on your server? Or do you need to change the name of a SQL server instance? sp_addserver will not work with SQL Server 2012 for remote servers anymore. Read today's post to know how to use: sp_addlinkedserver as the replacement....
|
|
-
|
|
Today we explore a former table hint - FASTFIRSTROW - which tells the optimizer that it is important to have the first row returned as fast as possible, allowing the application to return results to the users faster. The table is now replaced by a query hint - OPTION(FAST n)...
|
|
-
|
|
Changing database options to make it read-only, or taking a database offline? If you are using sp_dboption, your code will not work with SQL Server 2012. Use ALTER DATABASE...SET statement instead....
|
|
-
|
|
Starting SQL Server 2012, the WITH APPEND option in the CREATE TRIGGER statement has been deprecated. This option was used for compatibility levels 65 or lower to create another trigger of the same type on any given table....
|
|
-
|
|
AWE (address windowing support) is no longer available for SQL Server 2012. Today, I attempt to highlight the requirements & behaviour around 64-bit editions of SQL Server/operating systems....
|
|
-
|
|
Almost every product comes with a set of predefined system default data. There are very few product teams who use row constructors (introduced in SQL Server 2008) to populate their default data. What these teams fail to realize is that many a times, the conventional approach may have a negative impact on the time it takes to insert the data and also reduces the overall efficiency of the entire data load operation....
|
|
-
|
|
Returning Result sets is perhaps one of the most common methods used by development teams to debug databse triggers. However, returning result sets from triggers is already marked as a deprecated feature. DBAs can use the "disallow results from triggers" switch to begin educating teams to start moving away from this technique....
|
|
-
|
|
The old DATABASEPROPERTY function has been marked as deprecated starting SQL Server 2005. The replacement is the DATABASEPROPERTYEX which provides greater flexibility and exposes many more database properties to the user....
|
|