Vadivel's blog

When using SQL Server Management Studio, I feel it's a pain and waste of time to choose the same SQL server instance, authentication details repeatedly. As a workaround, I use to make use of the "ssms" command. If SQL Authentication:  ssms -s MySQLServer2017ENT -d testbed -u demo -p demo here, -s:  Server details -d:  Database to connect -u:  username -p:  password For Windows Authentication: ssms -s MySQLServer2017ENT -d testbed But opening the command prompt and typing this each time doesn't make sense either. So created a batch file and placed it on the desktop that way, double-clicking the batch file is all one has to do. Mainly while working on my laptop, this comes in very handy. Content of the batch file: start ssms -s MySQLServer2017ENT -d testbed -u demo -p demo exit

Have listed down few Lessons learned on the field which I found useful over a period of time. 1: Always execute every line of your code After developing a feature one needs to obviously test it. Make sure every line of your code has been executed at least once. Many times see bugs on a certain line of code which had never been run by the developer. Kind of a condition within your code where the control never reaches during the normal flow. The code might look decent enough while reviewing, but unless you had made sure control comes to that part of your code and test it nothing is guaranteed to work. Sounds obvious, doesn't it? Think how many times you would have faced this scenario by having used some test data which never takes you to an "else" part of the code (or) "case" of a switch statement etc., 2: Logging, Error Handling to be part of the code from the very beginning. While developing a new feature/module/project add logging and error handlin