blocks|key|2528276|text|我一直在使用扩展属性，因为它们非常灵活。大多数标准文档工具都可以从MS_Description中删除，然后您可以在定制工具中使用自己的工具。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2528277|参见此演示文稿：#41-获得一个杠杆，挑出任何海龟:用元数据提升|2528278|这个代码是：http://code.google.com/p/caderoux/wiki/LeversAndTurtles|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20180822072352/http://www.sqllunch.com/Lunches.aspx?Month=November%25202010#|1|http://code.google.com/p/caderoux/wiki/LeversAndTurtles^0|X|E|0|8|O|0|0|6|1J|1^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]]|J|$K|$5|L|M|N|E|$O|P]]|Q|$5|L|M|N|E|$O|R]]]]

I have been using extended properties since they are very flexible. Most standard documentation tools can be driven off <code>MS_Description</code>, and then you can use your own with custom-built tools.
See this presentation: <a href="https://web.archive.org/web/20180822072352/http://www.sqllunch.com/Lunches.aspx?Month=November%202010#" rel="nofollow noreferrer">#41-Get a Lever and Pick Any Turtle: Lifting with Metadata</a>
And this code: <a href="http://code.google.com/p/caderoux/wiki/LeversAndTurtles" rel="nofollow noreferrer">http://code.google.com/p/caderoux/wiki/LeversAndTurtles</a>

blocks|key|2528418|text|微软的Visio+Pro+(直到Visio2010)可以反向工程一个数据库，CA的ERwin也可以。Visio是更便宜的选项，但ERwin是更详细、更完整的选项。如果人们费心看的话，扩展的属性是很好的。您还可以使用类似Red格式的SQL+Doc输出文档。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2528419|我发现命名约定和正确设置外键会导致一个几乎自文档化的数据库。为了更好地理解目的，你仍然应该有一些外部文档。|entityMap|0|LINK|mutability|MUTABLE|url|http://office.microsoft.com/en-us/visio/visio-edition-comparison-FX101838162.aspx|1|http://www.ca.com/us/data-modeling.aspx|2|http://www.red-gate.com/products/sql-development/sql-doc/^0|3|9|0|15|5|1|37|7|2|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]|$A|U|B|V|1|W]|$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]|M|$5|H|I|J|C|$K|N]]|O|$5|H|I|J|C|$K|P]]]]

Microsoft's <a href="http://office.microsoft.com/en-us/visio/visio-edition-comparison-FX101838162.aspx" rel="noreferrer">Visio Pro</a> (up to Visio 2010) can reverse engineer a database as can CA's <a href="http://www.ca.com/us/data-modeling.aspx" rel="noreferrer">ERwin</a>. Visio is the cheaper option, but ERwin is the more detailed, more complete option. Extended properties are nice, if people bother to look at them. You could also use something like Red Gate's <a href="http://www.red-gate.com/products/sql-development/sql-doc/" rel="noreferrer">SQL Doc</a> to output documentation in HTML format.

I find naming conventions and properly setting up foreign keys lead to an almost self-documenting database. You still should have some external docs for better understanding of purpose.

blocks|key|1385090|text|试试SchemaSpy：http://schemaspy.sourceforge.net/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://schemaspy.sourceforge.net/^0|C|X|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

Try SchemaSpy: <a href="http://schemaspy.sourceforge.net/">http://schemaspy.sourceforge.net/</a>

blocks|key|2528542|text|看看SchemaCrawler+--这是我设计的免费命令行工具，用来做你想要的事情。SchemaCrawler生成一个包含所有数据库架构对象的文本文件。此文本输出设计为既具有可读性，又可与来自另一台服务器的类似输出进行区分。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2528543|在实践中，我发现输出数据库模式的文本文件是有用的，这是构建的一部分。通过这种方式，您可以将文本文件签入源代码控制系统，并具有模式随时间发展的版本历史记录。SchemaCrawler的设计也是为了在命令行中实现自动化。|entityMap|0|LINK|mutability|MUTABLE|url|https://www.schemacrawler.com/^0|2|D|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]]|C|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]]]

Take a look at <a href="https://www.schemacrawler.com/" rel="nofollow noreferrer">SchemaCrawler</a> - it is my free, command-line tool that I designed to do what you are looking for. SchemaCrawler produces a text file with all of database schema objects. This text output is designed to be both human-readable, as well as diff-able against similar output from another server.

In practice, what I have found is that outputting a text file of the database schema is useful, when done as part of the build. This way, you can check the text file into your source code control system, and have a version history of how your schema has evolved over time. SchemaCrawler is designed to automate this too, from the command-line.

