| Author |
 Topic  |
|
|
AskSQLTeam
Ask SQLTeam Question
USA
0 Posts |
|
|
byrmol
Shed Building SQL Farmer
Australia
1591 Posts |
 Posted - 10/28/2003 : 17:40:27
|
I only read the "Overview", but I am impressed.
- Non blocking index manipulation - Excellent..
- Database View - Perhaps a solution to temporal data?
- Database Mirroring - Cheap redundancy!
- Greatly improved recovery operations
- Nice touches to QA!
- XQuery and XML Data Type - BOOOOOH!!!!!!!!
- New CLR Native object model (SML) replaces SQLDMO
- Recursive queries - The Death of the Nested-Set in SQL Server?
- CTE? What the F*$#@ is a "Common Table Expression"
- PIVOT & UNPIVOT - For the cross tab queries freaks...
- APPLY operator? Relational? Hardly... It says "once per each row"... Bit suspect on this.
- BEGIN TRY/ BEGIN CATCH -- THANK YOU
DavidM
"SQL-3 is an abomination.." |
 |
|
|
AjarnMark
SQL Slashing Gunting Master
USA
3246 Posts |
|
|
Arnold Fribble
Yak-finder General
United Kingdom
1961 Posts |
|
|
byrmol
Shed Building SQL Farmer
Australia
1591 Posts |
Posted - 10/29/2003 : 04:46:33
|
Thanks Arnold.. Some good info there.. I especial like the DDL triggers.
DavidM
"SQL-3 is an abomination.." |
|
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
United Kingdom
846 Posts |
|
|
Lavos
Posting Yak Master
USA
200 Posts |
Posted - 11/06/2003 : 22:46:40
|
Yeah, APPLY's run for each row doesn't seem relational, but it's probably as close as we're going to get to a including a rowset sub-query.
I'm really liking some of the enhancements in T-Sql, though I really wish they would've added ANSI temp tables. IIRC, Oracle has them, and it'd save me a lot of hassle.
----------------------
"O Theos mou! Echo ten labrida en te mou kephale!"
"Where theres a will, theres a kludge." - Ken Henderson |
|
|
|
robvolk
Most Valuable Yak
USA
15559 Posts |
Posted - 11/06/2003 : 22:53:18
|
What's the difference between a SQL Server temp table and an ANSI temp table? Is one more (or less) temporary than the other?  |
|
|
|
byrmol
Shed Building SQL Farmer
Australia
1591 Posts |
Posted - 11/06/2003 : 23:08:59
|
This should probably be in the Yukon forum but the "Quick reply feature is just too handy...
With the introduction of XML data types/XQuery and CTE (Thanks Arnold), can anybody guess which is going to be faster for representing/manipulating hierarchies?
DavidM
"SQL-3 is an abomination.." |
|
|
|
Lavos
Posting Yak Master
USA
200 Posts |
Posted - 11/13/2003 : 20:23:02
|
An ANSI temp table is declared as part of the database schema as opposed to being declared inline in a stored proc. At the begining (end?) of a connection it is cleared and you can only see rows inserted on your connection. Obvious benefits follow from having it created declaratively. I hate hunting down temp table creation to update their structures if the schema changes.
You could hack one together using a regular table, @@SPID, and a view, but it's hard to make sure you clear out old rows since there really isn't a built in way to do actions automagically when a new connection is created AFAIK. (and of course, connection pooling can screw this up. Hmmm.)
----------------------
"O Theos mou! Echo ten labrida en te mou kephale!"
"Where theres a will, theres a kludge." - Ken Henderson |
|
|
|
ehorn
Flowing Fount of Yak Knowledge
USA
1629 Posts |
Posted - 11/15/2003 : 10:27:00
|
Graz had made mention of the new varchar(max) datatype
http://www.sqlteam.com/item.asp?ItemID=11986
also AjarnMark
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=21866
and that Varchar(max), nvarchar(max), and varbinary(max) will hold up to 2 GB of data.
Does this mean no more local variable limitations of 8000?
declare @ReallyReallyBigHunkOData varchar(2147483648)
Does anyone have more info on this datatype behavior in Yukon? |
Edited by - ehorn on 11/15/2003 10:57:19 |
|
|
|
robvolk
Most Valuable Yak
USA
15559 Posts |
Posted - 11/15/2003 : 12:00:37
|
You would declare it as varchar(max), and not worry about setting a size:
declare @a varchar(max)
set @a='Hello World!'
select @a |
|
|
| |
Topic |
|
Article: Yukon Details on Technet
