I recently came across this little gem of an SQL query for MariaDB: SHOW GLOBAL VARIABLES LIKE 'log_error'; I get that there are tons of bots on the Internet and so I expected what I saw on my live server. However my local server on my home connection + VPN has a ton of bot requests too! I want to be explicitly clear: I do not remote in to my home system what-so-ever. I want to completely lock MariaDB down from external access and whitelist localhost, ::1 and maybe one network IP when I test from my Mac on rare occasion. I know MariaDB users are tied to a host/IP but that is for internal commands. I know I can change the port number and that should be easy enough. But that feels like something to do in combination. I simply want to only whitelist three IP addresses to ever be able to access MariaDB. I've also disabled public access to MariaDB in the Windows Firewall. **How do I lock down MariaDB so it is not accessible to external hosts?** A small sample of the nonsense I'm seeing in the log: > 2025-05-07 18:29:28 6475 [Warning] Hostname 'rnd.group-ib.com' does > not resolve to '80.82.70.133'. 2025-05-07 18:29:28 6475 [Note] > Hostname 'rnd.group-ib.com' has the following IP addresses: 2025-05-07 > 18:29:28 6475 [Note] - 5.9.185.30 > > 2025-05-08 6:36:50 7001 [Warning] IP address '34.77.36.4' has been > resolved to the host name '4.36.77.34.bc.googleusercontent.com', which > resembles IPv4-address itself. > > 2025-05-08 19:51:43 7176 [Warning] Aborted connection 7176 to db: > 'unconnected' user: 'unauthenticated' host: '91.223.169.88' (This > connection closed normally without authentication) > > 2025-05-08 20:46:33 7283 [Warning] Aborted connection 7283 to db: > 'unconnected' user: 'unauthenticated' host: '103.203.57.18' (This > connection closed normally without authentication) > > 2025-05-10 12:14:01 7840 [Warning] Host name 'hn.kd.ny.adsl' could not > be resolved: No such host is known. > > 2025-05-10 13:02:33 7842 [Warning] IP address '198.235.24.242' could > not be resolved: No such host is known. ---------- It's been five hours and eight minutes since I changed the port number and the nearly minute-by-minute ..."events" have completely stopped. That, of course, does not negate the opportunity to learn how else I can strengthen the security of MariaDB on Windows. ---------- dbdemon's answer did not include the exact syntax so I'll clarify what works and how I verified it here: #Block all IP addresses except the same computer: bind-address = 127.0.0.1,::1 I restarted MariaDB and it worked. But I did not know if it would actually block anything so I did the inverse to specify IP addresses I'm not using to intentionally get blocked and thus verify that this will work: #Intentionally test the format to blocking local access: bind-address = 3.4.5.6,7.5.3.2 ...which does work which verifies that the first bind-address line *does* work.

