t-sql
SQL Azure Incompatibilities list
While 99% of what you do in SQL is supported in SQL Azure, there is a small list of things you'll have to redesign, or at least reconsider before implementing
t-sql
While 99% of what you do in SQL is supported in SQL Azure, there is a small list of things you'll have to redesign, or at least reconsider before implementing
Posted in: Microsoft SQL
How many of you have heard me rant against using "SELECT * FROM tableName"? If you have I'm sure you've heard me mention the following reasons why SELECT * is
dev
Microsoft continued their support of PHP by releasing a Community Technology Preview for the SQL Server Driver for PHP 2.0. With this release PHP developer can
dev
I'd like to introduce you to the idea that you can replace an equal sub query with an exists sub query. Doing this can change a seek operation to a scan
microsoft sql
Over at Experts-Exchange, I saw a question I get every once in a while. It all has to do with how SQL Server orders data in a VARCHAR column. SQL Server
microsoft sql
When converting a database from an older version of Microsoft SQL to Azure, there will be many gotchas along the way. I'd like to help you learn from the
t-sql
I'd like to start a new series that will help you learn some of the techniques I've used in the past. Some of these techniques are useful, some aren't. Using
t-sql
Consider the CREATE INDEX statement below: CREATE INDEX ix_tableName_columnName ON tableName (columnName) ON { partitionSchemeName (columnName) | fileGroupName
t-sql
I know I've covered quite a bit of the CREATE INDEX statement, but there is even more to learn. Today I want to cover ASC, DESC, and the WHERE clause for
dev
FILLFACTOR specifies the percentage for how full the Database Engine should make the leaf level of each index page during index creation or rebuild. FILLFACTOR
t-sql
I picked up this book as an introduction to the new geographic datatype in SQL 2008. I had played around with Google maps, and plotting WiFi hotspots I'd
t-sql
I've shown you how to create indexes, CLUSTERED versus NONCLUSTERED indexes, today I want to build on that. Let's say you have a lookup query that takes names,