解剖SQLSERVER 第十篇 OrcaMDF Studio 发布+ 特性重温(译)
解剖SQLSERVER 第十篇 OrcaMDF Studio 发布+ 特性重温(译) http://improve.dk/orcamdf-studio-release-feature-recap/ 自从我上次作了一个OrcaMDF特性概述之后,两个半月过去了。 只是两个半月过去了自从我上次一个OrcaMDF特性概述。 从那时起我一直在忙着
解剖SQLSERVER 第十篇 OrcaMDF Studio 发布+ 特性重温(译)
http://improve.dk/orcamdf-studio-release-feature-recap/
自从我上次作了一个OrcaMDF特性概述之后,两个半月过去了。
只是两个半月过去了自从我上次一个OrcaMDF特性概述。从那时起我一直在忙着参加SQLSERVER的最顶级的三个会议:SQLBits、SQLPASS、SQL Rally
大家对OrcaMDF的交流都很热烈,并且从他们身上获得了一些反馈,感谢您们所有人!
虽然一直比较忙,但是我尽量保证不丢下OrcaMDF 的开发工作
相比起国内,SQLSERVER的相关会议实在太少了
《SQL Pass北京举行2014年第一次线下活动》
新特性
下面是一个简单的列表自上次发布的特性开始
支持多数据文件数据库
通过标准SQLSERVER DMVs 暴露元数据
优化性能:字节数组使用更轻型,同时共享单一实例表模式之间的所有行
另外,我还添加了对一些额外的数据类型的支持
money
smallmoney
uniqueidentifier
用户定义类型
这些新特性只是一些小事情,接下来有个更大的事情 OrcaMDF Studio
OrcaMDF Studio
从这些反馈中我获得一些信息:太厉害的项目了!我绝对想试用一下这个软件,但是我还没有时间去使用
老实说,试用OrcaMDF会比较麻烦,你必须下载源代码,并且编译他,还要用自己写的程序去调用OrcaMDF
我没有考虑到直接最终的用户,这不是我所关注的。然而,为了得到更多的对OrcaMDF的使用反馈我必须对OrcaMDF进行改进
因此,我决定创建OrcaMDF Studio-这是一个UI 构建在OrcaMDF之上 允许你查询用户表,DMVs,系统表而不需要直接看源代码了
下面你看到的是OrcaMDF为你显示的一个标准的AdventureWorks 2008数据库中的Product表内容:
系统表
OrcaMDF Studio展示了所有的系统表(当前支持的 和能够解析的),就像普通表一样
用户表,索引和架构
最后,OrcaMDF 也展示了所有的用户表,包括他们的架构,索引和索引架构
错误报告
无论是OrcaMDF还是OrcaMDF Studio,距离投入生产环境依然是比较遥远的,你可能会遇到不支持的场景或者一些常见的错误
如果你遇到了,OrcaMDF Studio会将他报告出来,并且保存堆栈信息在程序目录里面。下面是一个典型错误的例子
尝试打开一个不受支持的XML数据类型列的表
如果你查看在程序目录里面的ErrorLog.txt文件,你会看到下面的异常
<span>25</span><span>-</span><span>11</span><span>-</span><span>2011</span> <span>00</span>:<span>41</span>:<span>21</span> <span>--</span><span>--------</span> System.ArgumentException: Unsupported type: xml(<span>-</span><span>1</span><span>) at OrcaMDF.Core.MetaData.DataColumn..ctor(String name, String type, Boolean nullable) </span><span>in</span> D:ProjectsOrcaMDFsrcOrcaMDF.CoreMetaDataDataColumn.cs:line <span>135</span><span> at OrcaMDF.Core.MetaData.DataColumn..ctor(String name, String type) </span><span>in</span> D:ProjectsOrcaMDFsrcOrcaMDF.CoreMetaDataDataColumn.cs:line <span>20</span><span> at OrcaMDF.Core.MetaData.DatabaseMetaData.GetEmptyDataRow(String tableName) </span><span>in</span> D:ProjectsOrcaMDFsrcOrcaMDF.CoreMetaDataDatabaseMetaData.cs:line <span>155</span><span> at OrcaMDF.Core.Engine.DataScanner.ScanTable(String tableName) </span><span>in</span> D:ProjectsOrcaMDFsrcOrcaMDF.CoreEngineDataScanner.cs:line <span>31</span><span> at OrcaMDF.OMS.Main.loadTable(String </span><span>table</span>) <span>in</span> D:ProjectsOrcaMDFsrcOrcaMDF.OMSMain.cs:line <span>158</span>
弹出一个完全匿名的错误提示,如果你遇到错误,我会很感激你将ErrorLog.txt file文件发给我以便调试有潜在问题的程序
所有的问题,错误报告,软件要求都可以发电邮给我
数据库版本支持
OrcaMDF 一开始对 SQL Server 2008 R2进行开发和测试,一些操作也能够在SQLSERVER2005上使用
不过会有很多错误,因为SQLSERVER2005的系统表结构跟SQL Server 2008 R2系统表结构有些不一样
OrcaMDF 对于不同版本的SQLSERVER并没有区别对待,当你使用不同版本的时候,稍后我会添加一个抽象层支持其他版本的SQLSERVER
打开正在运行的数据库
OrcaMDF Studio必须获得数据库文件的读锁。SQLSERVER在数据文件上持有排他锁,这意味着你不能打开一个正在运行的数据库
你只有分离数据库,使数据库脱机,备份-还原-分离或者 使用一个还未附加的数据库。
对于后续版本,我会添加一个自动VSS快照功能
系统运行要求
OrcaMDF建立在.NET 4.0之上,因此,你需要安装.NET 4.0 OrcaMDF Studio才能运作,OrcaMDF Studio可以运行在32位和64位机器上
免责声明
再一次,OrcaMDF 和OrcaMDF Studio 是实验用途的软件。对于使用他的任何风险不做任何担保。
OrcaMDF不会写任何东西进去你的磁盘,因此也不会以任何方式修改你的数据库文件。然而,我强烈建议你不要将他使用在生产数据库上
OrcaMDF 不知道也不关心信息安全,OrcaMDF 没有权限系统,无论谁拥有架构和对象,OrcaMDF 都会对他进行解析
而这个解析是不需要用户名和密码。但是,OrcaMDF 不支持对数据库做了透明数据加密TDE的数据,所以对TDE库里的数据是不支持的
下载
你可以从Github 的项目页面下载OrcaMDF Studio的二进制发布代码。请不要从其他地方下载OrcaMDF ,因为这些地方上面的
OrcaMDF 源代码有可能已经被别人修改过了。你应该总是从Github 的项目页面上获取源代码
一旦你下载了OrcaMDF,你需要执行OrcaMDF.OMS.exe程序
注意:这是debug模式下的调试版本,PDB文件。调试版本略低于发布版本,不过他允许我获取完全的堆栈跟踪当异常发生的时候。
一旦OrcaMDF 稳定下来了,我会提供调试版本和发布版本
第十篇完

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

