Totally agree!

But I think it must include : "Learn Transaction isolation levels/SQLServer Locking behaviour".

Maybe as subarticle for "Tuning".

You may have well-tuned stored procs that work fast only in test environment,...

>>EBD is open source

EDB is not open source. Now they're just "cheap Oracle"

>>How is this different from SQLExpress?

Differences:

1. EDB challenging not free versions, they're trying to challenge enterprise...

Even more: they (EnterpriseDB) are targeting not only Oracle.

Read this blog article

They're now offering Oracle-compatibility layer named "Redwood" mode.

And : "At the same time, they are looking...

I'm still thinking that passing XML-parameter is the best.

You have ability to pass not just array but a TABLE and even resultsets of several tables.

Look at :

1. DTS. Options "Fast_load" and "rows per batch".

2. If you're a programmer (even just a little bit) - look at .NET 2.0...

Maybe XML is what you need?

We did so in 2K with

1.sp_xml_prepare_document -

2. OPENXML

3. JOIN with resultset of OPENXML ( IN (SELECT...

As developers we MUST upgrade to Yukon.

We will have another headache - in near future we will have clients working with different versions of our system.

Just as we had...

Great article!

>>Function based indexes are something Oracle has had for years, I'd like to see MS do a bit of catching up there.

Indexes on calculated fields?

I have never use them....

I cannot believe when I read "SELECT INTO is BAD"

SELECT INTO is one of BULK operation.

In case of large datasets there are no other way then to use one or...

The most laughable in all this initiatives - I'm sure that companies lost more than obtain.

For Sony - anyway, I didn't listen music they produce.

For Microsoft - most of...

Stanislaw Lem "Summae Technologia", "Cyberiada", "Ion Tichi"

Ph.K. Dick - maybe everything

I'm tend to agree with Chris Smith.

Such design bad for OLTP, but in most cases good for OLAP.

Not for OLAP exactly, but for database containing fact tables for OLAP...

I prefer a lesser changes between versions and lesser development cycle.

Yukon - have amazing features.

But now adoption our system requires a lot of time.

And then upgrade on clients' servers...

It's a much better approach than using recursion as it is the most direct approach to do it. TSQL, even using recursion, would still have to do the string...

Something bad like this:

CREATE TABLE SourceTable(

_Name varchar(10)

,_Text varchar(10)

,id int IDENTITY(1,1)

)

GO

INSERT INTO SourceTable

(_name, _text)

SELECT 'Matt', 'Hi'

UNION ALL

SELECT 'Matt', 'How are'

UNION ALL

SELECT 'Matt',...