We are receiving this notification several hundred times a day and while we're regularly checking notifications from Severity 16 errors, this isn't something we're really concerned about. I've read the article and replies at https://dba.stackexchange.com/questions/33750/error-9245-severity-16-state-1-during-the-last-time-interval-xxx-query-n and while that's very informative, I'd like to know how can we suppress it? We have an automated alert set up for severity 016 errors and we don't exact categorize this one as an "action items" yet are receiving hundreds of them daily. Is there a way to suppress it?

*Using mariadb 10.4.13-MariaDB but I get the same error in a copy of the database running under 10.3.* The important part of the schema shows /*Database: mamlocal*/ ---------------------- /*Table Information*/ --------------------- Name Engine Version Row_format Rows Avg_row_length Data_length Max_data_length Index_length Data_free Auto_increment Create_time Update_time Check_time Collation Checksum Create_options Comment Max_index_length Temporary ------------------------------------ ------ ------- ---------- ------ -------------- ----------- --------------- ------------ --------- -------------- ------------------- ------------------- ---------- ----------------- -------- -------------- ----------------------------------------------------------- ------------------ ----------- ... member InnoDB 10 Dynamic 706 162 114688 0 49152 0 4528 2020-08-17 14:48:55 2021-04-06 10:27:53 (NULL) utf8_general_ci (NULL) 0 N ... and the table member is created using... CREATE TABLE member ( member_id int(11) NOT NULL AUTO_INCREMENT, member_title varchar(10) DEFAULT NULL, member_fn_1 varchar(50) DEFAULT NULL, member_sn varchar(50) DEFAULT NULL, ... other fields PRIMARY KEY (member_id) ) These statements each produce the expected results. SELECT * FROM information_schema.tables WHERE table_schema = 'mamlocal' AND table_name = 'member'; SELECT * FROM information_schema.tables WHERE table_name = 'member'; SELECT member_id FROM member SELECT member_id FROM mamlocal.member but these produce Error Code: 1109 Unknown table 'member' in field list UPDATE member SET member_id = member_id ; UPDATE mamlocal.member SET member_id = member_id *(The real update does something useful but I simplified it to try to find out where the error was)* Can anyone help me to identify why? I have looked at these other questions but still cannot see what is wrong Qn1 Qn2 Qn3 Here is an SQLfiddle showing the same code working correctly in MySQL, as I would expect and I have used similar code in many other places without problems to update table member. Using the same code to update another table works ok. **More experiments showing that table member is there.** This code... INSERT INTO member () VALUES (); UPDATE member SET member_id = member_id ; ... gives me the message 2 queries executed, 1 success, 1 errors, 0 warnings Query: insert into member () values () 1 row(s) affected Execution Time : 0.002 sec Transfer Time : 0.001 sec Total Time : 0.004 sec ----------------------------------------------------------- Query: UPDATE member SET member_id = member_id Error Code: 1109 Unknown table 'member' in field list Execution Time : 0 sec Transfer Time : 0 sec Total Time : 0.001 sec

I am playing around with a MariaDB Galera Master Master Cluster and I have some issues which I do not understand. [mysqld] bind-address=0.0.0.0 [galera] wsrep_on=ON wsrep_provider=/usr/lib64/galera/libgalera_smm.so binlog_format=ROW innodb_autoinc_lock_mode=2 innodb_locks_unsafe_for_binlog=1 query_cache_size=0 query_cache_type=0 default_storage_engine=InnoDB innodb_log_file_size=100M innodb_file_per_table innodb_flush_log_at_trx_commit=2 wsrep_provider=/usr/lib64/galera/libgalera_smm.so wsrep_cluster_address="gcomm://" wsrep_cluster_name='galera_cluster' wsrep_node_address='192.168.2.67' wsrep_node_name='KVM-1' wsrep_sst_method=rsync wsrep_sst_auth=repl_user:PASS On the other nodes [mysqld] bind-address=0.0.0.0 [galera] wsrep_on=ON wsrep_provider=/usr/lib64/galera/libgalera_smm.so binlog_format=ROW innodb_autoinc_lock_mode=2 innodb_locks_unsafe_for_binlog=1 query_cache_size=0 query_cache_type=0 default_storage_engine=InnoDB innodb_log_file_size=100M innodb_file_per_table innodb_flush_log_at_trx_commit=2 wsrep_provider=/usr/lib64/galera/libgalera_smm.so wsrep_cluster_address="gcomm://IP_ADDR_MAIN_NODE,OTHER_NODES_ADDRS" wsrep_cluster_name='galera_cluster' wsrep_node_address='192.168.2.68' wsrep_node_name='KVM-2' wsrep_sst_method=rsync wsrep_sst_auth=repl_user:PASS when i login to mysql and query for SHOW STATUS LIKE 'wsrep_cluster_size'; Empty set (0.00 sec) Am i missing anything?

