I recently changed from one department to another within my company and found some weird policies for DDL changes from which I would like your opinion. It happens for Oracle, but I'm sure the same could be applied to SQL Server.To create a table, I have to fill an excel file defining the schema, name, initial rows, growth among other things. This file must be emailed to the dbas to ask for a tablespace (filegroup).After receiving the tablespace, I have to generate the CREATE TABLE script that includes GRANTs to different users. This will have to be emailed for validation to the dba group including the previous response (if it's not included, they will ask for it even if it's the same dba who sent it). Once receiving the response, I need to create a ticket to run the validated script.In addition to that, a teammate must create another ticket on a different sytem.Finally, after obtaining all authorizations, the same dbas will run the script to create the tables.This seems over complicated and I'm sure that a single ticket that includes table definition, initial size and expected growth should be enough and DBAs must define the script by themselves. I'd like to know what do you think about this and how do you do it in your workplaces.
↧