How mature is Microsoft SQL Server support by the ORM?

[CLIFFORD ILKAY]

Hello,

There is an upcoming project where support for an existing application
where Microsoft SQL Server is being used. Switching to another database
is not an option. There are hundreds of custom reports that the users
have created with Crystal Reports. I found django-sqlserver
<https://pypi.python.org/pypi/django-sqlserver>. The latest version of
SQL Server it supports is 2008r2, which would be a problem given that
some sites are already running newer versions. How mature is this? Are
there any limitations or show-stoppers that you're aware of?

--
Regards,

Clifford Ilkay

647-778-8696

Dinamis

<http://dinamis.com>

[Larry Martell]

On Thu, Nov 21, 2013 at 1:20 PM, CLIFFORD ILKAY <cliffor...@dinamis.com> wrote:

Hello,

There is an upcoming project where support for an existing application
where Microsoft SQL Server is being used. Switching to another database
is not an option. There are hundreds of custom reports that the users
have created with Crystal Reports. I found django-sqlserver
<https://pypi.python.org/pypi/django-sqlserver>. The latest version of
SQL Server it supports is 2008r2, which would be a problem given that
some sites are already running newer versions. How mature is this? Are
there any limitations or show-stoppers that you're aware of?

I've been trying to get Vernon Cole's django-mssql package working (https://bitbucket.org/vernondcole/django-mssql-ado-merge) but I have not been successful. I messed around with this for a month, and then I stopped working on it. I plan to look at it again next week. I hadn't seen the package you mention. I'll check it out. 

[Fred Stluka]

Clifford,

I use:
- http://code.google.com/p/django-pyodbc/

No problem except that the MS SQL Server DB identifies itself
as using UTF-8, but actually contains Windows-1252 chars, so
we get UnicoeDecodeError a lot and have to repair the data.

--Fred

---

Fred Stluka -- mailto:fr...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no Windows or Gates.

---

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CACwCsY7PPvkEri30ERLG%3DwpV27-u4VCtF8v4ALucq2qwnQnY-g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Anssi Kääriäinen]

Check out https://bitbucket.org/Manfre/django-mssql/overview - my understanding is that it is well maintained and supports also 2012.

 - Anssi

[CLIFFORD ILKAY]

On 11/21/2013 11:41 PM, Fred Stluka wrote:

Clifford,

I use:
- http://code.google.com/p/django-pyodbc/

No problem except that the MS SQL Server DB identifies itself
as using UTF-8, but actually contains Windows-1252 chars, so
we get UnicoeDecodeError a lot and have to repair the data.

Hi Fred,

Is that because you had a legacy database with Windows-1252 characters in them? In other words, is this because of the data or because of django-pyodbc?

[CLIFFORD ILKAY]

On 11/22/2013 05:47 AM, Anssi Kääriäinen wrote:
> Check out https://bitbucket.org/Manfre/django-mssql/overview - my
> understanding is that it is well maintained and supports also 2012.

Thank you Anssi.

[Fred Stluka]

Clifford,

Yes, its because the legacy DB has Windows-1252 chars in it, but
mis-informs Django that it is all UTF-8 chars.

Not a problem with django-pyodbc, which seems to work perfectly.

--Fred

---

Fred Stluka -- mailto:fr...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no Windows or Gates.

---

--

You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/528FA684.3000202%40dinamis.com.