Businesses are now facing an ever-growing amount of data which is pushing the boundaries of what can be done with spreadsheets and macros. Transactions are expected to happen at a faster pace, involving multiple users from different departments in varying locations. More information is being tracked and reports should be dynamically generated based on what’s happening – right now. Today’s smart businesses strive for instant and accurate results.
The RESTful API has a funny place in the software development world: it’s widely regarded as the best general-purpose pattern for building web application APIs, and yet it’s also nebulous enough of a concept to cause endless disagreements within teams over exactly how to implement one.
Don’t ask me why you find yourself working in ASP.NET. I know there are more effective ways to build a site.
Don’t ask me what reason could possibly explain needing to change some passwords. Why isn’t this functionality built in to the app? I know, I know…
But you’re there. Your app is using the MembershipProvider system, which saves the passwords in the database in some kind of encrypted form. And now you have to change some passwords quickly, probably for multiple embarrassing reasons, yet the app doesn’t offer you the functionality to do so, and you don’t have the time to add that functionality and re-build and re-deploy the app.
If only it were possible to go into SSMS and change the passwords using only T-SQL.
Now you can.