blocks|key|2528336|text|如果它曾经写过，文档由一个word文档组成。将包括几个关系图。表的列表以及每个表所包含的内容及其与其他表的关系的简要说明。文档的一个章节包括安全设置:应用程序需要什么权限？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2528337|通常，在我工作过的公司中，数据库文档只有在客户是执行审计的时候才会编写，这就倾向于将数据库文档的使用局限于金融和政府客户。|2528338|免责声明:太多的开发人员认为代码就是文档，我也对此感到内疚。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

If it is ever written, the documentation consists of a word document. A couple of relationship diagrams will be included. Lists of the tables and a brief description of what each table holds and how it relates to other tables. One chapter of the documentation includes the security settings: what permissions does the "user" that the application need? 

Generally, in companies I've worked for, database documentation only gets written when the customer is the one who performs audits, which tends to limit its use to financial and government customers. 

Disclaimer: far too many developers take the attitude that the code is the documentation, and I've been guilty of it too.

blocks|key|1385173|text|我使用扩展属性和。效果很好！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I use extended properties and Red Gates SQL Doc. Works very well!

blocks|key|2528595|text|有趣的是，我想知道其他人是怎么做到的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2528596|在开发我的第一个大型数据库项目时，我发现10.0.1600.22支持数据库关系图，您可以将这些关系图导出到word文档或其他文档软件中，在这些软件中，您可以添加任意多的文档细节。只需在上展开连接到的数据库，右键单击对象资源管理器中的“数据库关系图”，然后选择“新建数据库关系图”生成一个交互关系图，它将显示不同表之间的所有关系。您甚至可以指定要在图表中包含哪些表，这样，如果您只是试图逐个记录图像，就不会异常地得到图像。导出图片到任何其他编辑软件和评论，你想要的。|2528597|我还在生成数据库的脚本中推荐了大量/注释/。|2528598|一般来说，写下这一切的目的是很多工作，但从长远来看是个好主意，比如几年后，当你或其他可怜的灵魂回来更新你的创作时！:)|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Funny, I was wondering how other people are doing this as well.. 

While developing my first big database project, I found that Microsoft SQL Server Management Studio 10.0.1600.22 supports database diagrams which you can export to a word document or other documentation software where you can add as much documentation detail as you want. Just expand the database you connected to on SQL Management Studio and right click on "database diagrams" in the object explorer and select "New Database Diagram" to generate an interactive diagram which will show all the relationships between the different tables. You can even specify which tables you want to include in the diagrams, so that the image does not get unweildly if you are just trying to document it piece by piece. Export the image to any other editing software and comment as much as you want.

I also recommend plenty of /comments/ in the script which generates your database. 

Generally it is a lot of work writing down what it is all for, but a good idea for the long term, such as when you or some other poor soul comes back to update your creation a couple of years later! :)

blocks|key|1385431|text|我为所有对象设置了MS_description扩展属性，然后使用ApexSQL医生记录整个数据库。我以前经常创建HTML文档，但最近我更喜欢PDF格式|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://www.apexsql.com/sql_tools_doc.aspx^0|W|9|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

I set the MS_description extended property for all objects and then document the whole database using <a href="http://www.apexsql.com/sql_tools_doc.aspx">ApexSQL Doc</a>.
I used to create HTML documents earlier, but lately I prefer PDF

blocks|key|2528760|text|我使用数据建模工具，因为它们允许我记录关于数据库的重要信息，而不是“适合”在数据库中的信息。元数据，如隐私/安全/敏感性问题、管理、治理等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2528761|这可能超出了某些人在记录数据库时所需的范围，但这些对于业务和帮助他们管理数据非常重要。|2528762|正式工具还帮助我管理存储在多个数据库/实例/服务器中的数据。在我们打包的应用程序世界中，这一点从来没有像现在这样真实。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

I use data modeling tools because they allow me to document important information about the database other than what "fits" in a database. Meta data like privacy/security/sensitivity concerns, stewardship, governance, etc.

That may go beyond what some need in documenting a database, but those things are important to the business and helping them manage their data.

Formal tools also help me in managing data that is stored in more than one database/instance/server. This has never been more true than in our packaged application world.

blocks|key|1385294|text|DB字典创建者|type|header-two|depth|inlineStyleRanges|entityRanges|offset|length|data|1385295|是一个开源数据库文档工具，具有良好的GUI和导出/导入选项。它使用扩展的属性来存储文档。它还将为主键列和外键列生成自动描述。|unstyled|entityMap|0|LINK|mutability|MUTABLE|url|http://datadictionary.codeplex.com/^0|0|7|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|F|7|R|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

