SQL Server 2005 Paging Results to show how to do page request queries

http://www.codeproject.com/script/articles/list_articles.asp?userid=1163927

The text books and course work (OU MS221) don't really make clear the relationship between different sequences of fibonacci numbers.

Fibonacci numbers

n        0   1  2   3   4   5    6   7    8     9   10   11     12   13  
Fn      0   1  1   2   3   5    8   13  21   34  55   89   144  233 
Fn+1  1   1  2   3   5   8   13   21 34    55  89  144   233
Fn+2  1   2   3  5   8   13  21  34  55   89 144  233
Fn+3  2   3  5   8  13  21  34  55  89 144  233

We can see  Fn = Fn-1 + Fn-2   ( example F5 = 5 = F4 + F3 = 3 + 2 )

So
       Fn+1 = Fn + Fn-1         or Fn = Fn+1 - Fn-1

      Fn+2 = Fn+1 + Fn

     Fn+3 =  Fn+2 + Fn-1   

using Fn+2 = Fn+1 + Fn

    Fn+3 = Fn+1 + Fn+1 + Fn

This can be expanded in Fn+4...etc.. so All Fn+m can be shown in terms of Fn+1 and Fn

Swung passed the Yam dealer today and picked up a battery for the bike. Filled with acid, quick charge then fitted it to the bike. Alarm went a bit OTT with new battery and fob decided not to work for a bit; so fitted that with new battery later. After a few attempts it roared into life. Amazing and exciting feeling seeing it working after sooo many long months in storage. Need to get it clean and start checking all the bits that will need checking and have to check brake fluid hasn't assorbed air/water leading to spongy brakes.

Also called DC to arrange a trip out

Everytime a new Visual Studio install is done we all forget how to setup VS again and scrabble google to find the anwser. This is a guide I put together for a developer that was struggling. The first section I nicked form a blog and forgot which one...I'll give you due credit if I knew who you were.

Error while trying to run project: unable to start debugging on the web server
One main reason for not anle to start debugging is Having VS2003 and VS2005 on the same machine.
In that case please change the framework version to enable your debug
1: Start -> Run -> inetmgr
2: Navigate to the virtual directory of the project which is throwing this error.
3: Right click on the virtual directory and choose "Properties"
4: Choose the tab ASP.NET
5: The first dropdown would read "ASP.NET Version", choose your framework

Then if it still doesn’t work register IIS with ASP.NET
1. Jump to DOS prompt
2. Change directory to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 (or very similar)
3. run command: aspnet_regiis –i

Then try this msdn arctile if the aboves doesn’t work.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vsdebug.asp

Roadshow

http://www.microsoft.com/uk/techroadshow2007/msdn/default.mspx

Daniel Moth Blog

http://www.danielmoth.com/Blog/

Mike Taulty Blog

http://mtaulty.com/communityserver/blogs/mike_taultys_blog/default.aspx

The road show was pretty good and LINQ was the most significant technology shown.

Part one was Language Enhancements and LINQ in the morning with Daniel Moth
and part two in the afternoon  Advances in Data by Mike Taulty which was advanced LINQ (and other stuff).

LINQ

Allows you to run SQL type queries against Objects, Collections, XML, Datasources, Datasets.
You can even use joins between different datasources. This was not explained in depth.

One of the cool things is that you can make changes to db objects then abandon them before they are saved to the database.

Even cooler if you load data from a db table change it but not save to the db , run a different query using the same record from the first changed set of data. It will return the unsaved data from the first query rather than the db version. This might not be a good or a bad thing.

Another surprising thing was that he pulled the customers table with a filter on one customer from this he was able to pull other information from other tables (orders etc) based on the db relationships of the customer table. What happens to your build if you make small db schema changes I have no idea.

The examples where flat on NorthWind db with little Sproc involvement so working on large frameworks would also need a serious evaluation.

Pros
Very flexible, powerful and can cut out a lot of the dal work that is currently done.

Cons
Like all stuff, you can really write some truly awful code and it blurs the lines between tier modelling as you can effectively cut out the business logic or at least pull it into the presentation layer (you can do this now). There was a cringe moment where he was using a db connection dropped to the desktop (this is a major no no with me).

You also have to watch what you are doing as you can easier request 10million records form the db with careless code.

Running the same query; you can also iif you’re not careful run the same query over and over rather than locally can

How does it work with a truly normalised db with a strong sproc base was not made clear.

Warning
Don’t run this on as production machines it will break them. Although it says it won’t break them on the ms sites it will.

Summary

LINQ will be with us for ever or will be killed off in a few years and I’m not sure which. I see huge advantages but I also see a potential of developing a major mess of an application and some very interesting debugging.