I've loaded the DB onto my local dev SQL2000 server and can connect to this DB just fine from the application. Now when I export this DB to the production server and attempt to connect the application to IT, I get the wonderful error above. I have checked over everything 20 times at LEAST. The user/login exists, and it has the proper permisisons/rights (ie. the same as I have on my dev server which is working).
Connection string for local machine which is working:
var MM_eDFMEAConnect_STRING = "Provider=SQLOLEDB;Data Source=ANNMIW40QZG31;User ID=eDFMEAuser;Password=password;Initial Catalog=PSCO_eDFMEA"
Connection string for remote production server (not working):
var MM_eDFMEAConnect_STRING = "Provider=SQLOLEDB;Data Source=marmissql01\auto_sql;User ID=eDFMEAuser;Password=password;Initial Catalog=PSCO_eDFMEA"
Can someone see something I am missing? or suggest something to try?
This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.
Load balancing is the method of dividing the total amount of work performed by one computer between two or more computers. Its aim is to get more work done in the same amount of time, ensuring that all the users get served faster.
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed