Extracting data from a packaged SQL Server Express 2008 application / database

Question

Extracting data from a packaged SQL Server Express 2008 application / database

mstone 9417

SSC Journeyman

Points: 96
More actions
March 2, 2015 at 5:51 am

#295672

Apologies if this is naive. I have a product which runs against a SQL Server database on a standalone Window 7 PC. I know the data structure from experience of the product before it was converted from Access, which allowed me to get at the database and write bespoke queries though this wasn't encouraged by the vendor for some reason. Subject to knowing the relevant username and password, which I think I do, I am assuming that I should be able get at the data in the .MDF file ? I tried setting up a new ODBC data source in the hope that I could query via Access. However, this failed as follows :-
Microsoft SQL Server Native Client Version 10.00.2531
Running connectivity tests...
Attempting connection
[Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [2].
[Microsoft][SQL Server Native Client 10.0]Login timeout expired
[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
TESTS FAILED!
Could direct access from the host machine be viewed as remote ? In which case it could be that access from outside the packaged application is being blocked ?

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

EMarkM Ten Centuries Points: 1114 More actions · Answer 1

There's a bunch of stuff to look at here, if I'm reading your post correctly.

Who administers this instance of SQL? In other words, do you have a DBA that looks after this stuff, or has it all fallen on your shoulders?

What you seem to be getting is a message that you simply cannot get through to the server. This could be for several reasons.

Often firewall is the first place to look, but as we're all local here I would rule that one out for now.

Named Pipes is mentioned - perhaps this connection protocol has been disabled for this instance of SQL - the most recent organisation I worked at only ever had TCP/IP enabled - all other protocols were out.

How are you attempting to connect to the server - via Windows authentication or a SQL login and password that a DBA has given you?

Are you or the DBA able to pop into the SQL Server logs and observe the failed login attempts?

There's other stuff to discuss, but we could do with covering the above first.

mstone 9417 SSC Journeyman Points: 96 More actions · Answer 2

What I have is a packaged product on my standalone PC which uses SQL Server as its database. Some of the data that I can see via forms within the application would be much more use if I could extract and manipulate it. At present my only option is manually transcribe the information into a spreadsheet. My cluelessness probably doesn't warrant a solution here but any help would be appreciated. I've tried windows authentication and username / password which I discovered in some of the distribution files. However it doesn't get as far as processing the username / password login.

EMarkM Ten Centuries Points: 1114 More actions · Answer 3

Perhaps a silly direction for me to take, but can you confirm the following:-

1. The SQL instance is up and running on the box (simply check in services is probably the easiest way).

2. You have SQL Server Management Studio installed either there or somewhere else so that you can actually examine the SQL Server.

3. If you can connect to the SQL Server via SSMS, can you expand Security\Logins and confirm that either (or both of) the Windows user you're using or the SQL login/password combo that you mentioned are present.

4. Once you have established that one of the logins is present, does it definitely have read access to the specific SQL database that you're trying to connect to?

mstone 9417 SSC Journeyman Points: 96 More actions · Answer 4

Thanks for your continued interest. Two SQL Server services are running - MSSQL$SQLEXPRESS and SQLWriter. I had come to the conclusion that I need to get Management Studio installed. However, I want to do so without compromising / changing the SQL Server software I already have installed and which the application relies upon. That should be possible ?

EMarkM Ten Centuries Points: 1114 More actions · Answer 5

Sure thing; you can install just the client tools wherever you like with no problem at all.

Just make sure that you, or whoever helps with the installation, selects only the connectivity and management tools in the setup screen - it's fairly clear when you get there.

Good luck, and let us know when you are in a position to make those checks.

mstone 9417 SSC Journeyman Points: 96 More actions · Answer 6

I'm assuming I pick it up here - http://www.microsoft.com/en-us/download/details.aspx?id=7593 - and that I need the x86 version ? My PC is 64 bit but the SQL Server software and database are located in the 'Program Files' directory rather than the 'Program Files (x86)'.

mstone 9417 SSC Journeyman Points: 96 More actions · Answer 7

The attachment I added to my previous post relates to the fact that I've stumbles upon import/export as a potential route to what I need. Will check further.