CodePudding user response:
Process is not important, the important thing is the result,, of course, in practice, and give priority to in order to convenient, general will add and delete SQL to write, but ordinary authority distribution, create a table of what, I still used to graphical interface,
CodePudding user response:
What do you eat take a bowl and chopsticks to eat, or take the plates and spoons to eat?This problem is how to achieve a purpose, the process is not important, it's important to quickly achieve results,
CodePudding user response:
Look at the situation of ah, see which convenient use, efficient best ~CodePudding user response:
Shall I open the data such as to change a value, directly in the input line above, write what SQL statements, but the batch change, is bound to the SQL statement. Otherwise, give you dead tired
CodePudding user response:
If is often need to perform operation, suggest using SQL, efficiency is higher.CodePudding user response:
See the need toTo need release, best or write scripts, because making a beta version, on the production server DB still have to get one, only scripts executed repeatedly the most convenient,
For the maintenance of the class, not used operations, such as: occasionally a database backup, the graphical interface,
Of course, if you are skilled, suggest all try to use the script,
CodePudding user response:
It is best to use all scriptSuch as view, usually with the UI, of course, no problem, but if you view the table-valued functions, then, you can only use the script writing your own SQL
The stored procedure, trigger, a custom function, you also can't be lazy, scripts
Database migration, some CLR can't packaging, their migration after generation script luo
In addition, in the practical work, the different statistics, different data detail, or write a SQL more accurate and more convenient