Posted from BLInk!
UpdateBatch has been dramatically changed with the current bits (41129) of VS2005. Here are the details on that.
Now that we can exceed the 2100 parameter limit I have been doing some experiments with a 10000 record query from a 104,000 record table and doing batch updates in big chunks. It will be important to tune your batch updates based on the system – location of sql server relative to the application, latency, etc etc. Here is what I hit today when working against a hardwired remote sql server 2000.
Interesting….
Modifying the new CommandTimeout property (from default of 10 to 60) on the DataAdapter’s SelectCommand, fixed this problem. Then I had to change it again for a batch of 10,000. I just popped it up to 120 and that did the trick.
What’s going on of course is that ado.net is building some big goo up front. Prior to this version, it built one big fat query to accomodate the entire batch. But that’s where they quickly (very quickly) hit the 2100 parameter limit. Now watching profiler, it is getting run one update (one row) at a time. I wish I could watch what happens in between, but, really, that’s okay! Can’t geek out too much.
This is the kind of fun you can have on a beautiful winter day with a broken foot. 🙂
A few days ago I noticed that GetDataReader had an obsolete stamp all over it in the online docs. Jackie Goldstein as well as Kawarjit Bedi (from the ADO.NET team) let me know it was just because the name was being changed. I found this warning in the latest bits (November CTP) to be much less alarming than the “obsolete” stamp!
Posted from BLInk!
Hip Hip Hooray! Yippee yi yo ki yay!!
Posted from BLInk!
Posted from BLInk!
turn on your speakers and click on “See the Ad” on the bottom left
Posted from BLInk!
Posted from BLInk!
Posted from BLInk!
Posted from BLInk!
Avonelle points out Joel Spolsky’s comment in a discussion about being a one-man shop and Christopher Hawkin’s response.
Although Joel’s backup logic is bull, I do agree with his main “thesis” – that a consultant is not an entrepreneur. In 16 or so years I have been a consultant, I have never considered myself an entrepreneur or a start-up business, so I don’t even care about qualifying that one.
However, he uses some dead-wrong points to back up that statement. Pure bull.
I am hardly the low man on the totem pole with my clients. I am a business partner – a trusted business partner. The owner of my largest client absolutely sees me that way. I have acquired such a good understanding of his business over the years that it is not uncommon for him to discuss other areas of his business (other than technology) with me and seek my opinion.
Perpetual Job hunting. My very first client came to me as a referral. I had a full time job then and was not even looking for contract work. Since then, almost all of my work has been word of mouth for all of these years. That does not mean that I “put the word out” that I was looking either. I’m talking about totally unsolicited. The only real caveat to this is that when I moved to Vermont, I needed a full time job in order to get a mortgage. At that time, I did have to actively look for a W-2 position.)
Back to work…
Posted from BLInk!