I created a test query to do some counting but five minutes of execution time is ridiculous! So I figured there must be a maximum execution time setting somewhere however the two things I found and tried failed: 1. max_execution_time = 2 2. max_statement_time = 2 I attempted to place these in all three sections in my my.ini settings file and restarted the MariaDB service on Windows to verify if it worked (it didn't). MariaDB states that it will stop all queries unlike MySQL that only stops SELECT queries. **How do I force MariaDB to terminate long-running SQL queries?** I want to define this in the my.ini setting file; I do *not* want to define this in the command line call. **Update 1:** This update to my registry based command works but I don't want to set this configuration in the command line, it belongs in the configuration file: "C:\MariaDB\bin\mysqld.exe" "--defaults-file=C:\MariaDB\data\my.ini" "--max_statement_time=4" "MariaDB"

I am doing resiliency tests for processes that easily take long enough that the user will just walk away and come back minutes if not hours later. I need to emulate something in my system failing so I can ensure my software will wait a few seconds and make a limited number of attempts to reconnect and finish this long-running task. What is not fine is when I manually stop the MariaDB service in Windows it is restarted! I didn't even know it at first except my log viewer was showing database activity, so I pressed F5 and yup, it was started again. Now, yes, I know service recovery is important in most scenarios, but now it's hurting my productivity. I presume there is a setting for the my.ini configuration file though I haven't been able to track down any relevant documentation. There also appears to be no non-default settings in the service properties. How do I prevent MariaDB from restarting the service after I've manually stopped it on Windows?

Background - I am using XAMPP, which has MariaDB on my Windows development machine. I cant remove this as I have a number of projects that depend and use this. On my new project on AWS EC2, Windows Server, I have IIS and MySql installed. Issue - 1. When I try my DB modifications on the dev machine, they don't always transfer over. I have to tweak them. 2. To confirm that my DB is identical to the Production one, I would like to backup the DB on the real server and restore it on my machine. But this is even worse, too many changes ae required. Question - How can I run both Maria and MySQL on my Dev machine? - MariaDB needs to remain unaffected - MySQL does not have to run with Apache, the Development IDE has its own webserver for debugging. - They both need to be available. Some projects will use MySQL, others will use MariaDB. No project will use both simultaneously. Note - I hadn't tried installing MySQL, as I didn't want MariaDB to break - which would affect other projects.

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.

I would like to install a second instance of MariaDB with MSI-Installer (Windows 10). The first instance is on drive C. When I want to install the second instance on drive D using MSI-Installer the installer recognizes that there is already an installation and asks if I want change/repair/remove. How can avoid this step and get the installation option? Windows 10/ MariaDB 10.6.8

I am using Windows 10, language Serbian, SQL Management Studio 2016 and can't use Database reports because there is error: > An error occurred during local report processing Culture is not > supported Parameter name: culture 3072 (0x0c00) is invalid culture > identifier. I try with different settings for Windows 10 - language (English), try with different settings for SSMS (English) but got same error. Do you have idea how to solve this? P.S. My Windows 10 system locale settings: Get-WinSystemLocale LCID Name DisplayName ---- ---- ---- 9242 sr-Latin-RS Serbian(Latin, Serbia)

I have to run SQL Server 2008 R2 on Windows 10 but it is not supported and so I am not getting any updates. Installing a later version of SQL Server is not an option. I can find all the service packs and cumulative updates online. **Questions:** 1. Is there a way to get updates automatically? 2. If not, do I have to install all the service packs in sequence, or can I install only the most recent.

I get this error message when I try to install PostgreSQL on my Windows machine. I tried all the provided solutions for solving this issue. I have uninstalled my McAfee antivirus as I wasn't using it anymore. I'm writing here after many failed attempts. It will be great if someone who has encountered this problem could answer my question. **Update:** I have found out that Windows security is the actual problem stopping the installation. As soon as I turn off my real-time protection, the app runs, but the moment I turn up the active protection, pgAdmin is not opening.

I need to load data into a table as fast as possible. So far I've done the following. - Create the table UNLOGGED - Removed all indexes - Removed all triggers - Created the table in a tablespace on a SSD hard disk - DML tuned for multiple records per INSERT statement Some background info.... the data is loaded into the system via powershell script reading from a remote data-stream. The data arrives at a variable rate 24*7, slowly during the evening, nighttime and morning, increasing during office hours (up to 2000 records/second or more). During busy-periods the system focuses on just reading the stream and loading the data. during quieter periods the system reads, processes and then deletes the data. The table gets truncated every night, and normally peaks at around 20 million rows on a busy day. The system can currently cope with a maximum of about 2400 records/second. Are there any other techniques that might squeeze a little more speed out of the system?

Postgresql service refuses to start if the data folder (PGDATA) doesn't belong exclusively to the postgres user (i.e. permissions = 700). **Is there any way to disable or circumvent that condition?** Ideally I would like postgresql to start even if the permissions on that folder is set to 777. Explanations: I have built a Docker image with a running instance of Postgresql. The requirements are: - a) the container should be able to run on Windows Home edition (which means Docker for Windows is not an option and we have to use docker-machine and VirtualBox) - b) the user should use Kitematic to download and run the Image, without any need to go to the command line or do any post-install configuration (i.e. it should work out of the box). This means that I only have control over what happens within the container running Psql; I can't change the VM or Windows configs. - c) the database must be stored on a data volume mounted on the file system of the host OS (because I want the container to be disposable and upgradable) a) and b) works perfectly well. But as soon as the user enables the Data Volume in Kitematic (condition c) ) Postgres refuses to start because the owner of the DB folder is reset to 1000:staff which are the default user and group in boot2docker Virtal Machine. There is no way to programmatically change the owner or permissions inside the VirtualMachine due to the way VBox shares the folder with Windows (via a vboxfs mount). So basically within the container I'm stuck with a PGDATA folder with full access to everyone (i.e. 777, which is not a really an issue in itself since the data is not sensitive and not exposed to other machines).

