I would NOT recommend use SHRINKDB "just for fun". Of course is clears all unused disk space but it also can have it's negative impact, from maximum fragmented indexes to performance, as for some operations the file has to grow again.
Also setting recovery model to simple should be diskussed. It depends on how many data you lose if your system crashes. The full recovery model is no problem if you backup and thus empty the log file regularly.
It is, however, a UAT box. Unless you're doing Point-in-time backups on your UAT box, there's no need to use any recovery mode other than SIMPLE. Also, a UAT box probably won't suffer the same amount of activity so it's not likely the log fie needs to be as large as the production box.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs