I had the same thought when I upgraded to SQL Server 2005.

I have a TVF to return just the "key" data in my hierarchical tree structure. It uses the...

Jeff Moden (1/8/2008)

---

JohnG (1/8/2008)

---

Definately NOT true. Oracle stores two digits per byte (plus an overhead byte or two for sign, etc.) in a varying storage model. Equivalent to...

Tony Mungor (1/8/2008)

---

I think it is interesting how when push comes to shove you can sell a SQL Server application/solution to an Oracle shop, but there is no way you...

You'll also love the fact that "INT" and all the Numeric data types take up the same number of storage bytes no matter how big or small you define them...

Generally true. You pick your...

The...

Steve Jones - Editor (1/7/2008)

---

I'm not an Oracle guy, but isn't Oracle optimized for cursors? Isn't that it's strength when working through sets of data?

If so, then does it matter...

OK, now we're onto a religious debate.

Having worked since 1984 with relational databases (see bio) -- initially with IBM's DB2 when it first came out (early 1980s) then working with...

My 2-cents on this is that it is probably some unique "quirk" in SQL Server (version unspecified). What version? 7, 2000, 2005, 2008?

I've seen stuff like this before (in...

Jeff,

In SQL Server 2005, sp_executesql is NOT limited to 4K (NVARCHAR(4000)) characters. You can use NVARCHAR(MAX).

The other "unique" constraints are often called "Alternate Keys" (AK in the IDEF1X data modeling notation).

Consider the following simple example:

Countries, per the ISO 3166 specification can be identified by:

- Name...

Always select just the columns that you need.

I've seen more code/applications break due to SELECT * vs. SELECT column1, column2, etc.

The tables in application systems are never permanant. Changes...

I agree with Nebojsa.

Use a return (OUTPUT) parameter as it is a much cleaner solution. You're calling a procedure and not a function. In coding, procedures are not...

Use the built-in stored procedure sp_executesql vs. just plain EXECUTE. Then you can pass your variable as a parameter without having to cast it as a string.

Additional benefits:

- reusable...

Rather than casting/converting all of the WHERE clause values into the dynamic SQL query string you should be using the system stored procedure sp_executesql vs. just plain EXECUTE. The...