I find it alarming that some modules do not support SQL Server 2000 when DNN 4.x and 5.x do. I know SQL Server 2005 and 2008 have some extra functionality but they aren't something that can't be totally done in 2000 or have a workaround.

What SQL Server functionality the module developers need beside CRUD operations where they don't mind excluding SQL Server 2000 customer market? There are DNN hosting companies out there that still support SQL Server 2000 only.

> Mainstream support for SQL Server 2008 has been terminated by Microsoft effective April 2008...

Blimey if that's the case I'm going back to SQL 2000 .

Sebastian

Your software development should not coincide with what Microsoft is doing. If MS stops support SQL Server 2000, your SQL stuff will still work. You really do not need MS's support to develop for SQL Server 2000. 2000 is a mature product and has gone through at least 5 service packs. It's very unlikely you will discover a new bug after all these years. Otherwise tell me what do you need MS's support for in particular?

If MS stops supporting Windows XP, your decision to make your software not work on XP is a very bad idea because I am sure XP will still be very popular for many years.

What I was asking was what featuers such modules truly need? nvarchar is supported by SQL Server 2000. I don't know what MAX does exactly. One can specify the size in 2000.  Also if DNN can use SQL Server 2000, my suggestion is that modules should also do the same so they can work hand in hand instead of  module jumping ahead and breaking compatibility.

So my adivce is that odule users should be aware of what the module supports and not assume that if DNN supports SQL Server 2000 that all modules automatically support it too.