I have a database running on a VM which is getting hammered during a large load, in particular I can see waits of WRITELOG happening. My initial thought is to split the files out on to their own drives but the backend storage is the same as where the other DB files are sitting. Basically it is SAN presented as a Cluster Shared Volume to a whole host of virtual machines. Would there be a performance advantage in doing this? Some memory in the depths of my brain is telling me something about the number of IO streams would be better potentially? ***************************************************************************** To update this I have now separated out the files and correctly sized the transaction log. I have been collecting information from sys.dm_io_virtual_file_stats and can see that I now have extremely high readIOStalls but with a low latency of 13ms. I also collected some memory information and PLE was in the thousands on average with this being a 32GB system I would expect that apart from in one 30min period where it drops right down to 30 before climbing sharply again, at this time lazy write/sec increases to 50 also before reducing to 0. Could this period be the cause of the large number of read stalls I am seeing? I would have expected to see with such high Read Stalls also high latency?

A few times a day, it is not able to connect and the error mentions: > Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. There is is large Microsoft article that suggests: To resolve this issue, upgrade the .NET Framework 4.5.1 to the Microsoft .NET Framework 4.5.2 Our SQL Server 2012 is running on VMWare and we have not been able to get much help from them even though we provided a lot of info that points to their implementation of the vsocklib.dll being a non-IFS Winsock. Have you guys ever had to deal with that particular scenario ? Has 4.5.2 this fixed the problem ?

I have 2 Windows 2012R2 VM's running on Vmware ESXi 7 with VMDK's as the SQL disks. I have a SQL 2017 AlwaysOn Cluster running on Server 2012R2. there is no any running backup (SNAPSHOT) *PROD : 10.10.22.1 and 10.10.22.2 HEARTBEAT : 192.168.200.2 and 192.168.200.3 file share witness already defined* CrossSubnetDelay : 1000 CrossSubnetThreshold : 20 PlumbAllCrossSubnetRoutes : 0 SameSubnetDelay : 1000 SameSubnetThreshold : 10 get-cluster |fl *history* RouteHistoryLength : 20 LOG: Cluster has missed two consecutive heartbeats for the local endpoint 10.10.22.1~3343~ connected to remote endpoint 10.10.22.2:~3343 Cluster has missed two consecutive heartbeats for the local endpoint 192.168.200.2:~3343~ connected to remote endpoint 192.168.200.3:~3343~. Clustered role 'sqlcluster' is moving to cluster node 'host02'. FailoverCluster Logs: Cluster node 'host01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges. Cluster node 'host02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges. Cluster resource 'sqlcluster' of type 'SQL Server Availability Group' in clustered role 'sqlcluster' failed. The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges. Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed. Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. System Log: Unable to update the IP address on Isatap interface isatap.{1DF84235-46E7-44DE-BD8F-5A80FD1BD3BD}. Update Type: 0. Error Code: 0x57.

I run Cassandra 4.1.3 inside OpenNMS Horizon 30.0.4; we run the solution on vms virtualized with VMware ESXi on Ubuntu 20.0.4 LTS; we were asked by the customer to migrate the solution from VMware to KVM. I could not find any reference to KVM virtualization; is Cassandra certified on Kvm? If not, is it because it's totally independent on the virtualization env on which it's installed? Thanks in adavnce for you help. Daniele

Is there a best practice on where to install SQL Server binaries for a new windows server deployment. I've seen some people suggest that it's best to seperate this from the OS drive and place it on it's own drive. I've seen others seperate it from the OS and place it on the same drive as the database file, and now while reading through the Architecting Microsoft SQL Server on VMWare vSphere the document says: > The SQL Server binaries should be installed in the OS VMDK. SQL > Server, even if another drive is selected for binary installation, > will still install things on the OS drive so there is no real point > in installing elsewhere I get the need to setup database, transaction logs, tempdb and backups each on their own drive and the reasons for these recommendations, however I'm not 100% sure on the best practice recommendation on where to install the SQL Server binaries and why, especially since i've seen various recommendations from trusted sources. For our application, this will be a virtuallized server on vmware.

