search

microsoft / mssql-jdbc

The Microsoft JDBC Driver for SQL Server is a Type 4 JDBC driver that provides database connectivity with SQL Server through the standard JDBC application program interfaces (APIs).
MIT License
1.05k stars 424 forks source link

Getting "[S0102][9105] The provided statistics stream is corrupt." on Update Statistics in Azure sql Datawarehouse #1257

Closed souravjha77 closed 4 years ago

souravjha77 commented 4 years ago

Driver version

8.1.1.jre8-preview

SQL Server version

Effective version: Azure SQL Database (ver. 12.0.2531)

Client Operating System

JAVA/JVM version

Cent OS 7

Table schema

Number of columns: 7 Total Number of rows : 0.5 Million Data types of columns: int,int, varchar, varchar, float,float,date

Problem description

Ran following command: "Update statistics "

  1. Expected behaviour: The above query should pass
  2. Actual behaviour: failed with below mentioned error.
  3. Error message/stack trace: [S0102][9105] The provided statistics stream is corrupt."
  4. Any other details that can be helpful: I have tried rebuilding the index as well as creating new statistics. But, both failed with same error mentioned in 3.

JDBC trace logs

Reproduction code

Just run the code "Update statistics " from intellij database tool / azure synapse ui

ulvii commented 4 years ago

@souravjha77 , please fill out the template and provide more details.

souravjha77 commented 4 years ago

@ulvii I have added the command. let me know if you need any other details

rene-ye commented 4 years ago

Please fill out the sections "Table schema" as well as "Reproduction Code".

souravjha77 commented 4 years ago

@rene-ye updated details of the column and table

ulvii commented 4 years ago

Hi @souravjha77 , A quick search of the error message makes me think that the issue is happening on the server side. Are you seeing the same error message when you run the query on SSMS or Azure query editor? If yes, please contact Azure support team instead.

ulvii commented 4 years ago

This does not seem to be a driver issue, closing. Please feel free to re-open it in case if you have any questions.