Featured Article(s)
Troubleshooting SQL Server 2005 Database Mail Problems
In this article, Alexander Chigrik explains some problems that you can have when you work with SQL Server 2005 Database Mail. He also tells you how you can resolve these problems.
Thanks To Our Sponsors
We’ve worked with some great companies this year! We really appreciate their support and help in bringing you SSWUG. Over the next few days I’ll be bringing you a list of the different sponsors, big and small. Take a moment and check it out – there are some outstanding products here!
Confio – Confio Ignite optimizes database performance fast
ConvertU2 – Access to SQL Server Conversion Systems
DataDirect Technologies – The World Leader in Data Connectivity
DBA24Hrs – Remove the mundane from SQL Server Management
dbMaestro – Change and Configuration Management
DBNetLink – Free your data with DbNetGrid
dbOrchestra – Gourmet DB Development that is affordable
Feedback on 1.000 Versions
Some final feedback on using version 1.000 of a product, specifically the updated suite headed our way in 2008.
Larry: "Visual Studio 2008 I think is a no brainer to use. Lots of IDE improvements and there have been substantial enhancements but if there are bugs there’s always the Visual Studio 2005 feature set that can be used. SQL 2008 I think we’ll be waiting a bit on. SQL 2005 might have been smooth for others, but it was the hands down the worst release with the most bugs I’ve seen since 1996. I had to learn to open support cases with Microsoft and use it fairly often, all since the release of SQL 2005, not a trend I’m pleased to see."
John: "We are digesting the SQL Server 2008 CTP presently. We will begin to deploy SQL Server 2008 in the 3rd quarter of 2008. I’m sure that will predate SP1."
Mike: "We always wait until the first service pack comes out. Unless our application teams indicate they need something out of the next release, in this case SQL 2008, we will not change for change sake."
I guess the net-net here from all of the responses is essentially:
– Visual Studio – go for it.
– SQL Server 2008 – if features are needed, go for it (after testing)
– SQL Server 2008 – no features needed, test, be cautious, hold if possible for SP1
– Windows 2008 – no rush to implement. This is the most cautious tone of the messages I’ve received.
I think it comes down to how core a given product is – and that dictates the specific levels of caution. The OS is the intricate, most core functionality of the system, therefor the most caution is applied to this update (it’s probably the most difficult too). SQL Server is next, of course, then the development tools.
2008 will be interesting, that’s for certain!
Featured White Paper(s)
Enterprise Strategies to Improve Application Testing – Optimized Test Environments Speed the Deployment of Reliable Applications
Today’s applications drive revenue and satisfy sophisticated marketplace initiatives. These customer-facing and mission-criti… (read more)
A simple solution to scripting when sysdepend is damaged
Damaged dependency information is a common problem when a database has a reasonable number of objects. This article explains … (read more)
Business Rule Mining: Get a Detailed Analysis of your COBOL Applications
LogicMiner can help your organization reduce maintenance costs and prepare for ongoing modernization of legacy applications. … (read more)