How to use Database mail feature in SQL Server 2000

  • Comments posted to this topic are about the item How to use Database mail feature in SQL Server 2000

    M&M

  • Nice Article.

  • most of us are still working on older, SQL Server 2000 servers

    Are there any statistics on this?!

  • As a freelancer most of the sites I work at are still extensively 2000, with a few 2005 servers. Almost all the businesses I've worked with are still only just considering converting to SQL 2008, as the general consensus among big business (and especially local government) in the UK seems to be "if it works, leave it alone".

    So from personal experience I would say 2000 use is still extensive.

  • Nice workaround, if you do have SQL 2005 indeed. Thus, why not to migrate your SQL 2000 dbs to SQL 2005?

  • myxdev-apps (3/9/2010)


    Thus, why not to migrate your SQL 2000 dbs to SQL 2005?

    Lots of reasons. The business may not see a requirement to migrate the database, there may be elements that won't convert easily, they may not sanction the development time to re-write stored procs or convert hundreds of DTS packages. I've run into all these and more as reasons why companies don't migrate databases.

  • Andeavour (3/9/2010)


    myxdev-apps (3/9/2010)


    Thus, why not to migrate your SQL 2000 dbs to SQL 2005?

    Lots of reasons.

    Yes. I was wondering about the article, not your post, but the other side, those small companies thata can't afford a new SQL Server.

    I agree with you that many companies won't upgrade their SQL 2000 for all it implies to them.

  • From the article:


    It might take a few more years before all of the existing SQL Server 2000 applications are upgraded to newer versions of SQL Server.

    SQL 2000 SP4 drops out of the extended support phase in April 2013. After that MS won't be doing any security patches, so security holes won't get fixed and your enterprise is at risk. So you need to be planning on upgrading within the next 36 months. http://support.microsoft.com/lifecycle/?p1=2852

  • RE : SQL 2000. I've been telling a client for more than 6 months that they should upgrade their server and move to at least SQL 2005. This week the 10 year old hardware failed. they are now upgrading by default 😀

    Developer, DBA, Pre-Sales consultant.

  • I still have to support a SQL 2000 instance for a vendor application that the business can't afford to upgrade at the moment. The new version of the software is a hosted system and very expensive. The current version does not support any SQL beyond 2000.

    I don't find configuring SQL Mail on SQL 2000 to be very difficult, but it's nice to know there are options.

    Aigle de Guerre!

  • Nice trick for using Database Mail in SQL Server 2000. I must admit I was wondering how you were going to do this when reading the title.

  • jinlye (3/9/2010)


    From the article:


    It might take a few more years before all of the existing SQL Server 2000 applications are upgraded to newer versions of SQL Server.

    SQL 2000 SP4 drops out of the extended support phase in April 2013. After that MS won't be doing any security patches, so security holes won't get fixed and your enterprise is at risk. So you need to be planning on upgrading within the next 36 months. http://support.microsoft.com/lifecycle/?p1=2852%5B/quote%5D

    Yes. 36 months = 3 years, which handily falls within the range of "a few more years". 😛

    Still, it's good to have a deadline, and better to be done well before it!

  • vk-kirov (3/9/2010)


    most of us are still working on older, SQL Server 2000 servers

    Are there any statistics on this?!

    Hi VK,

    I wrote this because most of my colleagues are still working on SQL server 2000. Not sure, when they plan to migrate to 2005 or higher.

    Moreover, in my company, this purely depends on management. We can remind them often but finally they decide based on budget etc.

    M&M

  • This is a great article. Do you have any comments on the security side of things here? We have to follow the CIS procedures that 'outlaw' SQL Mail. Does this workaround have any security implications?

  • mohammed moinudheen (3/9/2010)


    I wrote this because most of my colleagues are still working on SQL server 2000. Not sure, when they plan to migrate to 2005 or higher.

    Thank you for your clarification.

    mohammed moinudheen (3/9/2010)


    Moreover, in my company, this purely depends on management. We can remind them often but finally they decide based on budget etc.

    Such a familiar situation 🙂

    Thanks for the article, it is a nice example of using new features in old environment 🙂

Viewing 15 posts - 1 through 15 (of 64 total)

You must be logged in to reply to this topic. Login to reply