My scenario:
Access 2013 FE > SQL Server 2012 BE > Linked Server To IBM DB2
The FE Needs to be used by multiple people. I'm calling SP's in SQL Server that update the IBM DB2. The only easy way for Access to talk directly to the IBM is to install 'Client Access' on each client, which I don't really want to do, hence I use SQL Server and a DSN Less connection as the bridge.
My Problem:
The front end involves user selecting multiple items, adding them to a SQL Server table and then a SP runs that in turn updates the IBM DB2. However, if multiple users are using the FE, then they will all be adding multiple items to the one table, which I don't want, it needs to be session\client specific.
Is there a way round this?
Related
We have a lot of linked servers in our SQL Server 2012 instances. While browsing one of those linked servers, I noticed that a log-shipped database is unavailable there.
The database itself is "Standby / Read-Only."
Is it normal for log-shipped databases to be unavailable over linked servers, or is it more likely to be a permissions issue, or could it be something else? I want to query this database using a linked server query.
The cause of my problem is obviously a permission configuration with the linked server entry. I know this because I set up the same linked server on my local SQL Server instance--using my own login credentials--and was able to see the "Standby / Read-Only" database as I would've normally expected for a standard database. Clearly, then, there is something about the linked server setup on the other server that is restricting me from viewing one of the databases.
I am attempting to set up a MS Flow to add data to my SQL Server database. To set up the Flow Connection there are only six items:
Connect via on-premise data gateway
Connection Name
SQL server Name
SQL database Name
Username
Password
However, when I fill in the appropriate information I get the following error "Please check your account info and/or permissions and try again."
Please note that I can login to my database via SMSS and run queries (e.g. create a table)
Some complexities that are likely affecting the outcome:
(A) I have to logon to a VPN to my University (with my University ID/Password) before I login to the database via SMSS (with my database Login/Password using SQL Server Authentication).
I have tried to create the connection using all sorts of permutations (e.g. on the VPN vs. off the VPN, University ID vs database ID) but have been unable to find the right combination.
(B) I not on campus (and rarely am).
(C) I did not realize until now that there is a paid Flow and my University has the Free plan. However, looking at the features/pricing I should be able to hook up to my SQL Server database.
The error I am getting is both specific but not very helpful as far as giving me any hints on what to change.
With only six options, there is not a lot I can do with the MS Flow. Is there a setting within the SQL database that I need to change?
I need to be able to connect to 3 remote databases simultaneously from my local SQL Server instance using SQL Server 2008 R2. Db1 and Db2 are both on Svr1 and Db3 is on Svr3. Each database requires a different login to gain access. I want to write a script that has simultaneous access to all 3 databases.
I gave up trying to create these using sp_addlinked server (despite successful use of this in past projects) because I simply could not get any of the connections working. I did manage to set up working linked servers for access to Db1 and Db3 on Svr1 and Svr3 respectively, no problem, using SSMS (right click on Linked Servers, New Linked Server). However, I don't know how to set up the linked server for db2 - it will not allow me to set up 2 linked servers with the same name (understandably). When I try to set up one using a name that does not map to a known SQL Server instance (and so use a data source or provider string to connect), it won't work.
Can I do what I want to do using the SSMS method? Or is there a way I can use the same linked server for Db1 and Db2 but use different logins somehow?
We recently moved a database from MS SQL Server 2000 to MS SQL Server 2008. Everything works as expected with our main .NET client application but we are having problems with a MS Access 2003 application which connects via ODBC. A System DSN is used to make the connection.
When the database was running on SQL Server 2000 the Access application would request a user name and password once when the program was first started. Now, with the database running on SQL Server 2008 a user name and password dialog is requested every time a different table is accessed I believe.
This behavior occurs when using either the user account we have used for years and it also occurs if I use the database system admin account ( I know this is bad practice, it was just a test. )
What do I need to reconfigure to return to the previous, desirable behavior where the user is only authenticated a single time?
You could look at using a "DSN-Less" connection to MS SQL, microsoft provide instructions here: http://support.microsoft.com/kb/892490
The relevant connection string can be found here: http://www.connectionstrings.com/sql-server-2008#p3
All this aside, JMK's question is important, the method above is for if you are having linked tables to the server present in your Access database, however when working with dedicated database server's I always advise using "ADO" connections rather than "DAO" as this will avail better performance (especially if you are running queries)
If it is just queries you need to run then consider either the ADO method or take a look at the "Pass through" queries option, this like ADO will have the server doing the work rather than the local machine and the performance will be greatly improved.
I am working on a database application that runs on various independent servers.
Each server runs an Instance of SQL Server 2005 with the same database. We would have a Master Server where that would be the definitive source of information and various "Client" Servers that would be distributed around (with no network connection of any kind). This Client Servers would return from time to time (lets say once a week) to be synchronized with the Master. Simply put the process would be.
1) Update the database on the master server with all the modifications from a client server (taking into account not overwriting changes made by the update process of a different client server [that would update the same master server])
2) Copy an updated version of the master server database to the client server.
Thanks for any help
MS SQL Integration Services may help:
http://www.microsoft.com/sql/technologies/integration/default.mspx
Also check for database replication. Check the Master-Remote part too.