Nurah.lee

  Video references :  https://www.youtube.com/playlist?list=PLrzAZN530GJ_v59XeehutxytP0qh6NvR_

 List of command for ADB >adb devices -l List of devices attached >adb connect 192.168.1.102:39445 connected to 192.168.1.102:39445 >adb connect 192.168.1.101:5555 connected to 192.168.1.101:5555 >adb devices -l List of devices attached 192.168.1.101:5555     device product:rk3566_r model:rk3566_r device:rk3566_r transport_id:6 192.168.1.102:39445    device product:V2427T model:V2427 device:V2427 transport_id:5 >scrcpy --tcpip=192.168.1.110:5555 >scrcpy --tcpip=192.168.1.101:5555

  1. Lets connect adb through wifi 1. Prerequisites The panel and your PC must be on the same Wi-Fi network (or same subnet). Developer Options and Wireless debugging must be enabled on the panel. You’ll need the Android platform-tools (ADB) installed on your PC. 2. Enable Developer & Wireless Debugging on the Panel On the panel: Go to Settings → About → Build number → tap 7× until you see “You are now a developer.” Open Settings → Developer options . Toggle Wireless debugging → ON. On some builds it’s called ADB over Wi-Fi . (If there’s a prompt to allow pairing with a device, keep that screen open.) 3. Pair Your PC (Android 11+ Secure Pairing) Since Android 11, you must pair your PC the first time. On the panel: In Wireless debugging , choose Pair device with pairing code . You’ll see: IP address and port (e.g., 192.168.1.110:37099 ) Pairing code (e.g., 123456 ) On your PC: adb pair 192.168.1.110:37099 Enter the p...

 This MariaDB log shows that the server failed to start due to a corrupted InnoDB data file , specifically involving a missing MLOG_CHECKPOINT . Let’s walk through what’s happening and how you can attempt recovery step-by-step. 🔍 What’s Happening? Key Log Line: [ERROR] InnoDB: Missing MLOG_CHECKPOINT at 50981968 between the checkpoint 50981968 and the end 50981959. This means the InnoDB redo log is corrupted — it’s expecting a checkpoint that either doesn’t exist or is unreadable, which prevents InnoDB from initializing. 🛠️ Fix Step-by-Step ✅ 1. Backup First! Before trying anything else: Backup the entire MariaDB data directory (default on Windows is usually in C:\Program Files\MariaDB xx\data ). Also backup ib_logfile0 , ib_logfile1 , and ibdata1 . 🛑 2. Try Forcing InnoDB Recovery Edit your my.ini (or my.cnf ) file and add the following under the [mysqld] section : [mysqld] innodb_force_recovery = 1 Try restarting the MariaDB service. If it still fails,...

 ⚠️ Understanding SQL Server Memory Management SQL Server Memory Usage: SQL Server does not immediately release memory even if tables are truncated or data is deleted. Memory Retention Mechanism: By design, SQL Server retains memory (buffer pool, plan cache) for performance reasons. Memory Clearing is Manual: Reducing SQL Server's memory usage must be done explicitly. Solution: Clear SQL Server Memory Manually To manually clear SQL Server memory and force it to release unused memory: 1. Clear the Buffer Cache DBCC DROPCLEANBUFFERS; 2. Clear the Plan Cache DBCC FREEPROCCACHE; 3. Clear Cache for Specific Database (Recommended) USE [syncdb]; DBCC FREEPROCCACHE WITH NO_INFOMSGS; DBCC DROPCLEANBUFFERS WITH NO_INFOMSGS; Solution: Adjust Maximum Server Memory (Temporary Fix) If SQL Server continues to consume too much memory, limit the maximum memory usage: EXEC sp_configure 'show advanced options' , 1 ; RECONFIGURE; EXEC sp_configure 'max server memory...

  To check the size of your database in SQL Server , you can use the following query: Chatgpt - Refer this  https://chatgpt.com/share/681c2bc9-c948-8001-8530-d2563ec53c59 1. Check Database Size (Data + Log) USE YourDatabaseName; GO EXEC sp_spaceused; 2. Detailed Database Size (Data and Log Separately) SELECT      name AS FileName,     size * 8 / 1024 AS SizeMB,      max_size * 8 / 1024 AS MaxSizeMB,     physical_name AS FilePath,     type_desc AS FileType FROM sys.master_files WHERE database_id = DB_ID('YourDatabaseName'); 3. Size of All Databases on the Server SELECT      DB_NAME(database_id) AS DatabaseName,     SUM(size * 8 / 1024) AS SizeMB FROM sys.master_files GROUP BY database_id; Analysis and Recommendations: High Index Size: Your index size is almost as large as your data size (4.09 GB for indexes vs 4.83 GB for data). This suggests you may have many indexes , including unused ...