- Endpoints based on transport and protocol
- The security model changes a bit. SQL Brower Service is separated out
and can be stopped without stopping SQL Engine
- Discussion of how the login process works
- Standard SQL Logings
- Enforcement based on strenght, expirations and lockouts
- Follows local NT password policy on Windows 2003 Server only
- Talked about using SSL encryption
- User and Schema Separation
- Principal is essentially the users context, schema is the collection
of objects
- So instead of an user own objects, schemas own objects which can be
owed by a user.
- Not all users need to own a schema. This separation allows for
lower-privledge
- sp_CreateLogin becomes Create Login
- BLUE SCREEN OF DEATH! Oh no!
- Yukon will allow an "impersonation" context for certain activities
Due to the on-going problems with the presentation and depth of the
materials, I'm going to stop gathering notes here and
point
you at this instead.
Very interesting, the room is packed and SRO.
- Vision statement
- Provide an open "standard" based access path to SQL Server
- Outreach
- Interoperability
- Essentially collapsing the SQLXML stack into the server
- Relies on HTTP.SYS so its only a go on XPSP2 or Windows Server 2003.
- Basic work is to expose a stored procedure as a web service end point
(sometimes called RPC Access) and "Batch Access." WSDL requests are also
support (duh!)
- Gave an in-depth example of creating an endpoint
- All access to SQL Server must be authenticated in some way.
- Walking through the WSDL and a drill into the depths of that. Man, I'm
glad I don't have to write that!
- Even longer walk through of generating WSDL by hand.
Gave up on this session after this. While it was informative, it moved a bit
too slow for me too.
Okay, one of the top sessions I've been waiting for. Go Mark go, go Mark go!
- Talked about the XML as cardboard analogy -- the origami of XML.
- Version 2 themes
- Performance
- Usability
- XQuery and XPath
- XML <> ADO.NET
- XML tools in Visual Studio
- Use XMLTextReader whenever possible
- Talked about new features
- Read node as type (e.g.
XmlConvert.ToDouble(reader.ReadElementString()); becomes price =
reader.ReadAsDouble()
- Static reader rather classes of readers. Think about a Factor method
for Readers and Writers. Much easier to parse and validate while
streaming. Mark did a couple of good demos.
- Security bits around XSLT
- Type Writters
- Default implementations of base XmlReader and XmlWriter classes
- Good walk-through demo
- Showed using ReadValueAsList as an element value parser. Very
nice.
- Use XmlDocument with care. Use it only if you are going to query with
XSLT or XPath. Keep in mind that most of the time XPathDocument might be a
better choice. (consider it the primary replacement)
- In V2, in memory validation is enabled
- XQuery supported in the framework.
- XmlReader and XmlNavigator can be latched on to for an XmlDocument in
V2.
- XPathEditableNavigator, which exposed using an XmlWriter and have IUD
events and long with change tracking
- Good Mort-level demo of this for inflating book prices.
- V2 Adds XSLTCommand Class and XQueryCommand class
- Xpath for query, XSLT to transform XML
- XQuery
- Made the XQuery:SQL as XML:Database
- XQuery is essentially a superset of XPath (at a fairly high
level)
- Talked about FLWOR with a nice demos, especially joint T-SQL and
XQuery demo.usng sql:query()
- XSLT in V2 essentially emits IL, as previously mentioned thanks to
that XSLT debugging
- Remember that although XQuery and its embedded support is essentially
read only, but you could used OpenXML to do the updates if memory serves me
right.
- Talked about the XML Tools in VS2K5
- XML Editor with correctness and syntax checking and Intellisense if
the document has a bound schema.
- Step through debugging of XSLT baby, I can't wait.
BTW: Today's posts in Pink since Pink is the new Black
"I just want to start staying yes." What a cool concept. Speaker is Andy
Lees, the VP of Servers and Tools.
- Mix today: 70% support of what is, 30% support of what will be. Want to
drive that mix more to 50%/50%.
- Thee aspects of Windows Server System: Ops, App Infrastructure and
Information Work Infrastructure.
- Announced Common Engineering (CE) Roadmap and CE Criteria 2005
- MOM is the driver for system administration (MOM drives Exchange)
- Architectural Guidance for core usage scenarios
- Web Services for administration
- Windows Server System Infrastructure Environment like PAG for ITPro
- 10 years of support of the portfolio of business products
- Newsgroup integration in Visual Studio Help
- Discussion of MS Best Practice Analyzer and SQL Server 2005 Data
Encryption
- MS is running 99.9996% OS Uptime.
- Ilya Bukshteyn and Jon Rauschenberger from Clarity talked about
configuring Email access with ISA
- Nice demo of the ISA Email Configuration Wizard. Maybe a dozen
clicks to do that.
- Demo of the VPN connection wizard. 5-clicks in total. Nice.
- Quick demo the DFS/FRS enhancements in W2KSrvR2 and "Remote
Differential Connection." Very nice indeed.
- New version of MSBPA has a Yukon readiness analyzer
- Talked about native data encryption, but no real drill-through.
- Talked about Client Inspector and Isolator
- Machine connects to an isolation network
- Machine inspected
- Updated and authentication as needed
- Talked about WUS as a single update point and should have rollback
- 66% of e-mail is SPAM
- Talked about Exchange Intelligent Mail Filter (runs on server)
- Talked about CallerID
- Will be part of Exchange Edge services
- Free SMS 2003 and MOM 2005 Express for all Attendees. Also free copy of
services of Services for Unix.
- Quick overview of Windows SharePoint Services and Portal Server
- Good overview of Federated Identity using Web Services
- Talked about Anywhere Access which like a SMB-over-HTTP
Title: Yukon SQLCLR: How do we all get along?
Location: Room 15B
Time: 8:30 PM
Developers: Are you worried that you won't get to use all of the features and power that SQL Server 2005's (Yukon's) CLR Integration features bring to the table? DBAs, are you worried about what those crazy developers are going to want to do with the SQLCLR? What about those of us who live in both worlds? Rather than fretting and fussing about it, how about we get together and start building some understandings, commonalities and shared visions?
Seems like mountain climb, right? Well, every voyage up a mountain must begin with first steps and that's really what I'm shooting for -- what are the first steps we need to take. To help find that path, I'm planning on just asking these five questions tonight and seeing that discussion we get:
- Developers: What specific features of Yukon do you feel you are most like to use and why?
- DBAs: What are your concerns about the usage of those features and why?
- Both: What ideas do you have for resolving those issues and how would you implement them?
- Developers: What are the big picture issues that you want the DBA to keep in mind going forward?
- DBAs: What are the big picture issues that you want the Developers to keep in mind going forward?
There's only one rule that I'd appreciate it if we could follow tonight:
- While you may disagree with what somebody has to say, respect the person as your peer and partner.
Thank in advance for attending!