I added a linked server by using SQL Server Management Studio and NT authentification (sa)
I can connect to the server and see databases but I cannot query anymore
The option to data access is set to True
So I don't know what's wrong
EDIT: This morning, after trying again i could execute a query!
So, i can't find why but it's work! \o/
i'm not sure i get the issue because you write 'i cannot query anymore' as if you ever succeeded but if you expect to be able to right click on an object (table or view) accessible through a linked server and get the usual SELECT TOP X or Edit top X menu then you're out of luck: this is a feature that is not available on objects accessed through a linked server.
i just made a test on sql server version 2005, 2008 and 2012 using SSMS 2012 and 2005 and that right click menu is not available when on linked server.
I installed VS2013, VS2010 Shell (for the BI-Tools) and SQL Server 2012 on Windows 8.1 Pro. I configured the SQL Server and attached the AdventureWork2012 database successfully.
I created datasource > dataview > cube from the db above.
However, I got an error saying
"The project could not be deployed to the 'XX\DBT2' server because of
the following connectivity problems: A connection cannot be made to
redirector. Ensure that 'SQL Browser' service is running. TO verify or
update the name of the target server..."
I've checked the SQL Server and SQL Server Browser and both are running. (checked from SQL Server Configuration Manger)
I also checked the db connection I set up on the VB project. It said Test connection succeeded.
I think I missing some user permission thing but not sure which one is it so here is a little more info about the user right. The user I am using is the account that setup with the windows installation. I also followed some other article online that they said added a few more admin right (user, group) will solve this issue which it didn't for this case.
I also go into the SQL Server Management Studio and check the database permission. And the user right as well but I can't seem to find any problem.
I'm experiencing a weird problem with a SQL login. When I connect to the server in Microsoft SQL Server Management Studio (2008) using this account, I cannot see any of the tables, stored procedures etc. that this account should have access to on a particular database.
When I connect to the same server within Visual Studio (2008) with the same account everything is there. When I connect with the same account on a Virtual Machine everything is there. I've also had a co-worker connect to the server using the same login and he's able to view everything as well.
I use Microsoft SQL Server Management Studio all day connecting to different servers and databases and I've never experienced this problem.
Does anyone have any suggestions on how I can diagnose this problem?
I've checked to make sure I don't have any Table filters etc.
There's several database on this server and I'm able to see the correct tables that this account has access to in the other databases just fine.
Running this query lists the tables I'm expecting to see.
SELECT * FROM INFORMATION_SCHEMA.TABLES
I've solved my problem. It's a bug... Here are the details.
https://connect.microsoft.com/SQLServer/feedback/details/387616/tables-node-does-not-show-all-schemas-in-ssmse-2008
fire up SQL Profiler then refresh the database list in SQLSMS and see what the query is that it uses to list the databases.
you can restart sql management to fix it.
I'm working on a C# application that queries a SQL Server 2008 Express instance on a remote server (LAN).
When I am at my workstation/dev machine, I can open SQL Server Management Studio and connect to the SQL instance through Windows Authentication, and for all intents and purposes the experience is identical to working in SSMS "on" the server. As far as I can tell, I can do anything from my workstation that I'd be able to do on the server.
That same server hosts an Access 2003 .mdb file, which is set up as a linked server in the SQL instance.
The queries in question return result sets compiled by joining tables from a SQL db and the Access db.
When I execute a query "on" the server, which is to say that I am running SQL Server Management Studio on the server machine, everything works as expected. When I try to run the same queries from my dev machine, however, whether in SSMS or when attempting to run integration tests or debug the application, I can do nothing at all with the linked server. I can see it in SSMS, but any attempt to execute anything results in:
Cannot initialize the data source object of OLE DB provider 'Microsoft.Jet.OLEDB.4.0' for linked server '<DatabaseName>'.
I have looked through many threads relating to this error and have tried many permutations of provider settings, all to no avail.
Access DB does not have password (I've tried setting the security to use name "Admin" w/o password)
workstation user account has full permissions on server directory where Access DB is located
same behaviour was experienced with server as Win XP Pro SP3 and now with Win Server 2003
same behaviour was experienced with client as Win XP Pro SP3 and now with Win 7 Pro x32
Works great on the server, never remotely.
Help much appreciated.
Using SQL Server authentication instead of NT Auth, as suggested by Burnsys, seems to do the trick. The why of the matter seems to be an open question.
I've seen numerous answers to similar questions like this one. I haven't seen on the web many people have asked the seemingly simple question "How do I connect Access 2007 to an SQL server 2008 database" - but all of the answers describe how you can migrate from access 2007 to an sql server 2008 database, or they describe how to connect access 2007 to an sql server 2005 database. I can't find any simple solution to my problem (and probably this is a problem for many others). Here is the question (sorry for the over emphasis):
How do I connect to an sql server 2008 database (and I mean 2008, not 2005 :) ) from access 2007? Apologies again for the over emphasis, but this very simple question, and what I thought should be a very simple task seems, yes, ... impossible!
I tried running sql server browser, enabling pipes, TCP etc, but it seems that with 2008 SQLEXPRESS just isn't recognised! Please can someone help with this.
Peter
Guys - you really should check whether this works before firing off random answers. It takes all of about a minute to run up an Access project and discover that it doesn't actually connect to SQL 2008 easily.
There are plenty of reasons to use projects instead of ODBC, but here's a few:
Existence of DSN on deployment machines cannot be guaranteed
Network traffic - does not do pass-through queries by default
Poor support for stored procedures
Assuming that appropriate protocols have been enabled, the solution is to go to the Advanced tab of the data link dialog and delete the value in the Network Library setting.
There should be no issue with connecting Access 2007 to a SQL Server 2008 database.
You need to make sure that:
Your SQL Server 2008 database is accessible, ie that it isn't locked down and that it is accessible to the machine(s) where you will have your Access 2007 application.
A few things to check:
In SQL Server 2008, go to Properties > Connections > Check "Allow remote connections to this server".
Enable TCP/IP in the Configuration Manager.
Make sure the firewall allows incoming connections on TCP port 1433.
You can also start the SQL Server Browser Service so your SQL Server instance can be found.
You have created an ODBC DSN (a System DSN) using Windows ODBC administration tool. If you're running on a 64 bit system, make sure that you're using the 32 bit version of ODBC to create your DSN, otherwise it will never be visible to Access which is a 32 bits application.
Once you have created the ODBC link (and tested it works) on the machine where Access is installed, you can just link the tables: In Access 2007, in the External Data ribbon tab > import > More > ODBC Database.
Then select the DSN you create for your SQL Server 2008 database and chose which tables you want to link.
Ray,
The reason you are not seeing your database is because of permissions. You need to grant the user name you are using access to your database.
In MS SQL Server Management Studio expand the database you created and go to the security tab to configure the user name you are using. Either add it or create a new user
Hope this will help....
When going through the link or import wizard in Access choose Sql Native Client 10.0. When asked which server you wanrt to connect to, the server will not show in the combo box. If you type the correct name of the server and hit next, you will go to the authentication screen. Use windows authentication if that's what you choose and hit next. On the next screen, check the Change default database box and your server databases should appear; then you know that you have a good connection. Remember you have to type the correct server name, which should be MACHINE NAME\SERVER INSTANCE NAME.
One solution (though this may not apply to SQL Express) is to use an Access Data Project, although in 2007 it's not that intuitive how to do this.
Create a new (blank) DB, but rather than accept the default .accdb extension, change it to .adp. You can also select Access Data Project (.adp) format if you use the browse dialog to set the file location.
Once created, you will be asked if you want to link to an SQL DB... the rest is pretty intuitive, but ask for further details if you need to.
SQL Express 2008 + Access 2007 both on a workstation.
Connect to Adventureworks SQL db from Access 2007.
Here we go...
Open Access 2007
click on the windows or top left icon/ new/ click on blank database/ put in file name/
click on the browse icon/ save as type/ Microsoft Office Access Projects (*.adp)/ click OK/
click Create/ on the question do you want to connect to an existing SQL server database?
click Yes/ you can use the dropdown box to select your computer but put in it like this... (eg if your computer name is "laptop") put in... laptop/SQLEXPRESS
Click on user windows NT integrated security/ hit the down arrow on step 3. Select the database on the server: and it should show the adventureworks database. click test if you like or just OK.
Just had the same problem but found a link that suggested referring to the server in the Data Link Properites Dialog as .\SQLEXPRESS - It would seem the [.] before the instance name made all the difference.
That did the trick for me - I got connected but then access complained that the version combo - Access 2007 & SQL 2008 did not support managing DB objects form Access.
Message was as follows:
This version of Microsoft Access does not support design changes with the version of Microsoft SQL Server to which your Access project is connected. See the Microsoft Office Update Web site for the latest information and downloads. Your design changes will not be saved.