Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Misc. Issues » SQL Server 2005   (RSS)

Introducing Multiple Active Result Sets (MARS) (2)

MARS is a powerful tool, but you may shoot yourself by the foot if you don't use it correctly. In the following several talks, I will talk about how to use MARS safely. This talk will cover the session/request context management. In later talks, I will
Posted by pingwang | 2 Comments

Predicate ordering is not guaranteed

A typical programmer may expect that the predicates are always evaluated in the order that they are specified, but this is not true in database systems. For example, for the following clause, where col11 = 5 and convert(int, col2) = 100 programmers may

Introducing Multiple Active Result Sets (MARS) (1)

MARS is a new programming interface introduced in SQL Server 2005. It enables multiple result sets to exist at the same time for a given connection. To say it in a simple way, you can make a connection to server and then submit multiple requests to server
Posted by pingwang | 0 Comments

SQL Server Identity column FAQs

Q. How is identity values generated? Does SQL Server internally use lock as synchronization mechanism? A. Identity values are generated in-memory using light-weight synchronization, i.e. Spinlock (roughly speaking, Interlocked* function with yield). When
Posted by andrewz | 2 Comments

Name resolution, default schema, implicit schema Part IV

This post will talk about implicit schema used in compile plan and conclude the topic of Name resolution, default schema, implicit. A compile plan may refer to non-qualified schema object. It needs to record that fact an “implicit” schema is used (Name
Posted by andrewz | 0 Comments

Name resolution, default schema, implicit schema Part III

It is time to cover name resolution algorithm in SQL 2005 for objects. [ Algorithm] In a nutshell, objects name resolution follows the same rule as types and XML schema collections. However, SQL Server name resolution and execution context used to have
Posted by andrewz | 1 Comments
Attachment(s): Name Resolution.doc

Name resolution, default schema, implicit schema Part II

Last section clarified some background, let us continue with Name Resolution Algorithm for Types and XML Schema Collections [Algorithm] As implied by general syntax for referencing entities, types or XML schema collections cannot be referenced across
Posted by andrewz | 0 Comments

Name resolution, default schema, implicit schema Part I

This series of blogs describe name resolution behavior of schema objects, types and XML schema collections, and how it interacts with default schema, compile plan implicit schema. The first part will lay some background so that we are at the same page.
Posted by andrewz | 2 Comments
 
Page view tracker