Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Goalie35
Yak Posting Veteran
81 Posts |
 Posted - 2012-02-13 : 14:38:52
|
| We have a new client who had some problems with their last development company. Their dev company only delivered a half completed website (asp.net) and setup a database for them on a server they don't know how to get to & unfortunately, this dev company is not returning their calls to provide assistance. So we've now been given the task of fixing this...My question is in regards to the database and what would you recomend is the best approach to dealing with a database that I can't physically access or view/modify data. The website successfully connects to this database via an odbc connection they setup (login credentials are in the site's web.config file). So at least I know it connects successfully. Unfortunatley though, like I said, I haven't been able to physically access this server.So my next thought was to perhaps try to see if there's a way to import the data into a new sql server database on the same server as their website. Can sql server (version 2005) import data via an odbc connection? Another option was perhaps I could create a .net application to go into their database via this odbc connection, find all database tables & data, then pull it down into a new sql server 2005 database on their server.Any suggestions on the best way to pull down the data from this server?Thanks. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2012-02-14 : 00:45:59
|
| To some extent , it will depend on your security permissions. You may also need to download jobs sitting on another database.Jack Vamvas--------------------http://www.sqlserver-dba.com |
 |
|
|
|
|
|
Recomendation for a database we can't access?