Mini SQL Query Quick Start

by Paul Kohler 6. September 2010 06:04

I have finally had a chance to put together a simple “Quick Start” document for Mini SQL Query. It’s the main reason I have never made a formal “version 1” release!

Here is a link to the document: http://pksoftware.net/MiniSqlQuery/Help/MiniSqlQueryQuickStart.docx

I also “upgraded” the projects to version 3.5 of the framework as the version 2 requirement is all but gone. That was more around my usage on Windows Server 2003 etc.

 

PK :-D

Mini SQL Query RC1 Released

by Paul Kohler 5. October 2009 21:10

All,

I uploaded RC1 today: http://minisqlquery.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=33994

Lots of goodies including the new generic schema engine and text templating including access to the data.

One of the regular questions I get is if there is a plug-in that will convert “database A” to “database B”… answer… no – BUT – you can actually write a script connected to database A that writes out the schema for database b. Then you would run the generated SQL against database b. You could for example even create a db layout using Excel (one table per sheet etc), connect to it with Mini SQL Query and write a script that is a “create script” for the destination database. You can also get the data out with the template tool.

 

What’s Missing?

 

  • Schema wise the main thing missing is procedures/functions. Not all languages support them but it would be good to have for v1.
  • Another schema addition is foreign key information for other databases. This is not provided properly by the ADO.NET schema functions and so I manually provide it for the respective database driver.

 

PK  :-)

 

Mini SQL Query… go get latest!

by Paul Kohler 2. September 2009 00:55

I have finally got around to mapping through the Primary Key (for all DB’s) and Foreign Key info (for MSSQL and SQL Compact Edition)

MiniSqlQuery-SqlCe-ViewTable

MSSQL:

MiniSqlQuery-MsSql-DBInspector

And for SQL Compact Edition…

MiniSqlQuery-SqlCE-DBInspector

The tooltips have extra info too.

Go see http://www.pksoftware.net/MiniSqlQuery/Download.aspx the latest download…

PK  :-)

The Big Bang Mini SQL Query Changes

by Paul Kohler 24. August 2009 19:15

Just a quick note on some recent changes.

The other day I checked in some “breaking changes” around the gathering of database schema information. I used to rely on the very bland combined DataTable information. I took the plunge and converted it to populate a tree of classes:

  • DbModelInstance
    • Tables
      • Columns
    • Views
      • Columns

The columns contain some pretty rich data type information and have remained pretty generic.

There are primary key and non key collection filters etc. The main outstanding requirements that you simply cannot get out of the connection schema is foreign key relationships. This will need to be specific per connection which is a bit lame, some data sources will miss out simply due to the number of databases out there.

The other big change is that I am not trying to coerce all the schema gathering into the one area (my original hope) but now use a base schema collector with derivatives as required. Another advantage of this change is that I can actually provide schema information for databases that don not implement the “Get Schema” methods, for example, I have implemented an MS SQL Compact Edition (3.5) provider enabling Mini SQL Query to work nicely with SQLCE databases even though the provider throws a not implemented exception on a GetSchema call. I did this with a little help from Erik Ejlskov Jensen (http://erikej.blogspot.com). I am also looking at wrapping up his SQLCE Export tool as a plugin – see http://sqlcecmd.codeplex.com/.

Anyway, for now browse the code if you want to know more, I think its time for another release!

Mini SQL Query now using XML based connection definitions

by Paul Kohler 9. June 2009 18:00

I have finally completed the connection definition text to XML conversion for Mini SQL Query. The raw carrot (^) delimited line of text describing a connection string was the source of many email requests! Years ago the thing used to simply be the actual connection string (because they were all for MSSQL databases), then I expanded it to include a provider type and then when I decided to go public I thought a "named connection" string would be nice, appending another delimited field was the quick path...

That's all gone (well, is obsolete) in the latest source, I still need to update the GUI a bit but there is an automatic upgrade included for your convenience :-)