Matt, Thank you so much for your posting. My initial question was indeed about both the webserver AND the database, but I believe you're the first who commented on the latter. I am already aware about the Django + MSSQL issue, but compared to the Django+IIS, there are stable solutions that run solid in production mode.
As mentioned in the SO blog you indicated, we as well have a heavily invested MSSQL environment, direct interface to which (as opposed to XML-RPC calls, for instance) is more than just an advantage. Anthony On Dec 3, 5:26 pm, Matt Conrad <matt...@gmail.com> wrote: > I notice that the conversation is mostly about IIS vs Apache. > > You'll also want to think about the database. Django doesn't have > built in support for MSSQL. You could run Postgres or MySQL on > Windows, or there are some adapters for Django that will let it talk > to SQL Server. Either way, you'll probably want to think about this up > front. > > I haven't got any experience with this, but others here probably do. > If you want to stick with MSSQL, here's a discussion from a year ago > on SO to get you > started:http://stackoverflow.com/questions/842831/using-sql-server-with-djang... > > Matt > > On Fri, Dec 3, 2010 at 5:32 AM, ashdesigner <antony.shash...@gmail.com> wrote: > > Ok, I see. Happily, this is not the case with us. We've discussed the > > issue with the crew, and our decision is that most likely we'll deploy > > on Win+Apache. > > Hope there won't be any considerable development limitations due to > > the use of the Windows Server OS. > > > Thank you a lot! > > > Regards, > > Anthony -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