<h2><a href="http://datadictionary.codeplex.com/" rel="noreferrer">DB Dictionary Creator</a></h2>
is an open source database documentation tool with decent GUI and export / import options. It uses Extended properties to store the documentation. It'll also generates automatic descriptions for primary key columns and foreign key columns.

blocks|key|2528902|text|对于文档化SQL+Server，我强烈推荐最近刚刚发布的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2528903|使用Windows+PowerShell的Server和Windows文档作者:+Kendal|offset|length|2528904|链接中的简要说明：|2528905|SQL是一组Windows脚本和模块，用于发现、记录和诊断Server实例及其底层Windows和机器配置。SQL+Power+Doc与Server+2000到2012的所有版本以及Windows+2000和Windows+XP的Windows+Server和使用者Windows操作系统的所有版本通过Windows+Server+2012和Windows+8一起工作。SQL+Power+Doc还能够记录Windows+Azure+SQL数据库。|2528906|替代链接：kendalvandyke/sqlpowerdoc+github储存库，因为codeplex即将消失。|entityMap|0|LINK|mutability|MUTABLE|url|https://sqlpowerdoc.codeplex.com/|1|https://github.com/kendalvandyke/sqlpowerdoc^0|0|0|11|0|0|0|0|5|Z|1^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]|S|$5|N|O|P|A|$Q|T]]]]

For documenting SQL Server, I highly recommend just recently released :
<a href="https://sqlpowerdoc.codeplex.com/" rel="nofollow noreferrer">SQL Server &amp; Windows Documentation Using Windows PowerShell</a> written by Kendal Van Dyke
Brief description from the link :
SQL Power Doc is a collection of Windows PowerShell scripts and modules that discover, document, and diagnose SQL Server instances and their underlying Windows OS &amp; machine configurations. SQL Power Doc works with all versions of SQL Server from SQL Server 2000 through 2012, and all versions of Windows Server and consumer Windows Operating Systems from Windows 2000 and Windows XP through Windows Server 2012 and Windows 8. SQL Power Doc is also capable of documenting Windows Azure SQL Databases.
Alternative link: <a href="https://github.com/kendalvandyke/sqlpowerdoc" rel="nofollow noreferrer">kendalvandyke/sqlpowerdoc github repository</a>, as codeplex is going away.

blocks|key|2528944|text|我们使用Dataedo创建数据字典、文档存储过程和函数。我们粘贴在Visio中创建的ERD。所有文档都存储在Dataedo元数据存储库(格式化文本)中，我们将其导出到HTML以供内部使用，或者导出到PDF以供打印文档。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2528945|我们将每个对象分配给一个模块，并将每个模块分配给一个人。Dataedo附带了文档状态报告，因此我们可以判断是否有一个新的列或表需要文档化。|entityMap|0|LINK|mutability|MUTABLE|url|http://dataedo.com/^0|4|7|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]]|C|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]]]

We use <a href="http://dataedo.com" rel="noreferrer">Dataedo</a> to create data dictionary, document stored procedures and functions. We paste ERDs created in Visio. All documentation is stored in Dataedo metadata repository (formatted text) and we export it to HTML for internal use or export to PDF for printed document.

We assign each object to a module and assign each module to a person. Dataedo comes with documentation status reporting so we can tell if there’s a new column or table that needs to be documented.

blocks|key|1385851|text|在尝试了多年来这里的许多免费和付费解决方案之后，我用纯that创建了自己的开源解决方案，该解决方案输出了(+sp_doc+)中的文档，作为一个更大的免费脚本套件DBA+MultiTool的一部分。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1385852|通过to实现它降低了依赖第三方应用程序、PowerShell模块/库等的复杂性，并利用扩展属性的内置功能使数据库自描述。它可以很容易地连接到自动部署工作流中，从而生成数据库的最新视图。|1385853|数据库可能是复杂的，灾难性的事情。并不是每个数据库管理员、开发人员或分析师都有时间了解数据库的来龙去脉，以便完成他们的工作。更糟糕的是，很少有产品和更少的免费选项可以帮助以人类可读的格式显示数据库。sp_doc的S目标是在Github+Markdown+(GFM)中动态生成数据库文档，这意味着您现在有了一个免费的、可扩展的自文档数据库！|blockquote|1385854|更新:现在也可以通过dbatools的安装-DbaMultiTool命令安装它。|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/LowlyDBA/ExpressSQL/blob/master/docs/sp_doc.md|1|https://dba-multitool.org/|2|https://github.com/sqlcollaborative/dbatools/blob/development/functions/Install-DbaMultiTool.ps1^0|1I|6|1I|6|0|28|D|1|0|0|2R|6|0|J|F|2^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]|$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|K|3|L|5|6|7|1A|8|@]|D|@$9|1B|A|1C|1|1D]]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|U]]|V|$5|O|P|Q|E|$R|W]]]]

