EVE-SECURE / evemarketmonitorapp

Automatically exported from code.google.com/p/evemarketmonitorapp
0 stars 0 forks source link

MSSQL Server R2 #35

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hey, I installed the Microsoft SQL Server R2 and it gives me errors here and 
there, is that because EMMA is incompatible with the R2 version ?

Original issue reported on code.google.com by xeross.theelitist.net on 9 Jun 2010 at 8:10

GoogleCodeExporter commented 9 years ago
I'm using the 2008 R2 Express without any problems. Can you give more detail on 
what the errors are?

Original comment by SteveBal...@gmail.com on 18 Jun 2010 at 3:17

GoogleCodeExporter commented 9 years ago
is this app working with Microsoft SQL server 2008? I mean full server, not 
express edition. Where I can change settings to sql server in app?

Original comment by russinow on 24 Jun 2010 at 7:41

GoogleCodeExporter commented 9 years ago
It does work with the full SQL server. However, you need to make a change to 
the database connection string.

Look in the installation folder for 'EveMarketMonitorApp.exe.config' (E.g 
C:\Program Files\EMMA\EveMarketMonitorApp.exe.config)

Take a backup of the file just in case and then open it and find the connection 
strings section. E.g:

    <connectionStrings>
        <add name="EveMarketMonitorApp.Properties.Settings.EMMA_DatabaseConnectionString"
            connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename="|DataDirectory|\Data\EMMA Database.mdf";Integrated Security=True;User Instance=True"
            providerName="System.Data.SqlClient" />
        <add name="EveMarketMonitorApp.Properties.Settings.ebs_DATADUMPConnectionString"
            connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Data\EveData.mdf;Integrated Security=True;User Instance=True"
            providerName="System.Data.SqlClient" />
    </connectionStrings>

These Need to be modified to point to your full SQL server install. I'm not 
sure, as I havn't done it but I believe this involves changing 'User Instance' 
to False and setting the 'Source' to the name of your SQL database. After that, 
I believe it should all work fine.

Original comment by Ambo.E...@gmail.com on 30 Jun 2010 at 12:23

GoogleCodeExporter commented 9 years ago

Original comment by SteveBal...@gmail.com on 9 Sep 2010 at 10:59