Browse by Tags

Just a quick plug – tomorrow evening I’m doing a session on ADO.NET Data Services (“Astoria”) at the SQL Server User’s Group at Microsoft, Reading. See here for details; http://sqlserverfaq.com/events/167/Sessions-on-Understanding-ADONET-Data-Services-Windows-7-features-indepth-and-the-usual-SQL-Nuggets-and-Networking.aspx it’d be great to see you there.

A big thanks to all the people who came along to my session at SQLBits today on ADO.NET Data Services and also to the organisers and community around SQLBits that made the event happen in the first place. I was there for most of the afternoon and it seemed like a fantastic event to me in a cool venue. As promised, my slides from the session are here for download – you’ll perhaps notice that there are a few additional (hidden) slides in the slide-deck that I didn’t use in this talk as I collapsed this talk down from an earlier talk and updated it to reflect the RTM version of Data Services and also the various CTPs/Previews that are currently kicking around. So…you get a little more than I actually used at the conference. Enjoy :-)

Following on from that previous post about the WPF DataGrid I thought it might be interesting to try and move towards more of a master/details view with a separate grid displaying the orders for each customer. I modified the UI a little bit; < Window x:Class ="BlogPost.Window1" xmlns ="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x ="http://schemas.microsoft.com/winfx/2006/xaml" Title ="Window1" Height ="600" Width ="800" xmlns:grid ="http://schemas.microsoft.com/wpf/2008/toolkit" > < Grid > < Grid.Resources > < Style x:Key ="myStyle" TargetType ="{x:Type Control}" > < Setter Property ="Margin" Value ="10" /> < Setter Property ="FontSize" Value ="16" /> </ Style > </ Grid.Resources > < Grid.RowDefinitions > < RowDefinition Height ="Auto" /> < RowDefinition Height ="2*" /> < RowDefinition Height ="2*" /> < RowDefinition Height ="Auto" /> </ Grid.RowDefinitions > < TextBox x:Name ="txtCountry" Style ="{StaticResource...

Someone asked me if I had a simple sample of how to read/write documents into a database table using FILESTREAM in SQL Server 2008. I set about it. Firstly, I had to find out how to switch FILESTREAM on in the RTM of SQL Server. At times like this you need Bob Beauchemin to tell you how it's done and then you can go and run code such as this once you've done the necessary bits in SQL Configuration manager; exec sp_configure filestream_access_level, 2 reconfigure go CREATE DATABASE Documents ON PRIMARY ( NAME = DocData, FILENAME = 'c:\temp\docs.mdf' ), FILEGROUP FileGroup CONTAINS FILESTREAM ( NAME = DocFiles, FILENAME = 'c:\temp\docstreams' ) LOG ON ( NAME = DocLog, FILENAME = 'c:\temp\docs.ldf' ) GO and now I've got a database that can accept file stream data. Phew. Time for a simple table; create table Docs ( id uniqueidentifier rowguidcol not null primary key , documentData varbinary( max ) filestream not null , documentName nvarchar(1024) not null ) Now I've got a table I can use something like Windows Presentation...

The UK, SQL Server User Group has Michael Rys delivering a talk on Monday in London. Michael's a Program Manager in SQL Server. Go here for the details and to sign up. I don't know Michael personally but I know that back when I was looking at SQL Server 2005 and I asked any kind of question about the new XML data type it was more-often-than-not an email that came back from Michael with the answer in it so you should be in for a treat if you manage to get yourself signed up for this.

Matt Warren has an "interesting" post on how you could hack your way to a mocked implementation of LINQ to SQL - if I had a pound for every time someone's asked me how to do this then I'd have at least 3 pounds :-) Seriously though, there is interest in doing this kind of thing and it's a good starting place if you're inclined to head down this route.

I had a discussion at DevWeek about when SqlDataReader.Read () gets called for resultsets coming back from stored procedures accessed with LINQ to SQL. I've got this stored proc; create procedure dbo.GetCustomersByCountry @country nvarchar( max ) as set nocount on select * from dbo.customers where country = @country and I've brought it into LINQ to SQL using the designer and that means that I can write code such as; using (NorthwindModelDataContext ctx = new NorthwindModelDataContext()) { var query = ctx.GetCustomersByCountry( "UK" ); foreach (Customer c in query) { Console.WriteLine(c.CustomerID); } } Question is - when does SqlDataReader.Read() get called here? Do we read all of the data up front and then just provide access to an in-memory collection or is the data read from the wire as the loop iterates over it? I wanted to check so I went ahead and set some breakpoints in a few places; Inside the constructor of my Customer class. Inside SqlDataReader.Read() and what I see there is an interleaved set of calls...

Just a quick plug :-) I'm speaking at the "SQLBits" conference in Birmingham on the 1st March. The agenda is up here . The agenda is built by voting from prospective attendees and I found it interesting in that I submitted a few sessions that looked something like; "Entity Framework Tour" "LINQ to SQL" Tour "LINQ to Entities" Tour (this is similar to the first topic but with a very different emphasis) "Understanding LINQ" and what surprised me is that the last session was the one that got picked despite it being the session that I'd say is least directly related to SQL - i.e. you can quite happily have some LINQ without bothering with a relational database. So...if you can make the date and the location then sign up for SQL Bits and I look forward to seeing you at my session if it appeals to you. As an aside, if there's something that you'd like to see included in a session like "Understanding LINQ in .NET Framework V3.5 and Beyond" then feel free to ping me a mail letting me know what it is that you want to see...