Tree of Life

Decided to write about a few practices I try to follow to be more efficient in the "IT realm" Use RDP Manager or Netop or whatever your remoting solution is to build a "directory" for your servers and back it up. Establish a hierarchy like this \ \ \ (Eg: NA\PROD\ECOM\firmweb1) Use a good folder structure to keep your project files, start a folder for each project. Use sub-folders for details on a particular part of project when too many files accumulate. Keep this folder close to root (C:\) back it up often Use SyncToy or any cloud solution to automate your backup. You will always skip manual backup. Use a batch (if you need control) file and schedule it periodically and make it email you If you produce Excel reports from SQL dumps, create a tab called query and paste your long complex SQL query into it. Learn Windows , Excel , Gmail shortcuts!!  Maintain an "Installer" folder and break it down to OS, Development Tools, Databases, Application Se...

Never again write any login password logic. Generate all necessary components in your database using the following: cd c:\Windows\Microsoft.NET\Framework\v4.0.30319 c:\Windows\Microsoft.NET\Framework\v4.0.30319>aspnet_regsql.exe -A all -C "your_sql_connection_string" Start adding the following features: Membership Profile RoleManager Personalization SqlWebEventProvider script takes care of all and you have a login engine .. take it to next level integrating it with Facebook, Twitter etc..

He "is a God among insects" :) http://sqlblog.com/blogs/aaron_bertrand/archive/2010/10/25/fun-with-software-uninstalling-sql-server-2008-r2-evaluation-edition.aspx

The wonderful site, http://cloudharmony.com/speedtest/run allows you to run tests on latency, small and large file download speed. Depending on the nature of your application, the choice of a provider is crucial (of course price is another important factor). In the tests, Large File Download category, Amazon S3 is the winner with an average of 15.33 Mb/s. This might be suitable for applications working with large files (pdfs, catalogs, repositories). Windows Azure Service is the winner of the small file category with around 2.5 Mb/s. The difference between the large and small file is significant. This order of magnitude difference is probably due to the overhead of authentication, establishing a connection etc. Once the pipe is secure and ready, you are probably bound to the limitations of your IPO as well as the cloud service provider's SLA. Latency might be a concern for high throughput applications - I would argue that self-hosting or keeping the applications close...