We are trying to install Cosmos DB ODBC Driver following the instructions provided [in this Microsoft Azure resource](https://learn.microsoft.com/en-us/azure/cosmos-db/odbc-driver) and are running into the following error: >The setup routines for Microsoft DocumentDB ODBC Driver ODBC driver could not be loaded due to a system error code 126: The specified module could not be found. (C:\Program Files\Microsoft DocumentDB ODBC Driver\lib\DocumentDBODBC_sb64.dll). We've tried unsuccessfully on Windows Server 2008R2 and Windows Server 2012R2. We have it working on several Windows 10 desktops, just not server OS's unfortunately. We tried several things like installing using run as administrator, from command line, with both 32 and 64 bit installed, and then one or the other. We opened the location of the DLL to 'Everyone/full control' We checked that the Visual C++ redistributables are installed although not sure which specific ones are needed. Any advice would be greatly appreciated.

I Got Error: >A user request from the session with SPID 183 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory. When I manually run the stored procedure it works ok, this one time got this error. Any idea what can cause it and how to prevent it? Can someone explain what should I look for in the Dump File?

Microsoft SQL Server Enterprise (64-bit) Version 15.0.2080.9

SQL Dump Log: (Had to cut part of the last part of the Dump due to characters limitation)
. This is an informational message only. No user action is required.
2022-05-26 04:46:58.08 Backup      BACKUP DATABASE successfully processed 6689 pages in 1.556 seconds (33.580 MB/sec).
2022-05-26 04:47:10.65 Backup      Database backed up. Database: MaltaExperience, creation date(time): 2020/07/20(10:20:33), pages dumped: 755, first LSN: 314:106:1, last LSN: 314:109:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\MaltaExperience_20220526_0447.bak'}). This is an informational message only. No user action is required.
2022-05-26 04:47:10.66 Backup      BACKUP DATABASE successfully processed 745 pages in 0.197 seconds (29.512 MB/sec).
2022-05-26 04:47:14.82 Backup      Database backed up. Database: OMNIS_DW, creation date(time): 2019/11/18(12:21:57), pages dumped: 21770, first LSN: 829:515:1, last LSN: 829:518:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\OMNIS_DW_20220526_0447.bak'}). This is an informational message only. No user action is required.
2022-05-26 04:47:14.84 Backup      BACKUP DATABASE successfully processed 21617 pages in 1.457 seconds (115.906 MB/sec).
2022-05-26 04:47:23.26 Backup      Database backed up. Database: STL_DEVELOPERTOOLS, creation date(time): 2019/12/03(18:53:01), pages dumped: 714, first LSN: 59:3426:1, last LSN: 59:3429:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\STL_DEVELOPERTOOLS_20220526_0447.bak'}). This is an informational message only. No user action is required.
2022-05-26 04:47:23.28 Backup      BACKUP DATABASE successfully processed 705 pages in 0.107 seconds (51.415 MB/sec).
2022-05-26 04:47:34.52 Backup      Database backed up. Database: W6_BMIT, creation date(time): 2020/07/28(11:59:10), pages dumped: 74251, first LSN: 27089:468:1, last LSN: 27089:471:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\W6_BMIT_20220526_0447.bak'}). This is an informational message only. No user action is required.
2022-05-26 04:47:34.54 Backup      BACKUP DATABASE successfully processed 74025 pages in 8.780 seconds (65.867 MB/sec).
2022-05-26 04:56:37.18 Backup      Database backed up. Database: W6_FB_KC_BMIT, creation date(time): 2020/07/27(20:48:58), pages dumped: 6268300, first LSN: 707616:301:1, last LSN: 707616:304:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\W6_FB_KC_BMIT_20220526_0447.bak'}). This is an informational message only. No user action is required.
2022-05-26 04:56:37.19 Backup      BACKUP DATABASE successfully processed 6268265 pages in 527.577 seconds (92.822 MB/sec).
2022-05-26 05:02:43.66 Backup      Database backed up. Database: hMailServer, creation date(time): 2021/04/14(11:58:22), pages dumped: 651, first LSN: 108:12495:1, last LSN: 108:12498:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\hMailServer_20220526_0402.bak'}). This is an informational message only. No user action is required.
2022-05-26 05:02:43.71 Backup      BACKUP DATABASE successfully processed 641 pages in 0.204 seconds (24.516 MB/sec).
2022-05-26 05:02:46.28 Backup      Database backed up. Database: RT_ILLY, creation date(time): 2020/11/27(16:16:32), pages dumped: 955, first LSN: 47:12768:1, last LSN: 47:12771:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\RT_ILLY_20220526_0402.bak'}). This is an informational message only. No user action is required.
2022-05-26 05:02:46.30 Backup      BACKUP DATABASE successfully processed 945 pages in 0.153 seconds (48.212 MB/sec).
2022-05-26 05:02:48.96 Backup      Database backed up. Database: W6_SO_DEMO, creation date(time): 2021/12/02(15:50:03), pages dumped: 723, first LSN: 46:3173:1, last LSN: 46:3176:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\W6_SO_DEMO_20220526_0402.bak'}). This is an informational message only. No user action is required.
2022-05-26 05:02:48.98 Backup      BACKUP DATABASE successfully processed 713 pages in 0.133 seconds (41.834 MB/sec).
2022-05-26 05:02:51.45 Backup      Database backed up. Database: W6_SO_ILLY, creation date(time): 2021/12/02(15:51:04), pages dumped: 803, first LSN: 48:9130:1, last LSN: 48:9133:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\BACKUP\SQL_DAILY_BACKUP\W6_SO_ILLY_20220526_0402.bak'}). This is an informational message only. No user action is required.
2022-05-26 05:02:51.47 Backup      BACKUP DATABASE successfully processed 793 pages in 0.128 seconds (48.351 MB/sec).
2022-05-26 06:30:01.21 spid183     CImageHelper::Init () Version-specific dbghelp.dll is not used
2022-05-26 06:30:01.24 spid183     ***Stack Dump being sent to F:\SQL\MSSQL15.MSSQLSERVER\MSSQL\LOG\SQLDump2803.txt
2022-05-26 06:30:01.24 spid183     SqlDumpExceptionHandler: Process 183 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2022-05-26 06:30:01.24 spid183     * *******************************************************************************
2022-05-26 06:30:01.24 spid183     *
2022-05-26 06:30:01.24 spid183     * BEGIN STACK DUMP:
2022-05-26 06:30:01.24 spid183     *   05/26/22 06:30:01 spid 183
2022-05-26 06:30:01.24 spid183     *
2022-05-26 06:30:01.24 spid183     *
2022-05-26 06:30:01.24 spid183     *   Exception Address = 00007FFC96483D83 Module(sqllang+0000000000903D83)
2022-05-26 06:30:01.24 spid183     *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
2022-05-26 06:30:01.24 spid183     *   Access Violation occurred reading address 000001EAC188A000
2022-05-26 06:30:01.24 spid183     * Input Buffer 218 bytes -
2022-05-26 06:30:01.24 spid183     *             exec [spr_X_BOB_ExportAndEmail_v4] 32, 32026    exec [spr_X_S
2022-05-26 06:30:01.24 spid183     *  UMMARY_ExportAndEmail_v2] 32, 32026  
2022-05-26 06:30:01.24 spid183     *  
2022-05-26 06:30:01.24 spid183     *
2022-05-26 06:30:01.24 spid183     *  MODULE                          BASE      END       SIZE
2022-05-26 06:30:01.24 spid183     * sqlservr                       00007FF789CF0000  00007FF789D8DFFF  0009e000
2022-05-26 06:30:01.24 spid183     * ntdll                          00007FFCAC280000  00007FFCAC46CFFF  001ed000
2022-05-26 06:30:01.24 spid183     * KERNEL32                       00007FFCAB950000  00007FFCABA03FFF  000b4000
2022-05-26 06:30:01.24 spid183     * KERNELBASE                     00007FFCA8950000  00007FFCA8BE3FFF  00294000
2022-05-26 06:30:01.24 spid183     * apphelp                        00007FFCA6480000  00007FFCA650BFFF  0008c000
2022-05-26 06:30:01.24 spid183     * CRYPT32                        00007FFCA86A0000  00007FFCA8894FFF  001f5000
2022-05-26 06:30:01.24 spid183     * ucrtbase                       00007FFCA8310000  00007FFCA8409FFF  000fa000
2022-05-26 06:30:01.24 spid183     * MSASN1                         00007FFCA8260000  00007FFCA8271FFF  00012000
2022-05-26 06:30:01.24 spid183     * ADVAPI32                       00007FFCA9EF0000  00007FFCA9F96FFF  000a7000
2022-05-26 06:30:01.24 spid183     * msvcrt                         00007FFCA9CD0000  00007FFCA9D6DFFF  0009e000
2022-05-26 06:30:01.24 spid183     * sechost                        00007FFCABF90000  00007FFCAC02EFFF  0009f000
2022-05-26 06:30:01.24 spid183     * RPCRT4                         00007FFCAC120000  00007FFCAC23CFFF  0011d000
2022-05-26 06:30:01.24 spid183     * ole32                          00007FFCA99F0000  00007FFCA9B45FFF  00156000
2022-05-26 06:30:01.24 spid183     * combase                        00007FFCA94B0000  00007FFCA97DCFFF  0032d000
2022-05-26 06:30:01.24 spid183     * bcryptPrimitives               00007FFCA8BF0000  00007FFCA8C71FFF  00082000
2022-05-26 06:30:01.24 spid183     * GDI32                          00007FFCAC030000  00007FFCAC058FFF  00029000
2022-05-26 06:30:01.24 spid183     * gdi32full                      00007FFCA8500000  00007FFCA869BFFF  0019c000
2022-05-26 06:30:01.24 spid183     * msvcp_win                      00007FFCA8460000  00007FFCA84FFFFF  000a0000
2022-05-26 06:30:01.24 spid183     * USER32                         00007FFCAB7B0000  00007FFCAB946FFF  00197000
2022-05-26 06:30:01.24 spid183     * win32u                         00007FFCA8C80000  00007FFCA8C9FFFF  00020000
2022-05-26 06:30:01.24 spid183     * NETAPI32                       00007FFC9FCD0000  00007FFC9FCE8FFF  00019000
2022-05-26 06:30:01.24 spid183     * pdh                            00007FFCA48C0000  00007FFCA490CFFF  0004d000
2022-05-26 06:30:01.24 spid183     * SQLOS                          00007FFC9C2B0000  00007FFC9C2B7FFF  00008000
2022-05-26 06:30:01.24 spid183     * sqlmin                         00007FFC98220000  00007FFC9B1ECFFF  02fcd000
2022-05-26 06:30:01.24 spid183     * WS2_32                         00007FFCAB740000  00007FFCAB7ACFFF  0006d000
2022-05-26 06:30:01.24 spid183     * OLEAUT32                       00007FFCA9C00000  00007FFCA9CC3FFF  000c4000
2022-05-26 06:30:01.24 spid183     * sqlTsEs                        00007FFC952B0000  00007FFC95B79FFF  008ca000
2022-05-26 06:30:01.24 spid183     * sqldk                          00007FFC94D80000  00007FFC952A7FFF  00528000
2022-05-26 06:30:01.24 spid183     * opends60                       00007FFC94D70000  00007FFC94D78FFF  00009000
2022-05-26 06:30:01.24 spid183     * qds                            00007FFC94C40000  00007FFC94D67FFF  00128000
2022-05-26 06:30:01.24 spid183     * svl                            00007FFC94C10000  00007FFC94C3CFFF  0002d000
2022-05-26 06:30:01.24 spid183     * MSVCP140                       00007FFCA03C0000  00007FFCA0450FFF  00091000
2022-05-26 06:30:01.24 spid183     * MPR                            00007FFCA0690000  00007FFCA06AAFFF  0001b000
2022-05-26 06:30:01.24 spid183     * VCRUNTIME140                   00007FFCA0310000  00007FFCA0328FFF  00019000
2022-05-26 06:30:01.24 spid183     * Secur32                        00007FFCA24D0000  00007FFCA24DBFFF  0000c000
2022-05-26 06:30:01.24 spid183     * WINHTTP                        00007FFCA4740000  00007FFCA4830FFF  000f1000
2022-05-26 06:30:01.24 spid183     * sqllang                        00007FFC95B80000  00007FFC98177FFF  025f8000
2022-05-26 06:30:01.25 spid183     * secforwarder                   00007FFC94BF0000  00007FFC94C00FFF  00011000
2022-05-26 06:30:01.25 spid183     * bcrypt                         00007FFCA8CA0000  00007FFCA8CC5FFF  00026000
2022-05-26 06:30:01.25 spid183     * ODBC32                         00007FFC94B30000  00007FFC94BE4FFF  000b5000
2022-05-26 06:30:01.25 spid183     * WINTRUST                       00007FFCA8CD0000  00007FFCA8D30FFF  00061000
2022-05-26 06:30:01.25 spid183     * WINMM                          00007FFCA0390000  00007FFCA03B3FFF  00024000
2022-05-26 06:30:01.25 spid183     * VCRUNTIME140_1                 00007FFCA0B90000  00007FFCA0B9BFFF  0000c000
2022-05-26 06:30:01.25 spid183     * ncrypt                         00007FFCA7D00000  00007FFCA7D25FFF  00026000
2022-05-26 06:30:01.25 spid183     * USERENV                        00007FFCA8140000  00007FFCA8168FFF  00029000
2022-05-26 06:30:01.25 spid183     * profapi                        00007FFCA8280000  00007FFCA82A3FFF  00024000
2022-05-26 06:30:01.25 spid183     * WININET                        00007FFC93C00000  00007FFC940E0FFF  004e1000
2022-05-26 06:30:01.25 spid183     * XmlLite                        00007FFCA1E80000  00007FFCA1EB9FFF  0003a000
2022-05-26 06:30:01.25 spid183     * AUTHZ                          00007FFCA7310000  00007FFCA735BFFF  0004c000
2022-05-26 06:30:01.25 spid183     * WINMMBASE                      00007FFCA0330000  00007FFCA035CFFF  0002d000
2022-05-26 06:30:01.25 spid183     * cfgmgr32                       00007FFCA8410000  00007FFCA8459FFF  0004a000
2022-05-26 06:30:01.25 spid183     * dhcpcsvc                       00007FFCA4AF0000  00007FFCA4B0BFFF  0001c000
2022-05-26 06:30:01.25 spid183     * NSI                            00007FFCAA230000  00007FFCAA237FFF  00008000
2022-05-26 06:30:01.25 spid183     * NETUTILS                       00007FFCA7780000  00007FFCA778DFFF  0000e000
2022-05-26 06:30:01.25 spid183     * NTASN1                         00007FFCA7CC0000  00007FFCA7CFBFFF  0003c000
2022-05-26 06:30:01.25 spid183     * SSPICLI                        00007FFCA8170000  00007FFCA819EFFF  0002f000
2022-05-26 06:30:01.25 spid183     * DPAPI                          00007FFCA8030000  00007FFCA8039FFF  0000a000
2022-05-26 06:30:01.25 spid183     * LOGONCLI                       00007FFCA7860000  00007FFCA78A1FFF  00042000
2022-05-26 06:30:01.25 spid183     * SAMCLI                         00007FFCA4D60000  00007FFCA4D77FFF  00018000
2022-05-26 06:30:01.25 spid183     * psapi                          00007FFCA9D70000  00007FFCA9D77FFF  00008000
2022-05-26 06:30:01.25 spid183     * kernel.appcore                 00007FFCA8240000  00007FFCA8250FFF  00011000
2022-05-26 06:30:01.25 spid183     * instapi150                     00007FFC926E0000  00007FFC926F2FFF  00013000
2022-05-26 06:30:01.25 spid183     * CRYPTSP                        00007FFCA8D40000  00007FFCA8D56FFF  00017000
2022-05-26 06:30:01.25 spid183     * rsaenh                         00007FFCA75B0000  00007FFCA75E2FFF  00033000
2022-05-26 06:30:01.25 spid183     * CRYPTBASE                      00007FFCA7C00000  00007FFCA7C0BFFF  0000c000
2022-05-26 06:30:01.25 spid183     * imagehlp                       00007FFCABA10000  00007FFCABA2CFFF  0001d000
2022-05-26 06:30:01.25 spid183     * gpapi                          00007FFCA6E80000  00007FFCA6EA1FFF  00022000
2022-05-26 06:30:01.25 spid183     * wkscli                         00007FFCA37E0000  00007FFCA37F7FFF  00018000
2022-05-26 06:30:01.25 spid183     * cscapi                         00007FFC91F70000  00007FFC91F81FFF  00012000
2022-05-26 06:30:01.25 spid183     * sqlevn70                       000001D105470000  000001D1057A9FFF  0033a000
2022-05-26 06:30:01.25 spid183     * CLUSAPI                        00007FFC9DFD0000  00007FFC9E0D9FFF  0010a000
2022-05-26 06:30:01.25 spid183     * DNSAPI                         00007FFCA7790000  00007FFCA7855FFF  000c6000
2022-05-26 06:30:01.25 spid183     * IPHLPAPI                       00007FFCA7740000  00007FFCA777DFFF  0003e000
2022-05-26 06:30:01.25 spid183     * RESUTILS                       00007FFC9E0E0000  00007FFC9E17DFFF  0009e000
2022-05-26 06:30:01.25 spid183     * VERSION                        00007FFCA24F0000  00007FFCA24F9FFF  0000a000
2022-05-26 06:30:01.25 spid183     * hkruntime                      00007FFC89B70000  00007FFC89E42FFF  002d3000
2022-05-26 06:30:01.25 spid183     * dbghelp                        00007FFCA35B0000  00007FFCA379CFFF  001ed000
2022-05-26 06:30:01.25 spid183     * hkcompile                      00007FFC89980000  00007FFC89ABFFFF  00140000
2022-05-26 06:30:01.25 spid183     * hkengine                       00007FFC89280000  00007FFC89975FFF  006f6000
2022-05-26 06:30:01.25 spid183     * SHLWAPI                        00007FFCAC0C0000  00007FFCAC111FFF  00052000
2022-05-26 06:30:01.25 spid183     * ncryptprov                     00007FFCA0AE0000  00007FFCA0B39FFF  0005a000
2022-05-26 06:30:01.25 spid183     * msv1_0                         00007FFCA79B0000  00007FFCA7A26FFF  00077000
2022-05-26 06:30:01.25 spid183     * NtlmShared                     00007FFCA79A0000  00007FFCA79ACFFF  0000d000
2022-05-26 06:30:01.25 spid183     * cryptdll                       00007FFCA7AA0000  00007FFCA7AB4FFF  00015000
2022-05-26 06:30:01.25 spid183     * kerberos                       00007FFCA7AF0000  00007FFCA7BF3FFF  00104000
2022-05-26 06:30:01.25 spid183     * schannel                       00007FFCA74E0000  00007FFCA7563FFF  00084000
2022-05-26 06:30:01.25 spid183     * SECURITY                       000001D78EFE0000  000001D78EFE2FFF  00003000
2022-05-26 06:30:01.25 spid183     * MSCOREE                        00007FFC9B6B0000  00007FFC9B713FFF  00064000
2022-05-26 06:30:01.25 spid183     * mscoreei                       00007FFC98180000  00007FFC9821BFFF  0009c000
2022-05-26 06:30:01.25 spid183     * SqlServerSpatial150            00007FFC8ACF0000  00007FFC8AD91FFF  000a2000
2022-05-26 06:30:01.25 spid183     * clbcatq                        00007FFCA9B50000  00007FFCA9BF1FFF  000a2000
2022-05-26 06:30:01.25 spid183     * msxml3                         00007FFC8AAB0000  00007FFC8ACEAFFF  0023b000
2022-05-26 06:30:01.25 spid183     * ualapi                         00007FFCA0FA0000  00007FFCA0FB9FFF  0001a000
2022-05-26 06:30:01.25 spid183     * SHELL32                        00007FFCAA240000  00007FFCAB738FFF  014f9000
2022-05-26 06:30:01.25 spid183     * shcore                         00007FFCA97E0000  00007FFCA9887FFF  000a8000
2022-05-26 06:30:01.25 spid183     * ESENT                          00007FFCA0C70000  00007FFCA0F92FFF  00323000
2022-05-26 06:30:01.25 spid183     * ntmarta                        00007FFCA71F0000  00007FFCA7220FFF  00031000
2022-05-26 06:30:01.25 spid183     * windows.storage                00007FFCA8D60000  00007FFCA94A7FFF  00748000
2022-05-26 06:30:01.25 spid183     * powrprof                       00007FFCA82B0000  00007FFCA830CFFF  0005d000
2022-05-26 06:30:01.25 spid183     * msoledbsql                     00007FFC8A7E0000  00007FFC8AA54FFF  00275000
2022-05-26 06:30:01.25 spid183     * COMDLG32                       00007FFCA9890000  00007FFCA99B6FFF  00127000
2022-05-26 06:30:01.25 spid183     * COMCTL32                       00007FFC8A730000  00007FFC8A7D8FFF  000a9000
2022-05-26 06:30:01.25 spid183     * MSOLEDBSQLR                    000001D791460000  000001D791481FFF  00022000
2022-05-26 06:30:01.25 spid183     * dhcpcsvc6                      00007FFCA4B90000  00007FFCA4BA5FFF  00016000
2022-05-26 06:30:01.25 spid183     * sqlncli11                      00007FFC8A3D0000  00007FFC8A722FFF  00353000
2022-05-26 06:30:01.25 spid183     * MSVCR100                       0000000074D40000  0000000074E11FFF  000d2000
2022-05-26 06:30:01.25 spid183     * SQLNCLIR11                     000001D7914C0000  000001D7914F7FFF  00038000
2022-05-26 06:30:01.25 spid183     * netbios                        00007FFC8D7F0000  00007FFC8D7FBFFF  0000c000
2022-05-26 06:30:01.25 spid183     * sqlnclirda11                   00000000749E0000  0000000074D38FFF  00359000
2022-05-26 06:30:01.25 spid183     * SQLNCLIRDAR11                  000001D791510000  000001D791547FFF  00038000
2022-05-26 06:30:01.25 spid183     * clr                            00007FFC940F0000  00007FFC94B2AFFF  00a3b000
2022-05-26 06:30:01.25 spid183     * MSVCR120_CLR0400               00007FFC93B00000  00007FFC93BF6FFF  000f7000
2022-05-26 06:30:01.25 spid183     * clrjit                         00007FFC9B370000  00007FFC9B49AFFF  0012b000
2022-05-26 06:30:01.25 spid183     * BatchParser                    00007FFC8A3A0000  00007FFC8A3C9FFF  0002a000
2022-05-26 06:30:01.25 spid183     * SqlAccess                      00007FFC8A320000  00007FFC8A395FFF  00076000
2022-05-26 06:30:01.25 spid183     * SRVCLI                         00007FFC9FCF0000  00007FFC9FD15FFF  00026000
2022-05-26 06:30:01.25 spid183     * ftimport                       0000000060000000  0000000060024FFF  00025000
2022-05-26 06:30:01.25 spid183     * MSFTE                          0000000049980000  0000000049D2DFFF  003ae000
2022-05-26 06:30:01.25 spid183     * mskeyprotect                   00007FFC9B4A0000  00007FFC9B4B4FFF  00015000
2022-05-26 06:30:01.25 spid183     * mswsock                        00007FFCA7A30000  00007FFCA7A96FFF  00067000
2022-05-26 06:30:01.25 spid183     * ntdsapi                        00007FFCA1550000  00007FFCA1577FFF  00028000
2022-05-26 06:30:01.25 spid183     * DSPARSE                        00007FFCA24C0000  00007FFCA24CCFFF  0000d000
2022-05-26 06:30:01.25 spid183     * rasadhlp                       00007FFCA2BF0000  00007FFCA2BF9FFF  0000a000
2022-05-26 06:30:01.25 spid183     * fwpuclnt                       00007FFCA4B10000  00007FFCA4B88FFF  00079000
2022-05-26 06:30:01.25 spid183     * ncryptsslp                     00007FFC9B580000  00007FFC9B5A3FFF  00024000
2022-05-26 06:30:01.25 spid183     * xpsqlbot                       00007FFC89FA0000  00007FFC89FA9FFF  0000a000
2022-05-26 06:30:01.25 spid183     * xpstar                         00007FFC89F20000  00007FFC89F91FFF  00072000
2022-05-26 06:30:01.25 spid183     * SQLSCM                         00007FFC8A2C0000  00007FFC8A2D3FFF  00014000
2022-05-26 06:30:01.25 spid183     * xpstar                         000001D79C2D0000  000001D79C2DCFFF  0000d000
2022-05-26 06:30:01.25 spid183     * SAMLIB                         00007FFC9FF10000  00007FFC9FF34FFF  00025000
2022-05-26 06:30:01.25 spid183     * Sort00060101                   00007FFCA2630000  00007FFCA2642FFF  00013000
2022-05-26 06:30:01.25 spid183     * System.Data                    00007FFC88BA0000  00007FFC88F07FFF  00368000
2022-05-26 06:30:01.25 spid183     * System.Transactions            00007FFC88B50000  00007FFC88B9EFFF  0004f000
2022-05-26 06:30:01.25 spid183     * xplog70                        00007FFCA4180000  00007FFCA4195FFF  00016000
2022-05-26 06:30:01.25 spid183     * xplog70                        000001D79D0A0000  000001D79D0A3FFF  00004000
2022-05-26 06:30:01.25 spid183     * oledb32                        00007FFC8AED0000  00007FFC8AFBCFFF  000ed000
2022-05-26 06:30:01.25 spid183     * MSDART                         00007FFCA26B0000  00007FFCA26D6FFF  00027000
2022-05-26 06:30:01.25 spid183     * Comctl32                       00007FFC85500000  00007FFC85778FFF  00279000
2022-05-26 06:30:01.25 spid183     * comsvcs                        00007FFC937D0000  00007FFC93976FFF  001a7000
2022-05-26 06:30:01.25 spid183     * ACEOLEDB                       00007FFC86DB0000  00007FFC86E30FFF  00081000
2022-05-26 06:30:01.25 spid183     * MSVCR90                        0000000074930000  00000000749D2FFF  000a3000
2022-05-26 06:30:01.25 spid183     * mso                            00007FFC784A0000  00007FFC79BDCFFF  0173d000
2022-05-26 06:30:01.25 spid183     * msi                            00007FFC78010000  00007FFC78491FFF  00482000
2022-05-26 06:30:01.25 spid183     * srpapi                         00007FFCA2220000  00007FFCA2249FFF  0002a000
2022-05-26 06:30:01.25 spid183     * ACECORE                        00007FFC83960000  00007FFC83C54FFF  002f5000
2022-05-26 06:30:01.25 spid183     * MSVCP90                        0000000074850000  0000000074922FFF  000d3000
2022-05-26 06:30:01.25 spid183     * ACEWSTR                        00007FFC86CD0000  00007FFC86DA4FFF  000d5000
2022-05-26 06:30:01.25 spid183     * MSORES                         000001D79F2F0000  000001D7A381AFFF  0452b000
2022-05-26 06:30:01.25 spid183     * MSOINTL                        000001DC12AC0000  000001DC12D29FFF  0026a000
2022-05-26 06:30:01.25 spid183     * ACEINTL                        00007FFCA21E0000  00007FFCA2212FFF  00033000
2022-05-26 06:30:01.25 spid183     * msxml6                         00007FFC861C0000  00007FFC86416FFF  00257000
2022-05-26 06:30:01.25 spid183     * odbccp32                       00007FFC8A080000  00007FFC8A0A5FFF  00026000
2022-05-26 06:30:01.25 spid183     * sqlvdi                         00007FFCA23C0000  00007FFCA23FAFFF  0003b000
2022-05-26 06:30:01.25 spid183     *
2022-05-26 06:30:01.25 spid183     *     P1Home: 000001EA00000000:  
2022-05-26 06:30:01.25 spid183     *     P2Home: 00007FFC95D66469:  059647840F58F883  40245C8B48C03200  C483484824748B48  9090909090C35F30  4C90909090909090  415541544157DC8B  
2022-05-26 06:30:01.25 spid183     *     P3Home: 000001EAC1888230:  00007FFC975C9F10  0000000000000000  0000000000000000  000001EAC1888280  000001EAC1888290  0024000600000000  
2022-05-26 06:30:01.25 spid183     *     P4Home: 0000002C825F0930:  000000000000002C  0000000000000000  FFFFFFF76430E090  000001EAC1889FD0  0000000000000000  000001EAC1889CE0  
2022-05-26 06:30:01.25 spid183     *     P5Home: FFFFFFFFFFFFFF00:  
2022-05-26 06:30:01.25 spid183     *     P6Home: 000001E225BB5D00:  0000000000000000  FFFFFFFF00000000  0000000000000000  0000000000000000  0000000000000000  0000000000000000  
2022-05-26 06:30:01.25 spid183     * ContextFlags: 000000000010005F:  
2022-05-26 06:30:01.25 spid183     *      MxCsr: 0000000000001FA8:  
2022-05-26 06:30:01.25 spid183     *      SegCs: 0000000000000033:  
2022-05-26 06:30:01.25 spid183     *      SegDs: 000000000000002B:  
2022-05-26 06:30:01.25 spid183     *      SegEs: 000000000000002B:  
2022-05-26 06:30:01.25 spid183     *      SegFs: 0000000000000053:  
2022-05-26 06:30:01.25 spid183     *      SegGs: 000000000000002B:  
2022-05-26 06:30:01.25 spid183     *      SegSs: 000000000000002B:  
2022-05-26 06:30:01.25 spid183     *     EFlags: 0000000000010206:  
2022-05-26 06:30:01.25 spid183     *        Rax: 000001EAC1889FFC:  
2022-05-26 06:30:01.25 spid183     *        Rcx: 0000000000000072:  
2022-05-26 06:30:01.25 spid183     *        Rdx: 0000000000000072:  
2022-05-26 06:30:01.25 spid183     *        Rbx: 000001EAC1888230:  00007FFC975C9F10  0000000000000000  0000000000000000  000001EAC1888280  000001EAC1888290  0024000600000000  
2022-05-26 06:30:01.25 spid183     *        Rsp: 0000002C825F15D0:  000001EAC1888230  0000002C825F16D0  000001EAC1889FD0  0000000000000000  000001E5DDB48206  000001EA58FA7850  
2022-05-26 06:30:01.25 spid183     *        Rbp: 0000002C825F16D0:  00007FFC97573E08  0000E70000000004  000001DBE1359150  0000000700000010  000001000000000A  0000000000000000  
2022-05-26 06:30:01.25 spid183     *        Rsi: 000001EAC1889FD0:  002E006F00620064  0055005F006E0066  007800610054004B  0074006C0075004D  0069006C00700069  006000C400720065  
2022-05-26 06:30:01.25 spid183     *        Rdi: 000000000000002C:  
2022-05-26 06:30:01.25 spid183     *         R8: 0000000000000000:  
2022-05-26 06:30:01.25 spid183     *         R9: FFFFFFF76430E090:  
2022-05-26 06:30:01.25 spid183     *        R10: 000001EAC1889FD0:  002E006F00620064  0055005F006E0066  007800610054004B  0074006C0075004D  0069006C00700069  006000C400720065  
2022-05-26 06:30:01.25 spid183     *        R11: 0000000000000000:  
2022-05-26 06:30:01.25 spid183     *        R12: 000001EAC1889CE0:  00007FFC975C9BA0  BFF0000000000001  000001EAC1889C40  0000000000000001  000001EAC1889D08  000001EAC1889B80  
2022-05-26 06:30:01.25 spid183     *        R13: 000001EA58FA7850:  00007FFC974A1098  0000009100000001  000001DBE1340060  00000000000002D5  000001EA58FA7BB0  000001DBE1340060  
2022-05-26 06:30:01.25 spid183     *        R14: 000001EAC18882C0:  00007FFC97549C98  0000000000000001  000001DBE1340060  0000000000000000  0000000000000000  0000000000000000  
2022-05-26 06:30:01.25 spid183     *        R15: 0000000000000018:  
2022-05-26 06:30:01.25 spid183     *        Rip: 00007FFC96483D83:  F575007E3C834266  44C03305EBFF0345  0004C8858B48F88B  7889441070894800  000000031C40C718  E8000004B08D8D48  
2022-05-26 06:30:01.25 spid183     * *******************************************************************************
2022-05-26 06:30:01.25 spid183     * -------------------------------------------------------------------------------
2022-05-26 06:30:01.25 spid183     * Short Stack Dump
2022-05-26 06:30:01.27 spid183     00007FFC96483D83 Module(sqllang+0000000000903D83)
2022-05-26 06:30:01.27 spid183     00007FFC96483310 Module(sqllang+0000000000903310)
2022-05-26 06:30:01.27 spid183     00007FFC95D6BF6D Module(sqllang+00000000001EBF6D)
2022-05-26 06:30:01.27 spid183     00007FFC95D8C514 Module(sqllang+000000000020C514)
2022-05-26 06:30:01.27 spid183     00007FFC95D8C32B Module(sqllang+000000000020C32B)
2022-05-26 06:30:01.27 spid183     00007FFC95DA36A2 Module(sqllang+00000000002236A2)
2022-05-26 06:30:01.27 spid183     00007FFC95D8C32B Module(sqllang+000000000020C32B)
2022-05-26 06:30:01.27 spid183     00007FFC95D6C1DD Module(sqllang+00000000001EC1DD)
2022-05-26 06:30:01.27 spid183     00007FFC95D29ADD Module(sqllang+00000000001A9ADD)
2022-05-26 06:30:01.27 spid183     00007FFC95D6BC75 Module(sqllang+00000000001EBC75)
2022-05-26 06:30:01.27 spid183     00007FFC95D6C1DD Module(sqllang+00000000001EC1DD)
2022-05-26 06:30:01.27 spid183     00007FFC95D29ADD Module(sqllang+00000000001A9ADD)
2022-05-26 06:30:01.27 spid183     00007FFC95D6A9AF Module(sqllang+00000000001EA9AF)
2022-05-26 06:30:01.27 spid183     00007FFC95D29ADD Module(sqllang+00000000001A9ADD)
2022-05-26 06:30:01.27 spid183     00007FFC95E09598 Module(sqllang+0000000000289598)
2022-05-26 06:30:01.27 spid183     00007FFC95D29ADD Module(sqllang+00000000001A9ADD)
2022-05-26 06:30:01.27 spid183     00007FFC96490A9B Module(sqllang+0000000000910A9B)
2022-05-26 06:30:01.27 spid183     00007FFC96490945 Module(sqllang+0000000000910945)
2022-05-26 06:30:01.27 spid183     00007FFC964907ED Module(sqllang+00000000009107ED)
2022-05-26 06:30:01.27 spid183     00007FFC95D29BB0 Module(sqllang+00000000001A9BB0)

I'm trying to connect (on the same host) from SSMS 19.0.2 to a newly installed SQL Server 2022 developer edition instance. I am getting a weird internal error:

===================================

Internal connection fatal error. Error state: 15, Token : 23 (Microsoft.Data.SqlClient)

------------------------------
Program Location:

   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover, Boolean isFirstTransparentAttempt, Boolean disableTnir)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, ServerCertificateValidationCallback serverCallback, ClientCertificateRetrievalCallback clientCallback, DbConnectionPool pool, String accessToken, SqlClientOriginalNetworkAddressInfo originalNetworkAddressInfo, Boolean applyTransientFaultHandling)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at Microsoft.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides)
   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
   at Microsoft.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

