Fetched Row Count Not Match With Source Table Row Count about go-mssqldb HOT 4 OPEN

thx for opening an issue!
The implications of this issue are pretty bad, considering querying rows is the primary use of the driver.
Have you tried reverting to any older versions of the driver, including the old denisenkom versions, to see if this bug is relatively new or old?

from go-mssqldb.

Hi, I haven't tried the older version, but I'll try it out. Which is the older version should I try?
And something that I suspect is, there is a frequent restore activity on the table from my other team, is it affecting the rows that I fetched ?

from go-mssqldb.

i'd assume ongoing restores would disrupt a multimillion row query, depending on what kinds of locks are in use.
They'd probably be upset if your query grabbed a lock on the entire content of the table...

from go-mssqldb.

Somtimes my SELECT query failed with error like this:

"Error": {
  "Number": 927,
  "State": 6,
  "Class": 14,
  "Message": "Database 'xxxx' cannot be opened. It is in the middle of a restore.",
  "ServerName": "xxxx",
  "ProcName": "",
  "LineNo": 1,
  "All": [
   {
    "Number": 927,
    "State": 6,
    "Class": 14,
    "Message": "Database 'xxxx cannot be opened. It is in the middle of a restore.",
    "ServerName": "xxxx",
    "ProcName": "",
    "LineNo": 1,
    "All": null
 }

So I can tell my SELECT query was interrupted with the restore actitivy.
I think it is make sense that the restore acitvity cause I can't retrieve a complete record from the table.

from go-mssqldb.