problem restoring database *Update*

[bossturbo]

I also sent an urgent ticket to linnworks official support, but hoping someone here may have an answer for me sooner.

--

OK, so my PC died that was the linnworks server. I've got a new 64-bit PC up and running and reinstalled a fresh copy of Linnworks server 64-bit. Apparently I had never done a database backup (linnworks never prompted me, so I never did it, whoops). I have the old hard drive installed in the new PC as a secondary drive, so I can access the old database files. But I am unable to "restore" the database since an actual backup was never done.

I've been following this thread: viewtopic.php?f=4&t=297&p=887&hilit=restore#p887

I've installed the Database Server tool by Microsoft, ran as Administrator all that jazz, but there is no backup files to be found, so the tool cannot perform a backup per usual. I have all the raw database files just fine last updated two days ago. Just for kicks I even just did a straight copy over the \MSSQL\Data files, but no luck.

Thanks, got some angry customers wondering where their product is!

[bossturbo]

OK I hacked together the old computer so I could run a "backup" from the linnworks folder in the program files in the start menu. I put all the components back in the new computer and it's still not working when I go to restore !

Now it gives me an error:
"
Restore failed for server 'Brian-pc\finaware' (microsoft.sqlserver.express.smo)

Additional information: System.data.sqlclient.sqlerror: The backup set holds a backup of a database other than the existing linnworks_finaware database.
"
Any ideas guys?

Why is this so complicated? Blackthorne restored in two clicks from within the program.

[bossturbo]

I forgot to check the "Overwrite data" checkbox. Everything worked after that.

[egyptiantrader]

I'm having the exact same problem. Did anyone find a fix? I agree this is way too complicated. There should be a restore function built into the program, users should not have to install 3rd party programs etc. it should be a 1 click operation like the backup function!

[bossturbo]

I'm having the exact same problem. Did anyone find a fix? I agree this is way too complicated. There should be a restore function built into the program, users should not have to install 3rd party programs etc. it should be a 1 click operation like the backup function!

Go into properties or something like that and make sure you have "overwrite data" checked... that's what my problem was.

[linn_systems]

there is no database restore utility supplied with linnworks because there is already one that does the job perfectly to begin with Microsoft Sql Server 2005 Management Studio.

In your specific case you need to go to Options and click Overwrite Existing Database option.

[Mark2356]

I'm having the exact same problem. Did anyone find a fix? I agree this is way too complicated. There should be a restore function built into the program, users should not have to install 3rd party programs etc. it should be a 1 click operation like the backup function!

Microsoft SQL is key to the whole program.

If it helps see it as a bit like needing windows to run things. Linn cannot do it all - we need them to choose good tools developed and used by millions - so that they can do their job well.

Having done a restore I know it can be a pain especially the first time and all I think is needed is some good documentation that also explains near the start why it has to be done through the MS SQL interface. Once you know and understand then the hassle seems acceptable and worthwhile. Rather than why on earth have linn made this so hard - which is what I thought first time round until I understood what was going on and why.

[jondoe]

I use ql Server Configuration Manger to backup SQL database. It involves a bit of learning at first s, but after that you can backup your database with no more than a few clicks taking a minutes or two by the program itself. I also use Blackthorne. It saves me time by running backup for both Linnwork and Blackthorne databases together via the sql Server Configuration Manger.