Splitting Database

7 posts / 0 new
Last post
CarlPalmer
CarlPalmer's picture
Splitting Database

I have a database that is approaching the 20000 file mark. How do I export a portion of those to a new database?

Can I use full blown SQL Server as a back end instead of Sql Server CE?

admin
admin's picture

Hi Carl,
You can use the function File -> Import from Alfa Ebooks Manager to import books to new database
You can use any SQL manager if you have knowledge in this program

CarlPalmer
CarlPalmer's picture

I don't want to use SQL manager. I want to run SQL database, and use it as a target for your book manager software, but you do not at present, that I can find, have any way to change the database location.

Since SQL CE and SQL Server both use almost the same connection string, I can't see that this would be that big an issue to implement. The 20000 book limit is far too limiting. I have far more than that in one directory.

There are no good book managers on the market that can handle large numbers of books, and I see in the forums all the time people slamming into these limited products.

Please give me the option at install to select a SQL Server that I can use at the back end instead of forcing me to use CE.

admin
admin's picture

Carl, we don't force you to use CE. You can use CompactView, for example

CarlPalmer
CarlPalmer's picture

OK, you have completely missed everything I just said.

I am NOT looking for a VIEWER. I have several viewers. I use SQL professionally every day. I am looking for a full on alternative to the database you are using for your product which is Windows Embedded Compact Edition. CE for short. This database is a stand alone file meant for small projects.

I want to use a full blown professional edition of MS SQL Server 2014, which resides on a server class machine. It is a full blown service meant for many millions of records.

Both types of SQL use the same syntax to get data, it is the connection string that is different. A connection string tells the program where the data is stored. This is what I want to change so that I can use your software for millions of records and not 20,000

I found the connection sting in the file aem.exe.config located in the root of the software. The connection string starts on line 13 in a tag called ^connectionStrings^

Please note I had to replace all the greater than and less than signs with carrots, or the forum would not display the code.

^connectionStrings^
^add name="bookLibraryEntities" connectionString="metadata=res://*/BookLibraryModel.csdl|res://*/BookLibraryModel.ssdl|res://*/BookLibraryModel.msl;provider=System.Data.SqlServerCe.4.0;provider connection string="Data Source=|DataDirectory|\Resources\BookLibrary.sdf"" providerName="System.Data.EntityClient" /^
^/connectionStrings^

What I want is assistance in changing the above code into something that can use MS SQL Server, not just the Embedded Compact edition.

Or better yet, be given the opportunity at install time to choose an existing MS SQL Server, and not Windows Embedded Compact Edition. It would take 3 parameters, server name, username, and password. The installation process would then have to test connection to the server, and then the installation would have to create the tables on that server. It would also have to modify the aem.exe.config file.

I know for a fact that there are many people out there wanting something that can address very large collections, as I do. Your software is fantastic. Your database management is extremely limiting. If you can provide the option to use other professional databases as an alternative, I am sure that you will see many more sales.

Calibre which is free, is pretty good. It has the same limitations. It also wants to copy all your files into a big pile. There are many people frustrated with it's design decisions. Your software does everything calibre does, and more. I love it. I just can't us it for a collection of hundreds of thousands of ebooks split into different types, where one type may have 50-60,000 books.

You have an opportunity to take your great software and make it Awesome, and put a product on the market that does what no other product does.

admin
admin's picture

ok, now its clear. we'll consider this feature for next versions

coolhacker
coolhacker's picture

I would love this ability too. Have you looked into this further? I tried to use the compactview and it claims it needs a password. I would love the ability write my own SQL statements to manage the database. If the database is just storing information and there is no code, I would hope you wouldn't feel like it is taking away from your copyright information. Anyways, SQL server would have no limit and this would not be for the common user I get it. I would even share anything I write including stored procedures. Thanks