I'm running a VM with Windows 10 32 bit OS and I need to install SQL Server Management Studio. The OS on my VM OS Name: Microsoft Windows 10 Pro OS Version: 10.0.19044 N/A Build 19044 The install for the last version fails with an error, the log shows that it fails installing the x64 redistributables the site for the download shows that the compatible OS are https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms Windows 11 (64-bit) Windows 10 (64-bit) version 1607 (10.0.14393) or later Windows 8.1 (64-bit) Windows Server 2022 (64-bit) Windows Server 2019 (64-bit) Windows Server 2016 (64-bit) Windows Server 2012 R2 (64-bit) Windows Server 2012 (64-bit) Windows Server 2008 R2 (64-bit) I'm struggling to find what is the latest version of SSMS compatible with Windows 10 32 bit version

MariaDB 10.7 service suddenly stopped in Windows 10 after a crash and the service is not starting. The pop up shows 'windows cannot start mariadb service). The windows event viewer gives the following data: - InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery. - InnoDB: Page [page id: space=0, page number=366] log sequence number 424180275 is in the future! Current system log sequence number 408454168. - InnoDB: unsupported undo header type 16 - InnoDB: Plugin initialization aborted with error Data structure corruption - Plugin 'InnoDB' init function returned error. - Plugin 'InnoDB' registration as a STORAGE ENGINE failed. - Unknown/unsupported storage engine: InnoDB - InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT for tablespace 251 Cannot restart the MaraDB service.

I have a SQL Server 2005 database that I can see in SQL Server Management Studio Express. There is a front end application, but since the upgrade to Windows 10, I cannot access the database with it. In SQL Server Management Studio Express there are no object folders listed for the database - and the summary shows 0 items. The database folder has a correctly named mdf file of 197MB. I have very little experience of SQL Server so would appreciate any pointers.

I have a large number of databases in postgresql 9.5 which I want to back-up using pg_dump tool. Each back-up should get its name from the corresponding database. when I run

SELECT datname FROM pg_database WHERE datistemplate=false and datname!='postgres';

in a psql terminal, it displays all the database names correctly. My issue now is how to use it in pg_dump inside a loop (if required,in a batch script) such that each database is backed up with its corresponding name. Something like this:

FOR %%d IN ("SELECT datname FROM pg_database WHERE datistemplate=false and datname!='postgres'") DO(
	
	%pgdump% %%d -f %%d.backup
)

when I run this, nothing happens. I am using windows 10 and I'd greatly appreciate any help/hint. Thank you.

I'm currently using the latest version of SSMS (17.8.1) on windows 10 and everytime I try to create a database diagram it crashes without giving me any error message. I've already tried to re-install SSMS but the problem still occurs.

