Rants Tagged with “Databases”
<< < 1 2 3 4 5 > >> (Total Pages: 5/Total Results: 47)
If you upgrade to RC1 be aware that SQL Server 2005 requires SP2 before it will work with Vista RC1. Yeah, I know there is no SP2...but that's the case. It just doesn't work. I am trying to hack around the problem so I'll let you know if I find a solution...
I was talking with a bright guy inside the ADO.NET team today when he told me that the DbCommandBuilder supports a new option called ConflictOption. This option alerts the DbCommandBuilder to use one of three methods for detecting concurrency conflicts:
- CompareAllSearchableValues: The 1.x behavior of comparing all values to make sure the row hasn't changed.
- CompareRowVersion: This compares the primary key and a timestamp field (or rowversion). This only works if the table has both a primary key and a timestamp (or rowversion) defined.
- OverwriteChanges: This only compares the primary key and does not provide any concurrency, but simply allows for overriting of data. *I DO NOT SUGGEST YOU USE THIS*.
Unfortunately, the TableAdapters in Typed DataSets (v 2.0) don't seem to be using this when they create their concurrency (the TableAdatper code generator uses a DbCommandBuilder to create the Update/Delete statements).
Additionally, the ASP.NET 2.0 DataSources do not use DbCommandBuilders so they won't use timestamps to do currency at all. But my rant about DataSources is for another day.
If you're in Atlanta and want to see me talk about the SQL Server CLR Integration, come by the Atlanta C# Users Group on May 1st (That's today). Meeting starts at 6pm. Here's a link to the User Group's Site:
http://www.atlantacsharp.org/NextMeeting.aspx
Since my announcement last year that there would not be an update to my book ("Pragmatic ADO.NET") to show the changes in ADO.NET 2.0, I have been asked what book I would recommend. I have scoured the ADO.NET 2.0 books and finally have a firm recommendation:
Pro ADO.NET 2.0, by Sahil Malik
While it is not the book I would have written, it is a very good book. It covers ADO.NET 2.0 very thoroughly and in a very readable manner. If you need an ADO.NET 2.0 book, go get this book today.
In a current project I am working on with a distributed team, we use a set of detached database (mdf/ldf) files to keep current the latest version of the database we're working on. I use SQL Server 2000 and 2005 on my local dev-box, but since this customer is going to use SQL Server 2000 I've been trying to keep the work on SQL Server 2000.
No real problem so far. One of the dev's on the project only has 2005 installed, but this isn't that big an issue and I've seen no compatibility problems so far...except...
One issue is that if you attach a detached database (mdf/ldf) to SQL Server 2005 it can *never* be re-attached to 2000. You must transfer the data back to 2000 if you need it there. Unfortunately the dev that is using 2005 made some schema changes. Ho hum...what to do.
SQL Packager has yet again come to the rescue as I used it to copy all the changes from the 2005 to 2000 with no problems. This saved me hours of time manually finding and making the changes. I simply created a database "update" project and used my 2000 database as the base and the 2005 server as the changed server. It just worked. I love when that happens.
Big props to SQL Packager for saving my day.
I am currently doing a bunch of evaluations on OR Mappers, Code Gen and Business Object Frameworks for my new book. If anyone knows about anything great that might go unnoticed, please drop a comment or send me an email!
Thanks!
I've talked with lots off prospective authors the last few years since my first book came out. I've tried to do what Chris Sells did for me, scare them... I've explained that it is long hours, lots of dedication and can get in the way of family time. I sure don't take my own advice very well. I've agreed to write another book, "Prescriptive Data Architectures" for Addison-Wesley. Unlike the first book (pre-blog craziness), I plan on using this blog to discuss my experience writing the book as well as a sounding board for my ideas that will be used in the book.
So, why am I writing the book? In my user-group talks and work with customers, I get a lot of questions about what data architecture is right for them. If you read my first book, you might assume that I think that DataSets are right for every project. I do not. I have found that answering the 'right architecture' question is a complex one that involves business, functional and techinical requirements. My goal with the book is to help readers understand their projects. Armed with that knowledge, they can make informed decisions about which data architecture makes the most sense for their project. This is something I have a passion for. That's why I am writing the book.
The book will be in the same Addison-Wesley checkerboard series that my first book was in and is expected to ship in January 2007.
For all of you who have wanted to use DB mirroring in
SQL Server 2005, you'll have to wait a bit more. This letter from the product team might help you understand why, it didn't for me ;)
The latest drop of
SQL Server 2005 is now on MSDN for subscribers. Curious thing...its a September CTP, not a RC. Anyone else think its going to slip past the November ship date (I doubt that
Visual Studio will, but i'll let you know what I see when I get it installed).
Check out this interview I did about databases and where data is headed!
