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  :-)

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)

MSSQL:

And for SQL Compact Edition…

The tooltips have extra info too.

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

PK  :-)

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!

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 :-)

I had some more questions regarding Mini SQL Query recently, this time via http://minisqlquery.codeplex.com/Thread/List.aspx (most have come come via email to date)

I thought I would post the response too just as a general update on activities…

----

Thanks for the detailed feedback and questions. I’ll answer in order of difficulty/priority:

Status

The status bar stuff is there – I think I just forgot about making good use of it - Ahem! I know that the lack of knowing that you are connected has been an issue in the past.

Query Execution

Background execution of the query has been on the cards for a long time just not a high priority (again, this is use style driven, i.e. most of my queries are against development tables etc). The ability to cancel the query it falls in the same category, it's been a rare need to date but I will look at adding it as part of the background runner enhancement.

Regarding events on completion etc, that’s easy to add. I would just create an event for Before/After query execution with reference to the executing editor (in turn giving access to the query and results). That would probably be raised via the service manager or host window etc. I’ll have a look.

Connections

I can see where you are coming from. Personally almost all my connections use SSPI so I don’t have the password save problem. Probably the easiest way to do it would be a “don’t save the password” option for each connection definition.

To be honest the connection stuff has always been an issue. I would class it as “passable” but definitely not a good interface – it’s just really basic and gets me by. I think I did it in my “anti-XML” phase. I am over that not but just have not revisited the problem!

Minimise/Notify Icon

Fairly easy to do but probably won’t make my to-do list. As always a patch is welcome if you are willing (failing that a straight forward snippet of code etc)

Current Activities

I am actually in the middle of refactoring the projects together as some things have changed over time (and the fact that the app is now open source). I will look at these tasks above in the order above but there is no timeframe to it – again, if you have changes you are willing to make let me know. On that, just let me know if you are working on an area and I’ll stay clear of it for a bit! I have had really useful contributions in the past and have put most in but some haven't made it but only because I was too busy at the time etc...

PK :-)