Check Out SQL Server 2005 (YUKON)
lots of good stuff to reduce development time, such as seamless debugging
through you r .NET code into the SQL Server stored procs and back out again
Thats juts one thing, there is a mass more!
Most of My .NET work has been with an Oracle back end but I can see teams
moving to SQL server 2005 purely for ease and speed (hence cost) of
development
hth guy
"mscertified" wrote:
chat are the pros and cons of using SQL Server or Orable as the database for
.NET applications. I'm interested in the current environments and what may be
coming in the future from Microsoft. In other words, are there any .NET or
SQL Server developments in the orks that might tip the scale either way?
