Can you please talk about why t-sql can not add support for classes (pl/sql packages)? It just makes code really long and horribly unorganized.

Why is that I can not include another sql file in a t-sql script (#include..)

Thanks
Ricky

Well I am sure you will get around to this but inner join, outer join, always has a vast amount of confusion, I see questions posted on it all the time, and times I strugle with it.

Also SQL performance, is there a better way to do something like sometime rather than using the IN statement in a where clause? Also what about batching query's Also when you get around to it COMPUTE clause, and FOR BROWSE well they really need a lot of explaining. Oh and just as a suggestion, if it is not too much trouble as I do realise your taking the time to even do this. But when you do examples maybe can you show them against maybe the northwind database, it is just something we all have access to.

Where ever you are going and want to do, unfortunately your not getting a lot of feedback, but I think it is all good. I read your blog so far I really like it ;-)

Why do you have to Deallocate a cursor after you close it?

Do you have any strategies for avoiding Unions?

Why can't I generate more dynamic sql in stored procs? An example would be, why can't I order by with a variable? Or, why can't I use a variable in the "SELECT TOP x?"

Well, I have a complaint. Many people wishes to start using the things with their production servers today, and Microsoft is pushing everything in their next versions. Option pack idea (NT4) was great, customers feel privileged to have some new things in their toolboxes. Pivot operator and Error Handling in Yukon’s TSQL are nice things, that many of us wish to start using asap.

I have always used:

DECLARE @somevar int
SET @somevar = 12

but, I have seen many people use:

DECLARE @somevar int
SELECT @somevar = 12


Which is more effecient?
Which is better?