Anatomy of SQL Server tenth Orcamdf Studio release + feature Recap (translated)

Anatomy of SQL Server tenth Orcamdf Studio release + feature Recap (translated)

http://improve.dk/orcamdf-studio-release-feature-recap/

Since I last made a orcamdf feature overview, 2.5 months have passed.

It's only been 2.5 months since I last had a orcamdf feature overview. I've been busy since then. Top three meetings of SQL Server:sqlbits,sqlpass,SQL Rally

Everyone is very enthusiastic about the orcamdf, and received some feedback from them, thank you all!

Although always busy, but I try to make sure not to leave Orcamdf development work

Compared to the domestic, SQL Server related meetings are too few

"SQL pass Beijing 2014 first offline activity"

New features

The following is a simple list of features that have been started since the last release

Support for multi-data file databases

Exposing meta data via standard SQL Server DMVs

Optimized performance: Byte arrays use lighter, while sharing all rows between singleton table schemas

In addition, I have added support for some additional data types

Money
SmallMoney
uniqueidentifier
User-defined Type

These new features are just a little thing, and then there's a bigger thing orcamdf Studio

Orcamdf Studio

I get some information from these feedback: it's a great project! I definitely want to try this software, but I don't have time to use it.

To be honest, the trial orcamdf will be more troublesome, you must download the source code, and compile him, but also to use their own program to call Orcamdf

I did not consider the direct end user, this is not my concern. However, in order to get more feedback on the use of orcamdf I have to improve the Orcamdf

So I decided to create Orcamdf studio-which is a UI built on top of orcamdf allows you to query user tables, DMVs, system tables without needing to look directly at the source code

What you see below is the content of the product table in a standard AdventureWorks 2008 database that Orcamdf displays for you:

system tables

Orcamdf Studio shows all the system tables (currently supported and resolvable), just like normal tables

User tables, indexes, and schemas

Finally, Orcamdf also shows all the user tables, including their schemas, Index and index schemas

Error Reporting

Whether it's orcamdf or Orcamdf Studio, the distance to the production environment is still relatively remote, you may encounter unsupported scenarios or some common mistakes

If you run into it, Orcamdf Studio will report it and save the stack information in the program directory. Here is an example of a typical error

Attempt to open a table with an unsupported XML data type column

If you look at the ErrorLog.txt file inside the program directory, you will see the following exception

 -- One- . xx: A: +----------System.ArgumentException:Unsupported Type:xml (-1) at OrcaMDF.Core.MetaData.DataColumn. ctor (string name, String type, Boolean nullable)inchD:projectsorcamdfsrcorcamdf.coremetadatadatacolumn.cs:line135At OrcaMDF.Core.MetaData.DataColumn. ctor (string name, String type)inchD:projectsorcamdfsrcorcamdf.coremetadatadatacolumn.cs:line -At OrcaMDF.Core.MetaData.DatabaseMetaData.GetEmptyDataRow (String tableName)inchD:projectsorcamdfsrcorcamdf.coremetadatadatabasemetadata.cs:line155At OrcaMDF.Core.Engine.DataScanner.ScanTable (String tableName)inchD:projectsorcamdfsrcorcamdf.coreenginedatascanner.cs:line toAt OrcaMDF.OMS.Main.loadTable (StringTable)inchD:projectsorcamdfsrcorcamdf.omsmain.cs:line158

Pop up a completely anonymous error prompt, and if you encounter an error, I would appreciate you sending ErrorLog.txt file to me to debug a potentially problematic program

All questions, bug reports, software requirements can be emailed to me

Database version Support

Orcamdf began to develop and test SQL Server R2, and some operations can be used on SQLSERVER2005

There are many errors, however, because the SQLSERVER2005 system table structure is somewhat different from the SQL Server R2 system table structure

Orcamdf is not treated differently for different versions of SQL Server, and when you use different versions, later I add an abstraction layer to support other versions of SQL Server

Open a running database

Orcamdf Studio must obtain a read lock on the database file. SQL Server holds an exclusive lock on the data file, which means that you cannot open a running database

You only have to detach the database, take the database offline, backup-restore-detach, or use a database that is not yet attached.

For subsequent releases, I will add an automatic VSS snapshot feature

System Operation Requirements
Orcamdf is built on. NET 4.0, so you need to install. NET 4.0 orcamdf Studio to work, Orcamdf Studio can run on 32-bit and 64-bit machines

Disclaimer

Once again, Orcamdf and orcamdf Studio are software for experimental use. No warranties are made as to the use of any of his risks.

Orcamdf won't write anything into your disk, so it won't modify your database files in any way. However, I strongly recommend that you do not use him on the production database

Orcamdf do not know and do not care about information security, Orcamdf no permission system, no matter who owns the schema and objects, Orcamdf will parse him

This parsing does not require a user name and password. However, Orcamdf does not support data that is transparent to the database to encrypt TDE, so the data in the TDE library is not supported

Download

You can download the binary release code for ORCAMDF studio from the GitHub project page. Please do not download orcamdf from other places, as these places above the

Orcamdf source code may have been modified by others. You should always get the source code from the GitHub project page

Once you download the orcamdf, you need to execute the OrcaMDF.OMS.exe program

Note: This is the debug version of the PDB file in debug mode. The debug version is slightly lower than the release version, but he allows me to get a complete stack trace when the exception occurs.

Once the ORCAMDF has stabilized, I will provide debug and release versions

End of the tenth chapter

Anatomy of SQL Server tenth Orcamdf Studio release + feature Recap (translated)