I have installed postgresql 14 on a Windows 10 machine. But, I'm getting this message: C:\Program Files\PostgreSQL\14\bin > pg_ctl.exe start -D "C:\postgres" pg_ctl: directory "C:/postgres" is not a database cluster directory The installation log file at %temp%\install-postgresql.log shows this text at the very end: > Error running C:\WINDOWS\System32\cscript //NoLogo "C:\Program > Files\PostgreSQL\14/installer/server/initcluster.vbs" "NT > AUTHORITY\NetworkService" "postgres" "****" > "C:\Users\nephewtom\AppData\Local\Temp/postgresql_installer_80ce3934c2" > "C:\Program Files\PostgreSQL\14" "C:\Program Files\PostgreSQL\14\data" > 5432 "DEFAULT" 0: Program ended with an error exit code Problem > running post-install step. Installation may not complete correctly > The database cluster initialisation failed. Setting variable whoami > from C:\WINDOWS\System32\whoami Script exit code: 0 I suspect it may be due to a permissions issue. Checking the troubleshoot guide here , it suggests to use cscript.exe, but that failed.

To clarify, I am using plain Postgres as packaged by EnterpriseDB (with StackBuilder), *not* EDB Postgres Advanced Server. I'm familiar with using pg_lsclusters, pg_dropcluster, and pg_createcluster on Linux. These tools don't seem to be installed by the Windows x86-64 EnterpriseDB installer (not recognized at the command line), and I don't see any graphical tools that are added to the Start Menu by the installer (which includes the StackBuilder, a Reload Configuration shortcut, and a psql Console).

Because reasons (tm), we want to identify the client's MAC address on SQL Server side (local network, not about security, enables a very convenient feature in way transparent for applications). We do that by querying net_address from master.dbo.sysprocesses. All clients are set up to use TCP/IP connections, the address value has always been correct, and all connections from the same computer have always had the same net_address. In Windows 10 clients, however, every single connection gets its own net_address, and they do not repeat. The only pattern we can see about these addresses is that the last two digits remain the same within approximately 6 seconds. So if another connection gets assigned with EBC1E384F4C2, all subsequent connections' addresses will also end with C2 until the 6 seconds elapse, then the suffix changes for another 6 seconds. We have tried in various combinations: - running cliconfg.exe and making sure only TCP/IP is enabled, and that there is an alias for the server name that is also set to use TCP/IP - disabling and enabling back connection pooling in the ODBC Data Sources - adding and removing Network Library=DBMSSOCN or Network=DBMSSOCN to and from the connection properties, depending on the connection type - setting and removing a fixed MAC address in the network adapter properties - removing and adding back TCP/IP v6 support from and to the network connection properties - reading about MAC randomization in Windows 10 which claims it only applies to Wi-Fi connections, and we only have wired connections Nothing seemed to have any effect. The only thing that did seem to have effect is: - You **toggle** the connection pooling status in ODBC Data Sources (does not matter if it was on or off, what matters is that you flip the status to the opposite), *but only provided that* - The system has been running for at least about 12 minutes after startup. If you flip the pooling status earlier than that, it will seemingly not have any effect. The moment you do that, the addresses stop changing, but they do not revert to the actual MAC address of the network adapter, instead they freeze at whatever values they had when the freeze happened, and from then on each application will receive the same MAC for all its subsequent connections, but that MAC will be different among different application on the same device. If you close and run an application again, it will receive its frozen MAC address again as if you never closed it. --- What is going on? How do we stop it from happening so that TCP/IP connections properly use the network adapter's MAC as opposed to a random address? Alternatively, is there a better way to reliably identify and distinguish client devices (not users) on a local network from SQL Server (e.g. hostname is no good because it depends on the connection string)?

I run Postgres 12 service in Windows Subsystem for Linux 2 (WSL2). In my /etc/postgresql/12/main/postgresql.conf, I have:

listen_addresses = '*'

while my /etc/postgresql/12/main/pg_hba.conf has this content:

local   all    postgres                 peer

local   all    all                      peer
host    all    all         0.0.0.0/0    md5
host    all    all         ::0/0        md5

host    all    all         0.0.0.0/0    md5
host    all    all         ::0/0        md5
host    all    all         all          md5

If I try to connect to this server from any other device then the local machine, it times out. Does anyone have any idea why should this be?