The MariaDB user specifies an allowed IP address in the Host column of the mysql.user table. So, it only allows logging in from the host with the specified IP address. And MySQL has the same design. **We have verified in testing:** With VirtualBox hypervisor, a virtual machine runs on the allowed host, and the VM's Setting has a "NAT" network adaptor for global traffics. So, the MariaDB user account also allows logging in from the VM. **Our Questions:** - Why does the allowed host IP address of MariaDB user also allow the VM running on the host? On both the host and the virtual machine, the testing connection client is DBeaver with MariaDB JDBC driver. And we want to better understand the mechanism: - How does the MariaDB server get the source IP address of the in-coming login request? Is it a JDBC driver property, or is it from the TCP/IP protocol? We highly appreciate any hints and suggestions, or any directions on the terminologies to search. \ Notes: I'm setting a "vmware" tag to this question, as "virtualbox" is not available in the choices.

The VMs I run SQL Server on are regularly backed up by the VMware backup tool. I would prefer not to use this backup solution but I have no choice but to cope with it. The problem I've come up across is the fact that every time the VM backup us ran, SQL Server thinks it has performed a full backup of the databases to a virtual device (physical_device_name = GUID). I can see those backups in msdb (they are copy_only backups so I don't have to worry). Do you know why it works this way? Is VMware aware of SQL Server existence? Or maybe SQL Server has wrong data in msdb? Can I run into any problems with that solution (other than trying to restore the DB from the virtual device)?

Is it a requirement for MS SQL Server's Always On Availability Groups to always utilize shared Storage SAN or a virtual shared storage like Storage Spaces Direct? Can I set up Always On Availability Groups using only the local SSDs, HDDs, or even virtual disks of my VMware Virtual Machine without shared storage, while running on a standard Windows Server? I'm planning to use this setup with the MS SQL Server Enterprise Edition. Any insights would be greatly appreciated. -\>Planning a HA/DR MS SQL Server Environment on VMware Virtual Machines Planning a HA/DR MS SQL Server Environment on VMware Virtual Machines

We are having major performance and latency issues with SQL Server 2019. We are running on a "quiet" **VMware** instance connected to a **vSAN**. According to MSFT documentation, best performance is obtained if the drives are formatted at 64k block size vs 4k. Doing some research, VMware publishes that you should NOT use 64k but 4k block size if on a vSAN. So which one is it and what is the science behind this?

I have oracle Database 12c in a virtual machine with the database working normally in a linux environment (Centos). Through windows, using ssh I was able to connect to the linux virtual machine. But when I try to connect the database using 'sqlplus' command, I get the following error. bash: sqlplus: command not found...

I am trying to understand the below behavior for one of our SQL server running on VM. SQL Server version 2017 has 64vCores and Host has 96 cores with base speed 2.1 GHZ Based on the article from https://sqlperformance.com/2017/05/monitoring/troubleshooting-cpu-vmware i collected the counters and can see below"- **Processor\% Processor Time in Task Manager or perfmon**: Toggles around 80 in peak business hours **% Processor Time** for VM ware is always pegging around 100% **Effective VM speed** MhZ averages around 140,305 so does not look to be limited anywhere. ( Minimum 8219 and maximum 157,612) **Host processor speed** is 2091 Is there a way to find what does that 100% coming from? Or is that OK to be 100 % for that counter where SQL seems to be between 75-80%? Additional info:- Avg Batch re/sec on high time = 30K Blocking/deadlocks= none Queries are generally fast like 100K executions/min and avg CPU they spend is few ms. Mostly all the above queries are single threaded due to various reasons. CTOP= 200 and MAXDOP =8 Thanks