After having tried many of the free &amp; paid solutions here over the years, I've created my own open source solution in pure T-SQL that outputs documentation in Github Flavor Markdown, <a href="https://github.com/LowlyDBA/ExpressSQL/blob/master/docs/sp_doc.md" rel="nofollow noreferrer"><code>sp_doc</code></a> as part of a larger suite of free scripts called <a href="https://dba-multitool.org" rel="nofollow noreferrer">DBA MultiTool</a>.
Doing it via T-SQL reduces the complexity of relying on a third party application, PowerShell module/library, etc. and leverages the built-in power of Extended Properties to make the database self describing. It can be easily hooked into automated deployment workflows to produce an always up-to-date view of the database.
<blockquote>
Databases can be complex, disastrous things. Not every database admin, developer, or analyst has the time to learn the ins and outs of a database in order to just do their work. To make things worse, few products and fewer free options exist to help present databases in a human readable format.
<code>sp_doc</code>'s goal is to generate on the fly database documentation in Github Flavor Markdown (GFM). This means you now have a free and extensible self-documenting database!
</blockquote>
Update: It can now also be installed via dbatools' <a href="https://github.com/sqlcollaborative/dbatools/blob/development/functions/Install-DbaMultiTool.ps1" rel="nofollow noreferrer">Install-DbaMultiTool</a> command as well.

blocks|key|1385660|text|ERD图(数据库图)对我的团队总是最有用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1385661|但是在我们创建的每个表和列的属性中都有写"Decription“的规则。|1385662|然后，我们使用一个软件名是企业架构师(+Enterprise+)来记录Tables和所有Indexes、Foreign+Keys和Columns以及Type和描述。|offset|length|style|CODE|1385663|📷|atomic|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://i.stack.imgur.com/qTrKM.png|imageAlt^0|0|0|Z|6|18|7|1G|C|1T|7|22|4|0|0|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@$F|X|G|Y|H|I]|$F|Z|G|10|H|I]|$F|11|G|12|H|I]|$F|13|G|14|H|I]|$F|15|G|16|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|17|8|@]|9|@$F|18|G|19|1|1A]]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

ERD Diagrams (Database Diagrams) were always the most useful ones for my team 

But there is rule to write "Decription" in Properties of each table and column which we create. 

Then we use a software name is Enterprise Architect to document <code>Tables</code> with all <code>Indexes</code> , <code>Foreign Keys</code> And <code>Columns</code> with <code>Type</code> and Description. 

<a href="https://i.stack.imgur.com/qTrKM.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/qTrKM.png" alt="enter image description here"></a>

blocks|key|2529047|text|特别是对于MySQL，我们总是使用MySQL工作台。我们在设计器中创建数据库设计，然后将其导出为可运行的SQL脚本。应用设计中的所有更改，然后运行生成的脚本，可以确保设计和实际数据库完全同步，并且文档不会像以前那么容易过时。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|https://www.mysql.com/products/workbench/^0|H|8|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

For MySQL in particular, we always use <a href="https://www.mysql.com/products/workbench/" rel="nofollow noreferrer">MySQL Workbench</a>. We create our database designs in the designer, then export it as a runnable SQL script. Applying all the changes in the design and then running the generated script ensures that the design and the actual database are perfectly in sync with each other, and that the documentation will not become outdated as easily.

I find that most of my clients are not documenting their databases at all and I find that pretty scary. To introduce some better practice, I would like to know what tools/process people are using.

<ul>
<li>How do you document your database? (SQL-Server) </li>
<li>What tool do you use? </li>
<li>Documentation Storage Format for database schema/meta-data?

<ul>
<li>Word documents</li>
<li>Excel spreadsheet</li>
<li>Plain Text</li>
</ul></li>
<li>Documentation process or policies?</li>
</ul>

I am not talking about reverse engineering / document a existing database, but mainly on the documentation best practices while you develop your system/database.

How do you document your databases?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我发现我的大多数客户根本没有记录他们的数据库，我觉得这很可怕。为了介绍一些更好的实践，我想知道人们使用的是什么工具/流程。你如何记录你的数据库？(Server)你用什么工具？数据库模式/元数据的文档存储格式？Word文档Excel电子表格纯文本文件处理还是政策？我不是在谈论反向工程/记录现有数据库，而是主要讨论开发系统/数据库时的文档最佳实践。

问你如何记录你的数据库？
EN

回答 15

Database Administration用户

Database Administration用户

Database Administration用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问你如何记录你的数据库？EN

回答 15

Database Administration用户

Database Administration用户

Database Administration用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问你如何记录你的数据库？
EN