Monday, August 25, 2003 - Posts

Awhile ago I was discussing with a few other peers on the ASP.NET forums regarding relational and object-oriented databases. In my opinion, it seems as though a .NET programmer would find an object-oriented database more useful than a relational database because you would then be allowed to pass entire objects to the application. However, the only object-oriented database that I'm aware of is called Caché by InterSystems (www.InterSystems.com). I have not had the opportunity to fully test their system. However, I do know some valuable information about the database and .NET development. OO databases allow for objects to be created and then passed between applications. .NET doesn't directly support the Caché database nor any other OO databases. To get the OO database to work with the current framework, you can either use it as a relational database or pass the objects to web services; none of which uses the speed of an OO database. So, it will be interesting to see what OO databases will do in the future. I'm wondering if a future version of MS SQL will contain OO technology. Hmmm...  :-)

with 0 Comments
One of my friends was recently in a job interview for a SQL Admin position. The HR representative in the interview asked him if he ever wrote complicated stored procedures. He told me this and I chuckled. What exactly dictates a complicated stored procedure? I'm interested to see what others would consider complicated, especially if you have an example. Post your “complicated procs” here.

with 0 Comments
Welcome to my SQL blog!

I'm not a SQL expert by any means, but, I hope to improve my knowledge and provide valuable insight to readers. I will be posting some interesting news and facts about SQL. My information might not always be regarding SQL Server 2000 or the upcoming SQL server code-named Yukon, but it will all relate to SQL.

Enjoy reading!

with 0 Comments