Forum Widgets
Latest Discussions
Do input tag values keep updating after SP execution begins?
In my facility we use PLC's to trigger SQL Stored Procedures through a Kepware server. Most of these SP's are for data collection. If I set the execute bit to true, but then one of my data collection points changes value before the execution finishes, does the SP see that data change? Or is it just using the value as it was at time of execution start? Thanks for your help in advance
SQL 2025 Jobs
SQL Server 2022 16.0.4212.1 Installed in a windows server 2025 DC. SQLSERVERAGENT starts with NT Service\SQLSERVERAGENT I have some jobs that runs at the scheduled times. But one no. Failure: "Job failed. The job was invoked by Schedule 9 (06:00 xxxxx). The last step to execute was step 0 (no steps ran)." Job steps: exec SP_01 GO EXEC SP_02 But if I run it manually, it runs without problems. Can anyone help me? Thank you
SQL Server 2019 – Repeated Recovery Mode and Backup Failure After Server Shutdown
Hello, We are currently using SQL Server 2019 Standard Edition in our company. Recently, our server experienced a complete shutdown due to a lightning strike. After the incident, one of our databases entered Recovery Mode, and it took approximately one hour before it returned to normal operation. The issue is that this behavior repeats every time we restart SQL Server. In other words: Server restart → Database enters Recovery Mode → Returns to normal after about one hour. Additionally, we are unable to perform backups on this database. Based on the SQL Server error logs and Windows Event Viewer, it appears that the backup attempts fail because the database has not completed recovery at the time of execution. We would like to ask for guidance on the following points: Could this issue be related to physical damage or disk corruption? Is there a way to prevent the database from entering Recovery Mode, or at least speed up the recovery process? Besides running DBCC CHECKDB, are there any other diagnostics or recovery strategies we should consider? Additional Information: SQL Server 2019 Standard Edition (on-premises) The affected database is running on a single instance We attempted to copy only the MDF file to another server and recover the database, but this also failed Thank you in advance for your support.
SQL Server 2022 Express Install Issues
I am a non tech savvy student trying to install SQL Server 2022 Express for class and I am running into issues, looking for help. It gets all the way through the install process and gives me "Unable to install SQL Server (setup.exe) Exit code (Decimal): -2061893606Error description: Wait in the Database Engine recovery handle Failed. Check the SQL Server error log for potential causes" and C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20250903_162628 I have fully uninstalled anything related to SQL and reinstalled multiple times with no success. I reset windows, no luck. Any help would be appreciated.
SQL Server not supported Windows 11 Home Version
I bought a new computer that came with Windows 11 Home. I am unable to install SQL Server 22 on W11. I would like to install Windows 10 that does support SQL server but I will void my support warranty doing so. I suspect I can upgrade to Windows 11 Pro but I am not sure that OS supports SQL Server. Any thoughts or advice would be helpful.Availability Group failover issue
Hello, We ran into an issue recently that caused a three-node availability group to fail. We're running SQL Server 2019 (RTM-CU32-GDR) on Windows Server 2019 Standard (version 1809). We're trying to understand why the availability group wasn't able to start when the cluster automatically failed it over to another node. First, here is the state/configuration of the availability group just before the failure: Node A - primary replica; synchronization state = synchronized; availability mode = synchronous commit; failover mode = automatic Node B - secondary replica; synchronization state = synchronized; availability mode = synchronous commit; failover mode = automatic Node C - secondary replica; synchronization state = synchronized; availability mode = synchronous commit; failover mode = manual Here's the abbreviated summary of events: An I/O error occurred on node A. Specifically, it was a checksum mismatch when reading one of the tempdb files. This caused the availability group cluster resource to fail. The cluster tried unsuccessfully to restart the AG on node A so it failed over the AG to node B. The AG failed to come online on node B. The cluster failed back the AG to node A and left it in a failed state. We manually failed over the AG to node B a few minutes later and it was successful. When the cluster tried to automatically fail over the AG to node B, the only error we found that indicates why the AG couldn't start is: "SQL Server Availability Group <AG1>: [hadrag] ODBC Error: [42000] [Microsoft][SQL Server Native Client 11.0][SQL Server]The availability replica for availability group 'AG1' on this instance of SQL Server cannot become the primary replica. One or more databases are not synchronized or have not joined the availability group. If the availability replica uses the asynchronous-commit mode, consider performing a forced manual failover (with possible data loss). Otherwise, once all local secondary databases are joined and synchronized, you can perform a planned manual failover to this secondary replica (without data loss)." Since all nodes were in synchronous commit mode, the above error implies that the secondary databases on node B were either not joined or not synchronized. This is concerning and we're worried that auto-failover is not as reliable as we expected. Does anyone have any suggestions for how to ensure the secondary node is ready and able to become primary when the AG fails on the original primary node? Or any suggestions for settings/configuration to change? The only corrective action we have taken so far is to increase the "maximum failures in the specified period" from the default of 2 to 6 (per the recommendation https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/hadr-cluster-best-practices?view=azuresql&tabs=windows2012#relaxed-monitoring) and to decrease the failover period from the default of 6 hours to 2. Any suggestions or insights would be greatly appreciated.
SQL SERVER EXPRESS EDITION 2022 NOT INSTALLING ON MY SNAPDRAGON X PROCESSOR
Every time i try to install sql server on my laptop ASUS ASUS Vivobook S16 (2025) with Office 2024 + M365 Basic*, Metal Body*, Qualcomm Snapdragon X - (16 GB/512 GB SSD/Windows 11 Home) S3607QA-SH075WS Thin and Light Laptop (16 inch, Cool Silver, 1.74 Kg, With MS Office) I get this error: Error installing SQL Server Database Engine Services Shared Features There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Error code: 1722 Log file: C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20250811_013441\sql_engine_core_shared_Cpu64_1.log Attaching the error ss Let me know what should I doFail to OPENROWSET insert geometry data from parquet
Hi! I'm trying to insert geometry data (WKB) from a parquet file to a data base table. I manage to get it working for small geometries but it's failing for lager geometriers. Here is the code: INSERT db.s.t SELECT geometry::STGeomFromWKB(a.geom,1) FROM OPENROWSET ( BULK 'path_to.parquet', FORMAT = 'PARQUET', DATA_SOURCE = 's3_sorce' ) AS a The failure: String or binary data would be truncated while reading column of type 'VARBINARY(8000)'. Check ANSI_WARNINGS option.... Seems as if the geometry type is not recognized. Is there a way around this?
