3 ms·
SQL Server gives you both. They have a UI for everything, and everything you do has an option to script. So you might go through the whole wizards for replicati
by MichaelGG 13y ago
SQL Server gives you both. They have a UI for everything, and everything you do has an option to script. So you might go through the whole wizards for replication, then when done, save off a T-SQL script. To my knowledge, there's nothing that requires the UI; it's there just to make things easier. Then on top of that, they expose an API you can use for further automation, if T-SQL isn't to your liking.
Your example is particularly odd:
RESTORE DATABASE bla FROM DISK = 'file.bak'
The docs are quite comprehensive, with lots of useful examples[1].
MS deserves some flak for UI-only, but SQL Server isn't one of those products (at least since 2005). MS products in general are also becoming much more scriptable, as Powershell access is becoming a requirement for new products.
I prefer a clicky interface for things I'm not going to do often (like configure a new cluster) or things I don't want to commit to memory or have to look up. Anytime I need to repeat, I either read docs and construct a command, or if it's a complicated thing, I'll use the wizard to generate a base script and modify as needed.
1: http://msdn.microsoft.com/en-us/library/ms186858.aspx http://msdn.microsoft.com/en-us/library/ms186858.aspx
- kryten 13y agoIt's not all roses. Have you ever tried scripting and versioning SSIS for example? Probably not. Which is why we use Spring Integration...