I have a Java jdbc client inserting data to a table in SQL server. At some point SQL server is stopped gracefully. My client receives this exception
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2392)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2376)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1900)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:6674)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:7989)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:901)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:796)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7535)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2438)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:208)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:183)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeUpdate(SQLServerStatement.java:721)
However, when the SQL server is started, I can see that this data is actually inserted in my table.
I would like to know
Stop behavior of SQL server. Whether the server can insert data and stop without replying back to the client
Any issue with JDBC driver or client that is not able to correctly handle SQL server stopping.
Is something like roll forward happening after the SQL server is started.
Any help or pointers on how to analyze this scenario would be very much appreciated.
Thanks!
Related
Can anyone please tell me why am I getting a connection reset error when I run the same call, but on a different database? The two tables contain the same data and they are on the same server.
I am trying to load from a SQL Server 2012 to Azure SQL Server using Talend. Job will read all the data from the source DB and load into destination. All the jobs are doing truncate and load. Lot of tables have records more than 7 millions. 5 tables have nearly 25 million records. I have one master job which will trigger all the jobs in parallel. I am facing a com.microsoft.sqlserver.jdbc.SQLServerException: Connection timed out (Read failed) issue.
When anyone of the job/table throws this error, all the jobs that are running parallelly also throws the same error. What is the reason for this issue and how to fix it?
Thanks,
"When you connect to a SQL Server 2012 instance running on Windows Server 2012, you get time-out error messages."
It's possible that the test server didn't get the same Windows updates as the production server. That might explain why production code and configuration are identical.
This is the Original Post, this issue might be caused by something unrelated to Java JDBC, such as SSMS or applications that do not use JDBC.
Verify that you can ping the SQL Server-installed server.
Verify that the SQL Server instance is up and operating.
Double-check that the connection codes you used are valid.
I have a Microsoft server 2012 running Microsoft SQL Server 2017 Express database. I am trying to log in through SQL Server Management on a remote machine but the log in loads forever and gives no error.
If I put in the wrong username and password I do get an error that the username and password is wrong and the error shows in the SQL Server log so it does seem to be making some type of connection.
When I connect on the local server it connects right away.
I have TCP enabled in the server configuration.
Does anyone know why this hang might be happening?
Only reason seems to be large database server with too many fragmented databases and may be slow network speed at the moment.
Our system (SQL Server) needs to connect and get data from an old IBM AS400. We need a way to get data from the AS400 using OPENDATASOURCE.
Can anyone who succeeded with this point me in the right direction on how to use it (ODBC drivers, syntax etc...)?
We are now using a linked server but due to the fact that the client reboots our server every night the linked server is dropped and all our processes go on error until it reconnects correctly, so is not an option here.
Thank you very much !
I´m looking into integrating our POS (point of sales) systems with our main database server and need some guidence on how to setup the communcation between the servers.
What is the prefered method of communicating between SQL Server asynchronously for smaller projects?
I got the "Message Broker" from google but I'm guessing thats a bit overkill.
Is creating xml files on the clients and sending them by FTP/SFTP to the master a valid option?
Clients are SQL Server Express and main server a SQL Server 2008R2.
Edit: Hope its more clear now.