Pretty sure I understand this, but wanted to be sure I do. We have a SQL Server 2016, that is running with 2 NumaNodes, each with 8 vCPUs. The Max Degrees of Parallelism (MAXDOP) is set to 8. This doesn't sound right to me. First question: Is that as bad an idea as I think it is? From my research, I need to tell them to reduce the VM Settings to make this run in a single NUMANode. We seem to be having random periods where queries that were running in 170 ms, are now timing out at 30+ seconds! So, we do a quick look, and it is 5% CPU use, and low disk I/O use, and reasonable network use... Basically, the machine is about idle.. We also looked for queries waiting on locks, and there were none. We are running the queries on the Secondary in a AG Group (a Read Only Query) So, my guess: It has gotten enough load that it switched and ran one the view in question (gets run about 4,000 times per day) on one of the vCPUs in the 2nd NUMANode, and then decided that execution plan should be always run on that node. The result is that all the data it is accessing is cached in the other node's memory, and it needs to fetch it across the inter-node link (remote memory), so it does that, but that ends up being a lot slower (170 times?), and the queries are now all stacking up running more and more of them across this remote link... until it will always timeout because the remote memory is saturated... Is that analysis valid? I would hate to submit this as a solution to why the query suddenly jumps up in time if this is totally not correct. And it will be hard to convince them they will get better performance with 8 CPUs than with 16. Oh, additional evidence to back up my claim: If I select * into #tmp from myView OPTION (MAXDOP 16) then I get a performance change of about -5% to -12% - meaning that it takes longer to run the query than if I just used the 8 vCPUs. However, not massively so. So my question is: Is there any validity to my analysis? Update: A couple other things, I got a lot of the information from: https://codenotary-compliance.medium.com/vmware-vsphere-why-checking-numa-configuration-is-so-important-9764c16a7e73 Secondly, If I do a select * from sys.[dm_os_nodes] Then I get foreign_commited_KB as 5,414,260 or 5 GB, from the information above, that would sound like it is committed out of the other node which (is bad?)

We are beginning to provision a set of physical servers for a virtual cluster of SQL Server 2016 nodes within VMware. We will be utilizing Enterprise Edition licenses. We plan on setting up 6 nodes, but there is a bit of a debate on what the ideal way to provision the physical servers with regards to CPU clock speed versus CPU core count. I know this is largely dependent on transaction volume and number of databases stored among other software-specific factors, but is there a general rule of thumb that is advised? For instance, is a dual 8-core, 3.2 GHz physical server (16 cores) more preferential to a dual 16-core, 2.6 GHz server (32 cores)? Has anyone come across a white paper that further delves into this type of topic?

We are using MySQL Circular replication (2 servers in a master-slave setting with each other) for an implementation with both servers is different regions. Previously, we had the entire setup running flawlessly, but the VMWare vendor had to upgrade their underlying infrastructure and had us move the sites over to a new infrastructure. They cloned over our entire app including the servers so we had to do next to no configuration on the actual VMs. However, once traffic was diverted over, one of the servers has gotten into a wierd setting where all flags (Slave_IO_Running: Yes, Slave_SQL_Running: Yes, Seconds_Behind_Master: 0) are showing that all is well, but in reality, the Master_Log_File and Read_Master_Log_Pos variables are not changing at all and seem to be stuck (also causing our NMS not to be able to catch this). Same was verified by creating 2 tables, one on each side. Changes on B are appearing almost immediately on A, but the same is not occurring for changes on A to B. We tried debugging it and when nothing else worked, we just got 2 new VMs, tested out replication again and moved the site over. Within 5 hours, we were at the same scenario again. Below are the outputs of Show Master Status and Show Slave Status of the newer servers. On a side note, there is another simple slave that is also connected to db03 that is fully synced and is following db03 diligently, which proves the issue is not on db03 end. Also, the original setup on the older infrastructure is also still running strong. Output from db-04-db (Database 04) .. *************************** 1. row *************************** File: mysql-bin.000191 Position: 40328871 Binlog_Do_DB: Binlog_Ignore_DB: Executed_Gtid_Set: *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: db-03-db Master_User: reple Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000293 Read_Master_Log_Pos: 154 Relay_Log_File: db04-relay-bin.000001 Relay_Log_Pos: 4 Relay_Master_Log_File: mysql-bin.000293 Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 154 Relay_Log_Space: 154 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: 0 Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 0 Last_IO_Error: Last_SQL_Errno: 0 Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 1 Master_UUID: 5949f340-64f7-11ec-82b5-00505601012c Master_Info_File: /var/lib/mysql/master.info SQL_Delay: 0 SQL_Remaining_Delay: NULL Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates Master_Retry_Count: 86400 Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: Auto_Position: 0 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: Tue Dec 28 13:54:37 UTC 2021 Output from db-03-db (DB 03) .. *************************** 1. row *************************** File: mysql-bin.000295 Position: 41834650 Binlog_Do_DB: Binlog_Ignore_DB: Executed_Gtid_Set: *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: db04 Master_User: reple Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000191 Read_Master_Log_Pos: 40328871 Relay_Log_File: db03-relay-bin.000588 Relay_Log_Pos: 40329084 Relay_Master_Log_File: mysql-bin.000191 Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 40328871 Relay_Log_Space: 40329337 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: 0 Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 0 Last_IO_Error: Last_SQL_Errno: 0 Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 2 Master_UUID: 20aa3d73-64ad-11ec-a86d-0050560200ee Master_Info_File: /var/lib/mysql/master.info SQL_Delay: 0 SQL_Remaining_Delay: NULL Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates Master_Retry_Count: 86400 Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: Auto_Position: 0 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: Tue Dec 28 13:54:34 UTC 2021 So my question simply is how can this actually occur?

