SQL Server 2008 Management Studio tip: Status bar Custom Colors

published 7 days, 6 hours ago, submitted by Jemm 7 days, 15 hours ago

blog.jemm.net — "Here is a handy tip for those of you who work often with multiple SQL Server instances: Custom Colors for the connection status bar." read more...

2 comments | category: Database | Views: 237

SQL Server – Using INTERSECT Operator

syedarizvi.blogspot.com — INTERSECT operator was introduced in SQL Server 2005. INTERSECT can be used to return distinct records from the left and right side of a query. <a href="http://syedarizvi.blogspot.com/2008/08/sql-server-using-intersect_07.html">Full story</a> read more...

add a comment | category: Database | Views: 15

SQL Server - Common Table Expressions (CTE)

syedarizvi.blogspot.com — Common Table Expressions (CTE) construct was introduced with Microsoft SQL Server 2005. CTE behaves like a derived table but unlike derived table which has statement level scope CTE offers a procedure level. read more...

add a comment | category: Database | Views: 9

SQL SERVER - 2005 - Difference Between INTERSECT and INNER JOIN

published 14 days, 20 hours ago, submitted by pinaldave 16 days, 4 hours ago

blog.sqlauthority.com — INTERSECT operator in SQL Server 2005 is used to retrieve the common records from both the left and the right query of the Intersect Operator. INTERSECT operator returns almost same results as INNER JOIN clause many times. When using INTERSECT operator the number and the order of the columns must be the same in all queries as well data type must be compatible. Let us see understand how INTERSECT and INNER JOIN are related.We will be using AdventureWorks database to demonstrate our example. read more...

3 comments | category: Database | Views: 235

Immediate deadlock notifications without changing existing code

weblogs.sqlteam.com — In my previous post about immediate deadlock notifications in SQL Server 2005 I've shown a way to use a try catch block to get the deadlock error. The con of this method, although it uses best practice for error handling in SQL Server 2005, is that you have to change existing code and it doesn't work for non stored procedure code. And that IS a pretty BIG con! So here's a solution to this con. read more...

add a comment | category: Database | Views: 5

Setting Up an alias name for connecting to SQL server

sqlblog.net — Shows you the steps you need to take to setup an alias for a sql server instance on windows server (or desktop). read more...

add a comment | category: Database | Views: 11

How To: Rename SQL Server 2005 Database Using TSQL

dbalink.wordpress.com — For some reasons, DBA’s need to rename their Databases. One of the reasons might be to comply to Best Practices Policy changes. Here we are going to rename our Database named “Bad_Ass_DB” into “Best_Practice_DB”. This is how Database renaming with TSQL is done in SQL Server 2005.... read more...

add a comment | category: Database | Views: 16

How to create SQL Server temp tables without collation problems

foxtricks.blogspot.com — Using temp tables in Microsoft SQL Server is tricky when your databases don't follow the server collation. This post explains how to create temp tables while avoiding the use of explicit COLLATE statements in your TSQL code. read more...

add a comment | category: Database | Views: 10