Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why some module developers do not support SQL Server 2000?Why some module developers do not support SQL Server 2000?
Previous
 
Next
New Post
3/3/2009 4:56 PM
 
Jon Seeley

www.seeleyware.com
Joined: 8/8/2006
Posts: 597

Been a while since I've used SQL2000 on my development machines actively and, as Mamlin i do a lot more than just DNN modules.

However, one HUGE addition in SQL20005 that has made my life easier in complex applications (which include complex DNN modules) is the new XML support that has been added in SQL2005.  Yes, SQL2000 has support but SQL2005 has some great additions.  Here is an article on that.

I'd be hard pressed to find other examples but that one alone is why I'd much rather support 2005 vs 2000.

-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
3/3/2009 5:20 PM
 
Brian Dukes


Brian Dukes's Avatar

Brian Dukes's Avatar

www.engagesoftware.com
Joined: 8/25/2006
Posts: 896

Also, as mentioned above, the (n)varchar(max) type is much easier and nicer to work with than (n)text, which it replaces.

From a development perspective, I find SQL Management Studio 2005/8 much nicer to work with than Query Analyzer from 2000.  However, when you're using Studio to automatically script your objects, it uses version specific syntax which you'll need to adjust.

Note that we support SQL 2000 in all of our modules at Engage, but I definitely feel the pain of doing it that way.

Hope that helps,

Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
3/3/2009 5:20 PM
 
Jeff Cochran


Joined: 6/3/2005
Posts: 2799

Salama wrote
 

Your software development should not coincide with what Microsoft is doing.  

Why?  SQL 2000 is nearing a decade old.  There are two versions out since it was released.  At some point a developer has to move forward, and stopping support for a version that's not even supported by the software publisher seems a reasonable time.

If a module developer doesn't aupport the version of SQL you are on, you have two choices.  Upgrade your SQL version or don't use that module.  The beauty of a free market is that you're always free to decline to use something.

Jeff
 
New Post
3/3/2009 11:24 PM
 
Robert J Collins


www.netlogiccorporation.com
Joined: 9/26/2003
Posts: 1021

I am also a fan of both the (n)varchar(max) and the XML Data Type.  Without them our LMS would require some serious workarounds and I think that we would lose some performance as well.  I would like to support 2000, but it just does not make business sense.  Time is money, and I cannot justify a more expensive product to our clients, just to support a very old database server that virtually none of our clients run (only one to date and they upgraded to 2005).  

Just my $.02
 

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
3/4/2009 8:47 AM
 
Brandon Haynes Haynes


brandonhaynes.org
Joined: 2/6/2006
Posts: 1172

Would it be needlessly inflammatory to mention that I've been taking advantage of the hierarchyid data type, first available in SQL Server 2008, in many of my recent projects?  :)

Brandon

Brandon Haynes
BrandonHaynes.org
 
 Page 5 of 6
Previous123456Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why some module developers do not support SQL Server 2000?Why some module developers do not support SQL Server 2000?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out