I recently migrated a physical SQL Server box (2012) over to ESX (5.1) simply for ease of administration. It is and will be the only guest on the server. As expected there was a marginal performance hit that for the most part is only noticeable on startup. Here in lies my issue. I have noticed that under virtualization the buffer pool takes memory much much much slower then its physical counterpart. Under the physical install within 2 days running SQL server had allocated all 120gb of memory allocated (max server memory). However, with practically the exact same setting running in the hypervisor (I have also given the guest full reservation of the memory) it has taken 7 weeks to reach 50gb. This was also painfully slow something like a Gb rise a day, this translated into a few days of slow queries. So while I have seen this on multi guest boxes and attributed it to memory pressure, I am confused at why it is happening on a single guest box. I know vmware will compress and dedupe memory, however most of this is unique data. So my question is: 1) Why exactly is this happening ? I'm interested in the exact mechanism that is causing this. 2) Is there a method to start SQL server with is full memory allocation ? I remember something like a traceflag for this but havent been able to find anything for 64bit. And is this necessary ? Thanks in advance. ------------------------- Another thing I noticed in the first few days after a restart is that the PLE stays very low in the 500 - 900 range this increases as the buffer pool grows.

My database version is postgresql 9.5. create table if not exists request_log ( id bigserial not null constraint app_requests_pkey primary key, request_date timestamp not null, ip varchar(50), start_time timestamp, application_name varchar(200), request_path text, display_url text, username varchar(50) ); I have a table that icludes incoming http request informations. The id column is primary key and index. The table has no relation. So I have 72320081 rows in this table. And when I run the count query to get count of table, select count(id) from request_log; query takes 3-5 minutes. The explain(analyze, buffers, format text) result for this request is: Aggregate (cost=3447214.71..3447214.72 rows=1 width=0) (actual time=135575.947..135575.947 rows=1 loops=1) Buffers: shared hit=96 read=2551303 -> Seq Scan on request_log (cost=0.00..3268051.57 rows=71665257 width=0) (actual time=2.517..129032.408 rows=72320081 loops=1) Buffers: shared hit=96 read=2551303 Planning time: 0.067 ms Execution time: 135575.988 ms This is very bad performance for me. I could not get reports from table from web applications because of performance. My server hardware sources are: - OS: Linux ubuntu server 16, On Vmware - 4 core cpu - Mem 6Gb - HDD 120 Gb I run the queries at nights, that there are no users on database, but slow. How can solve this problem?