I found [this](https://dba.stackexchange.com/questions/317116/microsoft-sql-server-2019-developer-edition-suddenly-throwing-internal-connectio) , and the answer suggests uninstalling KB5011048 (.Net Framework 4.8.1), but I do not have that version of .Net installed. Can someone point out what's wrong? *Edit:* I have made some progress. After fiddling with excluded port ranges, I now have SQL Server again listening on the default (1433) port. A Wireshark trace suggested that there was some sort of problem with a TLS handshake, so I changed the connection options to "Encrypt connection" and "Trust Server Certificate". Now I get a connection timeout in the post-login phase. If I use sqlcmd, the following happens:

> .\sqlcmd -S 'tcp:' -N true -C
read tcp 127.0.0.1:55499->127.0.0.1:1433: wsarecv: An existing connection was forcibly closed by the remote host.
read tcp 127.0.0.1:55499->127.0.0.1:1433: wsarecv: An existing connection was forcibly closed by the remote host.

In wireshark, I see TDS prelogin messages go back and forth, then the client sends what wireshark describes as a "TLS Exchange", to which the server sends a TCP ACK, and then closes the connection.

Since some time ago, I've started with MySQL so I don't know Workbench very well. That little red x next to the number of the line that indicates an error does not disappear, even though everything is okay and I fixed what was wrong. A simple example: select * project where name='Anna' and I can execute it but x won't disappear unless I delete everything and type again. This is very annoying and I can't concentrate because of always thinking about what should be wrong. Could somebody tell me what to do to fix this? :(

**MySQL 5.5.32, MyISAM** A LOAD DATA INFILE statement usually executes and returns normally, succeeding at loading the data. On rare occasion it fails, returning a generic syntax error, always indicating the same character as the problem spot. ERROR 1064 (42000) at line 36: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ull, @field_name)' **I have no reason to believe there is a syntax error** because the large majority of the time it succeeds, and it always succeeds on MySQL 5.5.19 and other versions. So all of these details might be red herrings. But, for what it's worth, that line in the statement is field_name = if(@field_name='None', null, @field_name); The question is whether this is a known bug, or a theoretically explainable behavior, and **not** what the syntax error is. Are there conditions in a database, or perhaps a file or filesystem, that could generate the same generic syntax error inconsistently but persistently like this?

If I become a MySQL DBA, will I have to deal all day with those kind of issues or do you have tips to prevent from breaking the whole replication? I received this message because I manuslly removed the database, and after that the php script removed it. >Last_SQL_Errno: 1133\ Error 'Can't find any matching row in the user table' on query.

I need some help of expert in Postgres. I'm getting a problem in my application. Problem: PG::InsufficientResources:

ERROR:  could not open shared memory segment "/PostgreSQL.1477116630": Too many open files in system
STATEMENT:  SELECT "work_orders".* FROM "work_orders" WHERE (created_at < '2025-04-07 19:58:00.668344' AND rascunho is true) ORDER BY "work_orders"."id" ASC LIMIT $1

I have tried some changes with AI help but no success. Here is my Postgres configuration: postgresql.conf:

listen_addresses                    = '*'
port                                = 5432
superuser_reserved_connections      = 3
unix_socket_directories             = '/var/run/postgresql, /tmp'
max_connections                     = 200
shared_buffers                      = 4864MB
effective_cache_size                = 14592MB
maintenance_work_mem                = 1216MB
checkpoint_completion_target        = 0.9
wal_buffers                         = 16MB
default_statistics_target           = 100
random_page_cost                    = 1.1
effective_io_concurrency            = 200
work_mem                            = 6225kB
huge_pages                          = off
min_wal_size                        = 1GB
max_wal_size                        = 4GB
max_worker_processes                = 10
max_parallel_workers_per_gather     = 4
max_parallel_workers                = 10
max_parallel_maintenance_workers    = 4
max_prepared_transactions           = 400

ulimit settings made in /etc/security/limits.conf:

postgres  soft  nofile  65535
postgres  hard  nofile  65535

root  soft  nofile  65535
root  hard  nofile  65535

nucleusdb soft  nofile  65535
nucleusdb hard  nofile  65535

Changes in the systemd service (/etc/systemd/system/postgresql.service.d/override.conf):

[Service]
LimitNOFILE=65535.

During the day I got a lot of these messages, here is a screen shot. 288 errors during 12 hours!

I am using SQL Server 2017 and the latest SSMS version. When I click securables of login in SSMS, I see this error: >Object reference not set to an instance of an object. (SqlMgmt) > >------------------------------ >Program Location: > > at Microsoft.SqlServer.Management.SqlMgmt.PermissionsData.Securable.GetImage(SecurableType type)\ at Microsoft.SqlServer.Management.SqlMgmt.PermissionsSecurableSelector.InitializeBitmaps() at Microsoft.SqlServer.Management.SqlMgmt.PermissionsSecurableSelector..ctor(IHelpProvider helpProvider, IServiceProvider serviceProvider, Principal principal, PermissionsDetailsGrid permissionsGrid, Object connectionInfo, Boolean yukonOrGreater)\ at Microsoft.SqlServer.Management.SqlMgmt.PermissionsOfPrincipalsCore.InitializeSecurableSelector()\ at Microsoft.SqlServer.Management.SqlMgmt.PermissionsOfPrincipalsCore..ctor(IHelpProvider helpProvider, IServiceProvider serviceProvider, Principal principal, Object connectionInfo, Boolean yukonOrGreater, Boolean showColumnPermissionsInDetailsGrid)\ at Microsoft.SqlServer.Management.SqlMgmt.PermissionsServerPrincipal.InitializePermissionsCore()\ at Microsoft.SqlServer.Management.SqlMgmt.PermissionsServerPrincipal.OnInitialization()\ at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SetView(Int32 index, TreeNode node)\ at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.OnBeforeSelection(Object sender, TreeViewCancelEventArgs e) What can be the problem? I first thought it might be permission problem, but even if I use sysadmin login, I see this error every time.

I have a million of rows of customers to be imported via SQL dump. Customer data will be inserted into main table customer and child table customer_address The dump contains the following SQL statements: **File**: customer-dump.sql BEGIN TRANSACTION; INSERT INTO customer (firstname, lastname) VALUES ('John', 'Doe'); INSERT INTO customer_address (customer_id, city, country) VALUES (LAST_INSERT_ID(), 'New York', 'USA'); COMMIT; BEGIN TRANSACTION; INSERT INTO customer (firstname, lastname) VALUES ('Lorem', 'Ipsum'); INSERT INTO customer_address (customer_id, city, country) VALUES (LAST_INSERT_ID(), 'Chicago', 'USA'); COMMIT; # So on for N no of customers I am importing via CLI as: mysql -u [user] -p [database] /tmp/customer-import-error.log **My Queries:** - How to continue the script execution even if there is a failure in some rows? - How to show/log errors for failed rows? - Any advice on such massive import?

I've been pouring over threads regarding this issue, but ours seems unique in that it's not an issue with the query but the row itself; or at least I couldn't find a similar topic addressing how to fix the row. A simple query like this: > update customer set customer_name = 'Health Net of CA' where customer_id = '15484'; Results in: ERROR 1406 (22001): Data too long for column 'customer_name' at row 1 Checking the character length: mysql> select char_length(customer_name) from customer where customer_id = '15484'; +----------------------------+ | char_length(customer_name) | +----------------------------+ | 54 | +----------------------------+ 1 row in set (0.00 sec) Describe shows: | customer_name | varchar(255) | YES | | NULL | | This database was populated using an import. I'm fairly sure strict mode was on but I didn't handle the import myself so I can't say for certain. This table has 39 columns, and most are Varchar(50) or tinyint so it shouldn't be an issue with the row being too big. Any suggestions on fixing these bad rows? Update: SHOW CREATE TABLE customer; | customer | CREATE TABLE customer ( customer_id int(11) NOT NULL AUTO_INCREMENT, customer_name varchar(255) DEFAULT NULL, customer_code varchar(12) DEFAULT NULL, customer_type text, bill_type text, attention varchar(100) DEFAULT NULL COMMENT 'Attention to who we deal biz with', address_id int(11) DEFAULT NULL, b_bad_debt tinyint(1) DEFAULT '0', b_fee_approval tinyint(1) DEFAULT NULL COMMENT 'boolean flag for Fee Approval 1=set, 0=unset', approval_amount decimal(5,2) DEFAULT NULL, notification varchar(45) DEFAULT NULL COMMENT 'notified customer by email / fax or ftp', b_tax_exempt tinyint(1) DEFAULT '0' COMMENT 'Tax Exempt Flag', sales_tax_number varchar(20) DEFAULT NULL COMMENT 'sales tax/ permit no.', b_prepay tinyint(1) DEFAULT NULL, create_date datetime DEFAULT NULL, last_updated timestamp NULL DEFAULT NULL, active tinyint(4) DEFAULT '1', created_by varchar(45) DEFAULT NULL, updated_by varchar(45) DEFAULT NULL, email varchar(45) DEFAULT NULL, email_extra mediumtext COMMENT 'extra emails as per creation', state_tax_code varchar(2) DEFAULT NULL COMMENT 'this is as CA if CA state and refer to TAX table', email_verified_by varchar(45) DEFAULT 'NA', fax_verified_by varchar(45) DEFAULT 'NA', b_always_send tinyint(1) DEFAULT '0' COMMENT 'there is customer that we need always send', b_project_customer tinyint(1) DEFAULT '0', b_exception_list tinyint(1) DEFAULT '0', b_has_inslist tinyint(1) DEFAULT '0', customer_passwrd varchar(255) DEFAULT NULL, delivery_opt varchar(45) DEFAULT NULL, max_fax_pages int(11) DEFAULT NULL, phone varchar(20) DEFAULT NULL, fax varchar(20) DEFAULT NULL, phone_extra mediumtext, phone_second varchar(20) DEFAULT NULL, b_multi_suites tinyint(1) DEFAULT '0', suite_list varchar(255) DEFAULT NULL, b_portal_download tinyint(1) DEFAULT '0', b_no_download tinyint(1) DEFAULT '0', PRIMARY KEY (customer_id), KEY customer_idx (customer_code,customer_name) ) ENGINE=InnoDB AUTO_INCREMENT=18870 DEFAULT CHARSET=utf8 |

I am learning basic SQL and have gotten stuck with triggers. I have a database with two tables, customer and invoice. The table characteristics follow:

CREATE TABLE customer (
	CUST_NUM		VARCHAR(8), 
    CUST_LNAME		VARCHAR(25),
    CUST_FNAME		VARCHAR(25),
    CUST_BALANCE	DECIMAL(9,2),
    PRIMARY KEY (CUST_NUM)
    );
    
CREATE TABLE invoice (
		INV_NUM		VARCHAR(10),
        CUST_NUM	VARCHAR(8)	NOT NULL,
        INV_DATE	DATE,
        INV_AMOUNT	DECIMAL(9,2),
        PRIMARY KEY (INV_NUM),
        FOREIGN KEY (CUST_NUM) REFERENCES customer (CUST_NUM)
        );

I am trying to create a trigger that will update the customer.CUST_BALANCE value after an insert in the invoice table. I am testing the trigger by entering values ('8005', '1001', '2018-04-27', '225.40') into Invoice This script:

DELIMITER $$
CREATE TRIGGER trg_updatecustbalance
AFTER INSERT ON invoice
FOR EACH ROW
BEGIN
	UPDATE customer
	SET customer.CUST_BALANCE=customer.CUST_BALANCE+NEW.invoice.INV_AMOUNT
    WHERE customer.CUST_NUM=NEW.invoice.CUST_NUM;
END; 
$$
DELIMITER ;

Yields Error Code: 1054. Unknown column 'new.invoice.CUST_NUM' The script:

DELIMITER $$
CREATE TRIGGER trg_updatecustbalance
	AFTER INSERT
	ON invoice FOR EACH ROW
BEGIN
	IF invoice.CUST_NUM=customer.CUST_NUM THEN 
    INSERT INTO customer
    VALUES (customer.CUST_BALANCE = customer.CUST_BALANCE + NEW.invoice.INV_AMOUNT);
    END IF;
END$$
DELIMITER ;

Yields Error Code: 1109. Unknown table 'invoice' in field list. I am looking for assistance in resolving this. Thanks! **ETA:** Edited to provide script for the tables and clarify script and errors of previous attempts.

I have duplicated the primary database to standby database and then I added the primary database in data broker configuration. But when I'm trying to add standby database I'm getting following error: DGMGRL> add database 'orcl_standby' as connect identifier is orcl_standby maintained as physical; Error: ORA-16606: unable to find property "" Error: ORA-16554: translation not valid Failed. Is this a problem with log_archive_dest_state_2? I have enable it. Or is there any problem in DR2ORCL.DAT files? Any help will be appreciated.

I am a DBA with local sysadmin rights, and sysadmin rights on the SQL instance. Up until recently, i have been able to connect to a SQL Instance without issue. All i am trying to do is connect to a SQL Instance using SSMS. Nothing fancy here - just normal login with Windows Authentication. Although this also occurs if using SQL Authentication. Now i am getting an error message "User does not have permission to perform this action (Error 15427)". My colleagues whom are also DBA's receive this same error. And the default SQL 'sa' account also receives this error. I have never seen something like this before and am having difficulty finding helpful responses as they all seem to be focusing on the error number rather than the symptoms i am experiencing. I can confirm that all Protocols are enabled and ordered as per our environment, and i can confirm that there have been no changes to this SQL Instance (that i am aware of). I can confirm the SQL Services are running and that permissions for the account running it have not changed (it is a gMSA). The saving grace is that this is in our Test environment so no Production data is at risk here. So i also have a great deal of flexibility in things i can try to resolve. Is someone able to please help me figure out what is going on here? Happy to provide further details if required, SQL Server: 2016, Version: 13.0.6435.1, Edition: Developer, Product Level: SP3, Cheers! Update - further testing/checks We have a user who is NOT a DBA. They are in an AD group that has read/write on a couple of DB's. They are able to connect to this SQL Instance. If i use their same machine, i am unable to connect to this SQL Instance. I can connect using other SQL Logins that DO NOT have sysadmin. If i use a SQL Login that DOES have sysadmin, i cannot connect. It seems like any login with sysadmin privileges is unable to connect??

I have two SQL Server 2016 instances (Instance A and Instance B) on the same server. Both instances have SSRS. At one point I upgraded Instance A to SQL Server 2019 but then due to the changes made to SSRS in 2019 I decided to bring Instance A back to 2016. I can connect to Instance A just fine on SQL Server 2016 Reporting Services Configuration Manager but now every time I try to connect to Instance B I receive this error: Report Server WMI Provider error: Invalid namespace. I've done some research and can't find a situation exactly like this. Does anyone know of a fix for this or have an idea of where I could find some more information on the problem? Before I try uninstalling and reinstalling SSRS on Instance B I wanted to see if I could find a fix that didn't require uninstalling and reinstalling.

I am using MySQL with XAMPP. For sometime now I keep getting a server unavailable error and upon digging deeper I noticed that my mysql.tables_priv table index is corrupted (ARIA Database Type). I have tried running aria_chk and myisamchk to repair, but to no avail. I have also tried mysql_upgrade but again this didn't help. The only thing I can think of now is to manually remove the tables_priv.MAD file from xampp\mysql\data\mysql folder, create an empty one and REPAIR TABLE tables_priv. Can you kindly advise if that is the right and safe approach to take? Also, if you have any other suggestion then please do mention.

I'm trying to migrate a simple MySQL test database to Oracle 19c using the migration wizard available in Oracle SQL Developer, the result is that the procedure create the user and the tables but the tables are empty and i receive the following error "ORA-00942 table or view does not exist". 2023-01-25T08:52:10.649730400Z 730400 oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle INFO oracle.dbtools.migration.convert.ConverterWorker Eseguito il coalesce del catalogo MySQL, schema test nello schema singolo test Convert.COALESCED oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle MySQL test test oracle.dbtools.migration.workbench.core.logging.LogInfo@61735376 2023-01-25T08:52:11.575035900Z 35900 oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle INFO oracle.dbtools.migration.core.util.MultiLevelLogManager Colonna 'number' modificato in 'number_' (Caratteri non validi, parola riservata o conflitto) oracle.dbtools.migration.workbench.core.logging.LogInfo@61735376 2023-01-25T08:52:14.770235800Z 235800 oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle INFO oracle.dbtools.migration.workbench.core.ui.FullMigrateTask Conversione completata in 0 secondi oracle.dbtools.migration.workbench.core.logging.LogInfo@61735376 2023-01-25T08:52:20.872501Z 501000 oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle SEVERE oracle.dbtools.migration.workbench.core.logging.MigrationLogUtil Generation phase ORA-00942: tabella o vista inesistente oracle.dbtools.metadata.persistence.PersistableObject.doUpdate(PersistableObject.java:364) oracle.dbtools.metadata.persistence.PersistableObject.save(PersistableObject.java:186) oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doGenerate(FullMigrateTask.java:1303) oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doMaskBasedActions(FullMigrateTask.java:437) oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doWork(FullMigrateTask.java:321) oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doWork(FullMigrateTask.java:154) oracle.dbtools.raptor.backgroundTask.RaptorTask.call(RaptorTask.java:199) java.base/java.util.concurrent.FutureTask.run(Unknown Source) oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:702) java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) java.base/java.util.concurrent.FutureTask.run(Unknown Source) java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.base/java.lang.Thread.run(Unknown Source) oracle.dbtools.migration.workbench.core.logging.LogInfo@15963e4b oracle.dbtools.migration.workbench.core.ui.FullMigrateTask$FullMigrateTaskException: Generation phase ORA-00942: tabella o vista inesistente oracle.dbtools.metadata.persistence.PersistableObject 364 oracle.dbtools.metadata.persistence.PersistableObject 186 oracle.dbtools.migration.workbench.core.ui.FullMigrateTask 1303 oracle.dbtools.migration.workbench.core.ui.FullMigrateTask 437 oracle.dbtools.migration.workbench.core.ui.FullMigrateTask 321 oracle.dbtools.migration.workbench.core.ui.FullMigrateTask 154 oracle.dbtools.raptor.backgroundTask.RaptorTask 199 java.util.concurrent.FutureTask oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask 702 java.util.concurrent.Executors$RunnableAdapter java.util.concurrent.FutureTask java.util.concurrent.ThreadPoolExecutor java.util.concurrent.ThreadPoolExecutor$Worker java.lang.Thread 2023-01-25T08:52:20.877506400Z 506400 oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle WARNING oracle.dbtools.migration.workbench.core.ui.FullMigrateTask L'esecuzione dello script generato include errori: FAILED : Migrazione del database : FAILED oracle.dbtools.migration.workbench.core.logging.LogInfo@2b459c32 MySQL queries: CREATE DATABASE test /*!40100 COLLATE 'utf8_general_ci' */; CREATE TABLE test ( number INT(11) NULL DEFAULT NULL, string VARCHAR(50) NULL DEFAULT NULL ) ENGINE=InnoDB; INSERT INTO test.test (number, string) VALUES ('1', 'test'); INSERT INTO test.test (number, string) VALUES ('2', 'test'); This is the master.sql generated from the wizard: SET ECHO ON SET VERIFY ON SET FEEDBACK ON SET DEFINE ON CLEAR SCREEN set serveroutput on COLUMN date_time NEW_VAL filename noprint; SELECT to_char(systimestamp,'yyyy-mm-dd_hh24-mi-ssxff') date_time FROM DUAL; spool "Test5_&filename..log" -- Password file execution @passworddefinition.sql PROMPT Dropping Role ROLE_Test5 ... DROP ROLE ROLE_Test5 ; PROMPT Creating Role ROLE_Test5 ... CREATE ROLE ROLE_Test5 ; -- PROMPT Drop test user -- drop user test cascade; PROMPT Create user test CREATE USER test IDENTIFIED BY &&test_password PASSWORD EXPIRE ACCOUNT LOCK /* DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP */; GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM, UNLIMITED TABLESPACE TO test; -- PROMPT Drop Emulation user -- drop user Emulation cascade; PROMPT Create user Emulation CREATE USER Emulation IDENTIFIED BY &&Emulation_password PASSWORD EXPIRE ACCOUNT LOCK /* DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP */; GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM, UNLIMITED TABLESPACE TO Emulation; set define on prompt connecting to Emulation alter session set current_schema=Emulation; set define off set define on prompt connecting to test alter session set current_schema=test; set define off -- DROP TABLE test CASCADE CONSTRAINTS; PROMPT Creating Table test ... CREATE TABLE test ( number_ NUMBER(10,0), string VARCHAR2(50 CHAR) ); GRANT ALL ON test TO ROLE_Test5; set define on prompt connecting to test alter session set current_schema=test; set define off spool off; COMMIT; I've also tryied to create the user and grant unlimited quota on all the table_spaces but the result is the same. Anyone have an idea of what could be the problem?

Every time I reboot Windows, for some databases I get this error: > The operating system returned error 21(The device is not ready.) 1. I checked the disk with chkdsk /r - no bad sectors. 2. I executed DBCC CHECKDB with no errors: *(CHECKDB found 0 allocation errors and 0 consistency errors in database)* 3. If I restart SQL Server the errors disappear. Windows 10 and SQL Server 2016 Express.