Forum Widgets
Latest Discussions
Unable to installing the SQL server 2022 reporting services on the Windows 10 Pro and Windows 11Pro
I am writing to you because I am encountering an issue while attempting to install SQL Server 2022 Reporting Services on Windows 10 Pro and Windows 11 Pro machines. While I have been able to start the installation process, I am unable to run the SQL Server 2022 Reporting Services .exe file. I have included the error message log details below for your reference. Application: SQLServerReportingServices.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 6CD5D612 (6CA70000) with exit code 80131506. I would greatly appreciate any assistance you can provide in resolving this issue. Thank you for your time and attention to this matter.
SQL Server Account locked out and password did not match?
Hi I posted this discussion earlier today, but could not find it! Perhaps I did not add a tag? In any case, I am reposting it. We have this situation that a SQL Server account has been having two different login failures recently. The errors appear in the SQL Server log without much details. Wonder if any one had encountered the same situation and if it had been resolved? The two different error messages are: 1. Login failed for user 'sql_account_name'.Reason: The account is currently locked out. The system administrator can unlock it. [CLIENT: ip_of_another_computer] 2. Login failed for user 'sql_account_name'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>] Note: I replaced the actual account name and ip with sql_account_name and ip_of_another_computer respectively. I found a query that displays the user account SQL agent jobs run under, but I did not see this SQL account. Also, I checked linked servers, but did not see this account. Furthermore, I checked Windows services of the two computers in the error messages, but I did not see that SQL account. I did look Windows task scheduler, but do not think we can use SQL account as run under for a task. Any idea or insight? ThanksSQL Server account locked out and password did not match?
Hi We have this situation that a SQL Server account has been having two different login failures recently. The errors appear in the SQL Server log without much details. Wonder if any one had encountered the same situation and if it had been resolved? The two different error messages are: 1. Login failed for user 'sql_account_name'.Reason: The account is currently locked out. The system administrator can unlock it. [CLIENT: ip_of_another_computer] 2. Login failed for user 'sql_account_name'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>] Note: I replaced the actual account name and ip with sql_account_name and ip_of_another_computer respectively. I found a query that displays the user account SQL agent jobs run under, but I did not see this SQL account. Also, I checked linked servers, but did not see this account. Furthermore, I checked Windows services of the two computers in the error messages, but I did not see that SQL account. I did look Windows task scheduler, but do not think we can use SQL account as run under for a task. Any idea or insight? Thanks
Difference SQL Server 2022 vs 2017 Bind table
Hi, I'm Beginner SQL Server Engineer. I got some Question to SQL Server 2022, 2017 Bind table. During SQL Server practice, I heard that the bind table does not know statistical information, so there should be no IO reduction due to the index, but in the 2022 version, it seems that the index in the bind table refers to statistical information. something change between 2017 and 2022 Bind table?
Error converting data type varchar to numeric when running insert query
Hi , I am getting below error when trying to run insert statement even though data types are same in target table and source view Error details : Msg 8114, Level 16, State 5, Line 1 Error converting data type varchar to numeric. Insert Query INSERT INTO [Data].[Noti_Window] SELECT CONVERT(VARCHAR(16), SYSDATETIME()) AS 'RunTime', EDW.* --INTO [Data].[Noti_Window] FROM ( SELECT * FROM [Data].[Noti_EDW_PAN_TempViewIII] UNION SELECT * FROM [Data].[Noti_EDW_DOD_TempViewIII] ) AS EDW INNER JOIN [Data].[Noti_Dim_PageID] AS PgID ON EDW.PageID = PgID.PageID ; Noti Window table structure. PAN and DOD View Structure. Could you please let me know how to find out which column is causing this issue bco'z from last 1 year working fine without any issues. Thanks in Advance for your great support. Regards, Bhaskar
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.
"Caller does not have permissions to execute the stored procedure" based on sys procedure
Did create the following procedure on my DB to read SQL Server Log: USE [MyDB] GO ALTER PROCEDURE [OMEGACA].[P_SYS_READ_POL_DEBUG] ( @p_log_no int, @p_search_1 nvarchar(4000), @p_search_2 nvarchar(4000) ) AS BEGIN EXEC sys.sp_readerrorlog @p_log_no, 1, @p_search_1, @p_search_2 ; END; Schema, DB user and Login is granted server role "sysadmin". Execute on the above procedure is granted to a certain MyDB's role. This role is granted to a certain DB user X (and login). When this user tries to execute the procedure above, it receives error: Caller does not have permissions to execute the stored procedure based on sys procedure Question: How can I get the needed permission for user X? ps. Granting sysadmin to X is not liked.
Filestream error - File location cannot be opened
Trying to solve this error: The File location cannot be opened. Either access is not enabled or you do not have permissions for the same. when trying to open a File Table using "Explore FileTable Directory" This is a client's computer and these are the configurations I have checked: SQL Server v 2019 (installed cumulative update today) Filestream enabled in configuration manager. All 3 check boxes are checked. In SSMS, instance has: Filestream Access Level = "Full access enabled", Filestream Share Name: MSSQLSERVER DB properties Filestream Directory Name is specified (and exists), Filestream Non-Transacted Access = "Full" Logged into computer as an admin and into SSMS as sa. I can execute a select statement against a filetable but am unable to access via the "Explore FileTable Directory" option. What am I missing?Need help to figure the solution for recent vulnerabilities report in my DB host server.
Dear Experts, During recent scans, below vulnerability was reported in my Stage database server, this is my current DB version Microsoft SQL Server 2019 (RTM-CU23) (KB5030333) - 15.0.4335.1 (X64). This scan item we keep coming on every scan item and need to a proper solution to fix. we have applied the patch- KB5030333 but still issue was reported. Even though planning to apply the Jan 2024 patch SQL db patch but i'm not confident if the patch will fix this scan or not as this scan item is coming from 2023 July onwards and after that we have applied JNS and OND patches as well. but again in jan scans this item came in. Need your expertise to understand the real cause of this scan and how to fix the same. Note: I'm very new to SQL DB and started learning from last 4-5 months. Vulnerability Title Vulnerability Description Vulnerability Proof Vulnerability Solution Microsoft SQL Server Obsolete Version: Remote An obsolete version of the Microsoft SQL database server is running. Note: When the support period ends for a Microsoft SQL Server product, no further patches will be provided even for serious security problems. * Running TDS service * Product SQL Server 2008 found in fingerprint is not SQL Server 2000 * Product SQL Server 2008 found in fingerprint is not SQL Server 2005 * Product SQL Server 2008 exists -- Microsoft SQL Server 2008 10.0.2531 Upgrade to the latest version of Microsoft SQL Server Download and apply the upgrade from: http://technet.microsoft.com/sqlserver
SQL Server Distributed AG's Forwarder Is Not Syncing After Primary AG's Internal Failover
I have set up a SQL Server Distributed Availability Group (DAG) in Kubernetes using SQL Server on Ubuntu images. The setup consists of two availability groups (AGs) across two separate clusters: Setup Details: Primary Cluster (AG1) Pods: ag1-0 (Primary), ag1-1, ag1-2. The Primary is Exposed via the LoadBalancer service. Remote Cluster (AG2): Pods: ag2-0 (The Primary of AG2, Acting as a forwarder of DAG), ag2-1, ag2-2. The Forwarder (ag2-0) is Exposed via the LoadBalancer service. Distributed AG Configuration: AG1 and AG2 are part of the DAG. Each AG’s primary is dynamically selected using the pod's label role=primary. LISTENER_URL in the DAG configuration points to the LoadBalancer service of each AG. Issue: DAG Not Syncing After AG1 Failover For testing, I triggered a failover in AG1 using: `ALTER AVAILABILITY GROUP [AG1] FORCE_FAILOVER_ALLOW_DATA_LOSS;` The global primary changed from ag1-0 to ag1-1, and I updated the role=primary label accordingly (removed from ag1-0, added to ag1-1. However, AG2 (the forwarder and its replicas) stopped syncing and became unhealthy. From ag2-0 (forwarder) logs, I only see connection timeouts and disconnections from the global primary. AG2 is not automatically reconnecting to the new primary (ag1-1), even though the LoadBalancer service in LISTENER_URL now points to ag1-1. Logs from ag2-0 (Forwarder) Shows Like A connection timeout has occurred while attempting to establish a connection to GLOBAL PRIMARY. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance Steps I Tried: - Checked DAG Configuration – The LISTENER_URL is correctly set to the LoadBalancer of AG1, which now points to ag1-1. - Ran the Resume Command: `ALTER DATABASE [agtestdb] SET HADR RESUME;` This did not resolve the issue. - Verified Network Connectivity Questions: - What steps are required to ensure AG2 correctly syncs with the new global primary (ag1-1) after an AG1's internal failover? - Is there a specific command that needs to be run on the forwarder (ag2-0) or the new global primary (ag1-1) to reestablish synchronization? - Why isn’t AG2 automatically reconnecting, even though the LoadBalancer service points to the correct primary? - Are there any best practices for handling SQL Server DAG failovers in Kubernetes? Any insights would be greatly appreciated!
