Microsoft SQL Server 2008: Échec de l'écriture sur le serveur

Question

J'ai une application Django avec un processus de travail qui effectue des transactions de base de données. Sous le capot, j'ai une base de données Azure SQL attachée à mon application. Le code de travail ressemble à ceci:

class Command(BaseCommand): 
    def handle(self, *args, **kwargs): 
     os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'project.settings') 
     django.setup() 
    consumer = Consumer() 

    logging.info('Booting drive consumer') 

    while True: 
     messages = consumer.poll() 

     for message in messages: 
      ... 
      DriveEvent.objects.create(event_id=response['Id'], drive_id=drive_payload['drive_id']) 
      ... 

Après environ 20 minutes, la création d'appels d'objets db commencent à défaut avec l'erreur suivante:

[drive-consumer-1]2017-07-19T03:19:08.545128400Z Traceback (most recent call last): 
[drive-consumer-1]2017-07-19T03:19:08.545133000Z File "/code/miles/management/commands/drive_consumer_worker.py", line 28, in handle 
[drive-consumer-1]2017-07-19T03:19:08.545137900Z  drive_consumer.consume(json.loads(record.value)) 
[drive-consumer-1]2017-07-19T03:19:08.545142500Z File "/code/miles/workers/drive_consumer.py", line 35, in consume 
[drive-consumer-1]2017-07-19T03:19:08.545152200Z  self._on_create(message['calendar_id'], drive_payload, message['access_token']) 
[drive-consumer-1]2017-07-19T03:19:08.545156900Z File "/code/miles/workers/drive_consumer.py", line 46, in _on_create 
[drive-consumer-1]2017-07-19T03:19:08.545161500Z  DriveEvent.objects.create(event_id=response['Id'], drive_id=drive_payload['drive_id']) 
[drive-consumer-1]2017-07-19T03:19:08.545166500Z File "/usr/local/lib/python2.7/site-packages/django/db/models/manager.py", line 85, in manager_method 
[drive-consumer-1]2017-07-19T03:19:08.545171300Z  return getattr(self.get_queryset(), name)(*args, **kwargs) 
[drive-consumer-1]2017-07-19T03:19:08.545175900Z File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 399, in create 
[drive-consumer-1]2017-07-19T03:19:08.545180700Z  obj.save(force_insert=True, using=self.db) 
[drive-consumer-1]2017-07-19T03:19:08.545185400Z File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 796, in save 
[drive-consumer-1]2017-07-19T03:19:08.545190200Z  force_update=force_update, update_fields=update_fields) 
[drive-consumer-1]2017-07-19T03:19:08.545194800Z File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 821, in save_base 
[drive-consumer-1]2017-07-19T03:19:08.545211400Z  with transaction.atomic(using=using, savepoint=False): 
[drive-consumer-1]2017-07-19T03:19:08.545215800Z File "/usr/local/lib/python2.7/site-packages/django/db/transaction.py", line 184, in __enter__ 
[drive-consumer-1]2017-07-19T03:19:08.545220400Z  connection.set_autocommit(False, force_begin_transaction_with_broken_autocommit=True) 
[drive-consumer-1]2017-07-19T03:19:08.545224900Z File "/usr/local/lib/python2.7/site-packages/django/db/backends/base/base.py", line 391, in set_autocommit 
[drive-consumer-1]2017-07-19T03:19:08.545229600Z  self._set_autocommit(autocommit) 
[drive-consumer-1]2017-07-19T03:19:08.545234000Z File "/usr/local/lib/python2.7/site-packages/sql_server/pyodbc/base.py", line 453, in _set_autocommit 
[drive-consumer-1]2017-07-19T03:19:08.545238600Z  self.connection.autocommit = autocommit 
[drive-consumer-1]2017-07-19T03:19:08.545243100Z File "/usr/local/lib/python2.7/site-packages/django/db/utils.py", line 94, in __exit__ 
[drive-consumer-1]2017-07-19T03:19:08.545247700Z  six.reraise(dj_exc_type, dj_exc_value, traceback) 
[drive-consumer-1]2017-07-19T03:19:08.545252200Z File "/usr/local/lib/python2.7/site-packages/sql_server/pyodbc/base.py", line 453, in _set_autocommit 
[drive-consumer-1]2017-07-19T03:19:08.545256800Z  self.connection.autocommit = autocommit 
[drive-consumer-1]2017-07-19T03:19:08.545262600Z Error: ('08S01', '[08S01] [FreeTDS][SQL Server]Write to the server failed (20006) (SQLSetConnectAttr)') 

init base de données (en settings.py) ressemble à quelque chose comme ceci:

DATABASES = { 
     'default': { 
      'ENGINE': 'sql_server.pyodbc', 
      'NAME': os.environ.get('DB_NAME'), 
      'HOST': os.environ.get('DB_HOST'), 
      'PORT': '1433', 
      'USER': os.environ.get('DB_USER'), 
      'PASSWORD': os.environ.get('DB_PASSWORD'), 
      'OPTIONS': { 
       'host_is_server': True, 
       'driver_supports_utf8': True, 
       'extra_params': 'tds_version=7.2;' 
      } 
     } 
    } 

Answer 1

par mon expérience, il semble être causé par la tds_version que la version 7.2 ne supporte pas Azure Database SQL. Veuillez vous reporter à ma réponse pour l'autre thread SO pymssql: Connection to the database only works sometimes pour passer à 7.3.

Eventuellement, le projet tiers michiya/django-pyodbc-azure sur GitHub peut vous aider à obtenir plus de détails.

Espérons que ça aide.