Christ, that was quick
So that was Christmas and New Year, was it? I swear the festive period is getting shorter each year. That one only seemed about two days long. Of course, I spent all of it in varying degrees of intoxication*, so I've probably just forgotten the larger part. If not the Lager part. Ho ho.Now it's 2006 and (as many others are wont to do) I've put myself on the wagon for a few weeks. Which is just as well because some
So unless you really want to read all about the fun I'm having with SQL Server Table Variables**, ADO.Net 2.0 TableAdapters*** or the ASP.Net 2.0 Membership & Profile Providers****, I'd say there won't be a lot of posting for the next few weeks.
In the meantime, Happy New Year everyone.
* A nearby boozer sells 330ml bottles of Duvel for £2.40, wheras a pint of Guinness is £2.75. Duvel is 8.5% alcohol by volume so... Oh, you do the sums...
** Fantastic idea, those. Precisely what the Doctor ordered. In-memory #temp tables. Just the job for iterative queries, which in this particular case is a real life-saver.
*** A good idea and certainly saves some coding. But what about stored procs that return multiple resultsets, eh?
**** Great idea, it seems like a lot of plumbing to get them working though. I guess they save poncing about with login forms though. The strong typing of Profile properties is nice, too.
2 Comments:
It's funny you should say that. I've been hoping you'd write a post on how to use SQL Server 200 table variables to eliminate the need for cursors.
Don't encourage me. I'm feeling almost motivated to do so at the moment. I think there's probably a great demand for blogs about .Net development and bowel movements.
Post a Comment
<< Home