Dynamic Memory or Statics Memory in Hyper-V environment

With Dynamic Memory, Hyper-V can provide a virtual machine with more or less memory dynamically in response to changes in the amount of memory required by the workloads or applications running in the virtual machine. Dynamic Memory helps you use memory resources more efficiently,

However, some heavy load database application like SQL server may not work well with dynamic memory and it may makes it possible to a Hyper-V server’s physical memory. In this case, you may assign statics memory to VM.

Advantages and Disadvantages of Hyper-V Dynamic Memory

Hyper-V Dynamic Memory is a useful feature which offers a lot of advantages, such as:
Reduced memory consumption, as the VM uses only the amount of memory that it actually needs within the limits set by an administrator
Efficient memory distribution, as you can dynamically assign more or less memory to the running VM
Higher consolidation numbers due to the more efficient use of memory resources
Enhanced reliability for restart operations with the help of Hyper-V Smart Paging
Cost-efficiency as VM resources are not wasted

However, Hyper-V Dynamic Memory also has a number of disadvantages, which can negatively affect VM memory performance. They include the following:
Risk of overprovisioning computer physical memory in case you don’t keep track of memory allocation within your virtual environment
Some memory settings cannot be changed when the VM is running. Thus, you cannot decrease or increase the maximum and the minimum memory amount, as well as modify the VM startup memory amount, when the VM is still running or paused.
When Hyper-V Dynamic Memory is enabled, issues with database applications may occur. It is recommended that you use applications that are compatible with Hyper-V Dynamic Memory to avoid any performance issues.

Example of converting Windows FTP script to WinSCP FTP script

Situation: the client has been using Windows FTP command script to upload files. However, the new Syncplify.me FTP is more secure and requires use FTP passive more. Since Windows command line doesn’t support Passive mode, they need to convert windows FTP script to WinSCP FTP script. Here is an example.

  1. Install WinSCP on the client’s computer.

2. Run this command: “C:\Program Files (x86)\WinSCP\winscp.com” open ftp://username:password@IP or FQND:21 -passive=on

for example

“C:\Program Files (x86)\WinSCP\winscp.com” open ftp://blin:Pa$$1357@ftp.chicagotech.net:21 -passive=on

3. Use ls to Lists the contents of remote directory

4. Use put to Uploads file from local directory to remote directory

For example

put *.doc *.jpg /ftp/*

5. Use get to downloads file from remote directory to local directory

6. close Closes session

7. exit Closes all sessions and terminates the program