I have 2 Windows 2016 VM's running on Vmware ESXi VMware ESXi, 6.7.0, 17700523 with VMDK's as the SQL disks. I have a SQL 2017 AlwaysOn Cluster running on Server 2016. Basically everything is pointing to an issue with the network configuration but for the time being we're stuck without a solution. Has anyone come across a similar issue which tends to failover the resources randomly? SQL Server **First machine : SQLDB01 , 10.20.20.30 Second machine : SQLDB02 , 10.20.20.31 AG Name : SQLDBAG File share witness host : 10.20.20.40** we use VMXNET3 nic's in the Failover Cluster Management – Cluster Event [FTI][Follower] Ignoring duplicate connection: route to remote node found [CHANNEL 10.20.20.30:~62034~] graceful close, status (of previous failure, may not indicate problem) (0) [NETFTAPI] Signaled NetftRemoteUnreachable event, local address 10.20.20.31:3343 remote address 10.20.20.30:3343 [DCM] Force disconnect failed on DisconnectSmbInstance::CSV, status (c000000d) [PULLER SQLDB01] ReadObject failed with GracefulClose(1226)' because of 'channel to remote endpoint fe80::a1b3:e30a:c6a:a379%9:~54878~ is closed' [QUORUM] Node 2: One off quorum (2) [DCM] UpdateClusDiskMembership: ctl 300224 nodeSet (2), status 87 [RCM] Moving orphaned group Cluster Group from downed node SQLDB01 to node SQLDB02. [RES] SQL Server Availability Group : [hadrag] Lease Thread terminated Operational Log: Microsoft Failover Cluster Virtual Adapter (NetFT) has missed more than 40 percent of consecutive heartbeats. -------------------------------------------------------------------------- UPDATED-10/30/2021 1) does the backup network support heartbeat too ? No Also , there is no relationship between backup NIC and failover clustering configuration. Already checked "Do not allow cluster network communication on this network " for BACKUP NIC. 2)How many (virtual) NICs? We have 2 NICs (LAN and BACKUP) 3)Are the VMs on same host? No, different ESX host No any intensive security scans and vMotions. Only I am backing up boot disk.(C Volume image backup) -------------------------------------------------------------------------- timeframes that these events occur: 10/27/2021, 1:00:44 AM Task: Create virtual machine snapshot 10/27/2021, 1:14:21 AM Backup successful 10/27/2021, 1:14:21 AM Task: Remove snapshot 10/27/2021, 1:15:38 AM Virtual machine SQLDB01 disks consolidated successfully -- 10/28/2021 1:14:22 AM --->> Microsoft Failover Cluster Virtual Adapter (NetFT) has missed more than 40 percent of consecutive heartbeats. 10/28/2021 1:14:28 AM ---->> Cluster has lost the UDP connection from local endpoint 10.20.20.30:~3343~ connected to remote endpoint 10.20.20.31:~3343~. 10/28/2021 1:15:35 AM [CHANNEL 10.20.20.31:~3343~]/recv: Failed to retrieve the results of overlapped I/O: 10054 -------------------------------------------------------------------- SQLDB02 events : I am assuming , there is conflict between Veeam replication job and netbackup daily incremental backup job. then I am getting disk consolidation message. but it doesn't happen all the time. 10/28/2021, 1:00:32 AMTask: Create virtual machine snapshot (NETBACKUP) 10/28/2021, 1:00:49 AM User logged event: Source: Veeam Backup Action: Job "SQLDB02_Replication" Operation: Started Status 10/28/2021, 1:00:58 AMTask: Create virtual machine snapshot (VEEAM) 10/28/2021, 1:14:17 AM NetBackup: Backup successful for SQLDB02 10/28/2021, 1:14:18 AMTask: Remove snapshot WARNING : 10/28/2021, 1:15:35 AM Virtual machine SQLDB02 disks consolidation is needed on ESX_IP (NETBACKUP) 10/28/2021, 1:15:35 AM Virtual machine SQLDB02 disks consolidation failed on ESX_IP (NETBACKUP 10/28/2021, 1:16:53 AM NetBackup: Consolidate disk failed for SQLDB02.

What are the impacts / steps from DB2 DB side before VMware SvMotion Storage migration ?

We have migrated a SQL 2000 server to VM and I am wondering what changes will need to be made on the VM? After the VM migration an SSIS package that transferred data from the 2000Server to a 2008Server will not connect. Nothing changed on the 2008Server but none the less the SSIS connection fails to authenticate. I can log in remotely from the 2008Server to the 2000Server using the credentials in the SSIS package. So, is there anything that needs to be configured on the VM side that should be configured? I have checked services, account privileges, etc. The two servers can communicate, ports are open, osql -L and sqlcmd -L see the servers. Nothing on the VM server has changed from the physical server configuration wise.

First I am not a SQL DB. I inherited an old system and am trying to keep the wheels from falling off. We have an MS SQL 2000 server (running server Win Server 2000) that we performed a P2V migration on. I did not realize that there are temp files running on an external USB HDD (that was connected to the old physical server) necessary for SQL operations. Its looking like we can not connect the USB HDDs to the VM (due to age of the OS, and the HDD being a 3.0, doesnt look like VMWare supports 3.0 passthrough to Win Server2000). So, is it possible to set those external HDDs up as a shared drive on another machine and run those temp SQL operations from the VM? As it is now the DB looks for a physical drive volume. We are considering swapping out the HDDs to USB 2.0, but this seems more time efficient. Thanks for any input