Thanks for your reply.
So now since the max server memory setting has been set to 512G which is more than the physical memory what kind of waits /error sql server may try to show in case of a problem?
SQL Server consumes memory from other processes or the OS, and keeps using more and more memory until there is no more memory left on the system. If the OS has no memory available, it will start using the page file instead of RAM. Using the paging file instead of memory can result in poor system performance - operations that should be fast and in-memory are constantly reading and writing to disk.
by default max server memory is set at 2147483647 MB, so thats the same scenario as i have here. meaning if someone keeps the default setting for the server are they bound to run into issues? OR does sql server controls memory usage irrespective of max server memory settings
By default, SQL Server can change its memory requirements dynamically based on available system resources. When SQL Server is using memory dynamically, it queries the system periodically to determine the amount of free memory. Maintaining this free memory prevents the OS from paging. If less memory is free, SQL Server releases memory to the OS. If more memory is free, SQL Server may allocate more memory. SQL Server adds memory only when its workload requires more memory. Please check this doc for more details.