For objects with the same name that already exist in the SQL Server database, the following steps need to be taken: Confirm the object type (table, view, stored procedure). IF NOT EXISTS can be used to skip creation if the object is empty. If the object has data, use a different name or modify the structure. Use DROP to delete existing objects (use caution, backup recommended). Check for schema changes to make sure there are no references to deleted or renamed objects.

The import steps are as follows: Copy the MDF file to SQL Server's data directory (usually C:\Program Files\Microsoft SQL Server\MSSQL\DATA). In SQL Server Management Studio (SSMS), open the database and select Attach. Click the Add button and select the MDF file. Confirm the database name and click the OK button.

When the SQL Server service fails to start, here are some steps to resolve: Check the error log to determine the root cause. Make sure the service account has permission to start the service. Check whether dependency services are running. Disable antivirus software. Repair SQL Server installation. If the repair does not work, reinstall SQL Server.

To view the SQL Server port number: Open SSMS and connect to the server. Find the server name in Object Explorer, right-click it and select Properties. In the Connection tab, view the TCP Port field.

SQL Server database files are usually stored in the following default location: Windows: C:\Program Files\Microsoft SQL Server\MSSQL\DATALinux: /var/opt/mssql/data The database file location can be customized by modifying the database file path setting.

If you accidentally delete a SQL Server database, you can take the following steps to recover: stop database activity; back up log files; check database logs; recovery options: restore from backup; restore from transaction log; use DBCC CHECKDB; use third-party tools. Please back up your database regularly and enable transaction logging to prevent data loss.

The problem was found that this time I was using the SqlServer database, which I had not used before, but the problem was not serious. After I connected the SqlServer according to the steps in the requirements document, I started the SpringBoot project and found an error, as follows: At first I thought it was a SqlServer connection. There was a problem, so I went to check the database and found that everything was normal. I first asked my colleagues if they had such a problem, and found that they did not, so I started my best part, facing Baidu. programming. The specific error message I started to solve was this, so I started Baidu error reporting: ERRORc.a.d.p.DruidDataSource$CreateCo

If the SQL Server installation fails, you can clean it up by following these steps: Uninstall SQL Server Delete registry keys Delete files and folders Restart the computer
