|
I just read through their Wikipedia page. It looks like it only persists objects, it seems it doesn't support SQL, it might not allow you to use queries to create different subsets of data.
Looking at their site now...
|
|
|
|
|
PIEBALDconsult wrote: it seems it doesn't support SQL
That's one of the things I didn't like about it, but they have a nice Native Query alternative that looks to be pretty sophisticated.
I've only been working with it for a couple of hours and have found a couple of things I don't like about it but can live with.
Also the documentation is decent so that helps a lot, at least for me.
|
|
|
|
|
If it does what you need, then use it.
|
|
|
|
|
PIEBALDconsult wrote: If it does what you need, then use it.
It looks like it will do what I want but I haven't used many embedded DB's so the only reason I posted was so if I got 3/4 of the way down the line and started finding problems, restrictions, etc. then maybe someone with more experience could save me the frustration and point me to a better EDB.
Anyway thanks for your input
|
|
|
|
|
for an embedded DB it's simply the fastest approach.
Not saying it's faster than SQL Lite or SQL Compact just that it's a lot
faster to create the app. No need to map or use ORM tools in order to fill
the gap between the ObjectModel and the DB Layer/Model.
I used it a lot as a small embedded DB and it's more than fine.
I wouldn't risk buying it and using it as a DB Server.
But for small/local/embedded DBs it just works.
I bug
|
|
|
|
|
Thanks that's exactly the feedback I was looking for. I'm just using it as a local DB as I didn't want users of application I am developing to have to install SqlExpress or other server just to run this app.. Just needed something fast, lite and easy to learn/use.
Thanks for the input,
Mike
|
|
|
|
|
you're welcome
I bug
|
|
|
|
|
Hi!
I"ve to add values to a field but the previous values should be deleted. Which query do I've to use?
|
|
|
|
|
T.RATHA KRISHNAN wrote: I"ve to add values to a field
A single field has a single value. The UPDATE-command would replace the current value of a field with a new value.
I are Troll 
|
|
|
|
|
I'll ask it anyway, having already tried Google and MSDN.
I'm fiddling with a SQL Server app to track substation equipment - one of several projects I'm working on. I've got a skeleton working on a local instance of SQL Server Express, but I'm thinking ahead to the day I deploy this on the company server, which has the full version of SQL Server installed. I don't want to manually recreate the database on the server - that way madness lies - and I don't want to Export/Import my existing database, as it's full of test cases I don't want to have to delete. I'm sure there's a nice, efficient way to create a database in SQL Server programmatically when my app runs for the first time, but I haven't a clue how to do it. Google returns a plethora of responses, enough to completely confuse me, and MSDN returns none of any relevance - the usual ratio.
Can someone point me to a tutorial of some sort that my aged brain can comprehend?
[EDIT]
While MSDN didn't help, I finally asked the right question in Google - which led straight back to Microsoft, of course:
using System;
using System.Data.SqlClient;
String str;
SqlConnection myConn = new SqlConnection ("Server=localhost;Integrated security=SSPI;database=master");
str = "CREATE DATABASE MyDatabase ON PRIMARY " +
"(NAME = MyDatabase_Data, " +
"FILENAME = 'C:\\MyDatabaseData.mdf', " +
"SIZE = 2MB, MAXSIZE = 10MB, FILEGROWTH = 10%) " +
"LOG ON (NAME = MyDatabase_Log, " +
"FILENAME = 'C:\\MyDatabaseLog.ldf', " +
"SIZE = 1MB, " +
"MAXSIZE = 5MB, " +
"FILEGROWTH = 10%)";
SqlCommand myCommand = new SqlCommand(str, myConn);
try
{
myConn.Open();
myCommand.ExecuteNonQuery();
MessageBox.Show("DataBase is Created Successfully", "MyProgram", MessageBoxButtons.OK, MessageBoxIcon.Information);
}
catch (System.Exception ex)
{
MessageBox.Show(ex.ToString(), "MyProgram", MessageBoxButtons.OK, MessageBoxIcon.Information);
}
finally
{
if (myConn.State == ConnectionState.Open)
{
myConn.Close();
}
}
Sorry about the formatting - that's Opera at work...
The article further states that, if I want just to use the Model database, eliminate all the crud and use simply, str = "CREATE DATABASE MyDatabase".
I haven't tried it yet as it's getting rather late, but I think I'll play a bit later this week. I presume that I can then use CREATE TABLE and all its sundry relatives to fill out the details once this part works, and I've already found a way to enumerate the available SQL Server instances, which will allow the end user to decide which server to host the app on.
Assuming that this works as advertised, and since it doesn't seem to be common knowledge, I suspect that it will make a decent article or tip. 
By the way, the article is located at: support.microsoft.com[^]
[/EDIT] We now return you to our regular programming...
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
modified on Wednesday, August 4, 2010 1:47 AM
|
|
|
|
|
Roger Wright wrote: I'm sure there's a nice, efficient way to create a database in SQL Server
Not programatically but there are 2 very simple ways to move a copy of your database to the production server. You can either backup your express version and restore it to the server or take a copy of the .mdf and .ldf files to the server and attach them. I think the attach one has the benefit of bringing the diagram which the backup/restore misses. Both are VERY simple processes.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Have you ever tried coding this[^] into a SqlCommand? I think I may give it a try...
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
I haven't done it in your kind of environment, but the following approach has worked for me elsewhere:
connect_to_server();
if (error_db_not_exist == open_database(my_db))
{
read_from_file(canned_sql);
run_query(canned_sql);
if (success != open_database(my_db))
}
where canned_sql is the appropriate set of creates, etc. Hopefully you can get this by querying system tables on your test server. An alternative is to export your test db, then delete all the *data* from that, leaving just the "structure".
HTH
Peter
Software rusts. Simon Stephenson, ca 1994.
|
|
|
|
|
It sounds to me that it's something similar to this[^] you need.
It creates a script for recreating a database on another server.
"When did ignorance become a point of view" - Dilbert
|
|
|
|
|
That's worth a look, Jorgen - Thanks!
It just seems silly to me that I can't export my database to a XML file, then regenerate the database on the target server using that file. I've used db-based product before that create the database on installation, but I assumed there was a CREATE DATABASE function, in addition to the CREATE TABLE function used regularly. It never occurred to me that they were scripting a copy and import process in the installer.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
I agree with Mycroft. I detach the database, copy the files, and reattach.
|
|
|
|
|
It sounds like scripting is the best way as you do not want everything to go. However I do not know if Express has scripting.
Another way would be to 1) backup the database 2) truncate tables 3) backup to second file then restore the second backup to new server.
|
|
|
|
|
Actually, I found this[^] to be intriguing. I wonder if I can code this into a SqlCommand? 
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
I found the solution at Microsoft Support, not MSDN.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
I am using this code on SQL Server Expess as stored procedure. The icd_disease has 12,000 records but with LEFT(icd_code, 1) = 'R' it’s just 400 records. Then why it takes more than 40seconds to bind into grid control although I ave already indexed the icd_code and icd_description field
SELECT icd_diseases.icd_id, icd_diseases.icd_code, icd_diseases.icd_description
FROM icd_diseases
WHERE LEFT(icd_code, 1) = 'R'
ORDER BY icd_description, icd_code
This is my binding code
data_table = new DataTable();
sql_connection = new SqlConnection((string)public_var._system_parameters_hash["SQL_SERVER_CONNECTION"]);
sql_connection.Open();
sql_command = new SqlCommand("sp_get_all_symptoms", sql_connection);
sql_command.CommandType = CommandType.StoredProcedure;
sql_adapter = new SqlDataAdapter(sql_command);
sql_adapter.Fill(data_table);
dataSymptoms.DataSource = null;
dataSymptoms.ResetBindings();
dataSymptoms.DataSource = data_table;
gridSymptoms.Columns["icd_id"].Caption = "icd_id#";
gridSymptoms.Columns["icd_id"].AppearanceHeader.TextOptions.HAlignment = DevExpress.Utils.HorzAlignment.Center;
gridSymptoms.Columns["icd_id"].AppearanceCell.TextOptions.HAlignment = DevExpress.Utils.HorzAlignment.Center;
gridSymptoms.Columns["icd_id"].Visible = false;
gridSymptoms.Columns["icd_code"].Caption = "icd_code#";
gridSymptoms.Columns["icd_code"].AppearanceHeader.TextOptions.HAlignment = DevExpress.Utils.HorzAlignment.Center;
gridSymptoms.Columns["icd_code"].AppearanceCell.TextOptions.HAlignment = DevExpress.Utils.HorzAlignment.Center;
gridSymptoms.Columns["icd_code"].Visible = false;
gridSymptoms.Columns["icd_description"].Caption = "Symptom";
gridSymptoms.Columns["icd_description"].AppearanceHeader.TextOptions.HAlignment = DevExpress.Utils.HorzAlignment.Default;
gridSymptoms.Columns["icd_description"].AppearanceCell.TextOptions.HAlignment = DevExpress.Utils.HorzAlignment.Default;
gridSymptoms.Columns["icd_description"].Width = 420;
|
|
|
|
|
Figure out what takes more time, the query or the code. If it is the query, take a look at execution plan. Might help.
|
|
|
|
|
WHERE LEFT(icd_code, 1) = 'R'
Doesn't look very efficient. I'd add an extra (redundant) column that holds the first character that you're filtering on. And put an index on that field 
I are Troll 
|
|
|
|
|
I am sure there is something wrong because running a query to get all the 12000 on the same PC but using SSMS takes 1sec only! The issue is when I run it on winform either to get all or to get starting with R so no creating another col holding the first character won't help when I want to get all
|
|
|
|
|
jrahma wrote: when I want to get all
sp_get_all_symptoms
jrahma wrote: I am sure there is something wrong because running a query to get all the 12000 on the same PC but using SSMS takes 1sec only!
I don't think that SSMS is using a datatable to cache the entire table locally. Might be using a reader, filling your grids with results as they arrive over TCP.
If all the ICD-codes need to be on the client, why not put them on the clientmachine as a SqlCe database?
I are Troll
|
|
|
|
|
Why not just do this?
WHERE icd_code LIKE 'R%'
Isn't that the same thing as LEFT(icd_code, 1)? I don't know whether the query optimiser is smart enough to reduce the two queries down to the same thing or not. Using LIKE would definitely result in the optimiser considering using an index on icd_code if there is one. I don't know whether the query optimiser considers using an index for LEFT or not.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
