数据库命名约定 [英] Database Naming Conventions

问题描述

您好管理员

遵循Sharepoint中数据库的命名约定的最佳实践是什么?

Whats the best practice for following naming conventions for database in sharepoint ?

我们正在计划版本环境类型数据库名称

We are planning on  Version_Environment_Type_DatabaseName

例如

     开发-SP2013_Dev_Config，SP2013_Dev_Content_Admin 

      Development - SP2013_Dev_Config , SP2013_Dev_Content_Admin  

     质量检查-              SP2013_QA_Config，SP2013_QA_Content_Admin

      QA -               SP2013_QA_Config, SP2013_QA_Content_Admin

     产品-            SP2013_Config，SP2013_Content_Admin

      Prod  -            SP2013_Config, SP2013_Content_Admin

但是有人问过要从名称中删除环境

However there has been ask about dropping environment from name 

这将使多个环境中的所有数据库看起来像prod一样.作为管理员，我们在不同的环境中工作，拥有环境会增加安全性.对Prod进行质量检查数据刷新时不要搞乱也很重要 进行测试.

Which will make all database in multiple environment look like same as prod . Being a admin we have work on different environments and having environment adds extra layer of security . Also can be important to not to mess up during Prod to QA data refresh for testing.

有什么想法吗?还是更好的方法?

Any thoughts ? or better approach ?

谢谢

-维玛安

推荐答案

即使您有指定环境的专用实例，我也不建议从名称中删除环境.如果您拥有专用实例，则仍然可以通过同名的Prod DB还原QA数据库，而无法实现 错误，直到为时已晚.我一直使用与您建议的内容类似的内容.我所遇到的唯一真正的最佳实践是保持您的命名约定一致.

I would not recommend dropping the environment from the name even if you have dedicated instances that designate the environment.  If you have dedicated instances you could still restore a QA db over a Prod DB of the same name and not realize your error until it was too late.  I've always used something similar to what you have suggested.  The only real best practice I've ever encountered is to be consistent in your naming convention.

这篇关于数据库命名约定的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！