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.
Related
I have been using Microsoft SQL Server 2017 for a while (just DDL and DML) and recently decided to install JetBrains DataGrip because I thought it was another DBMS but with dark theme.
When I try to create a new database it tells me to assign a host/user/password/port and I cannot do anything because it can't "connect to the database". I've been using Microsoft SQL Server Management Studio 2017 and never needed to assign a port/password/host or anything? I just created a new database and started adding/filling tables. How does JetBrains DataGrip work?
I noticed that on the JetBrains DataGrip page it doesn't say it's a DBMS, it says it's a "Database IDE". I cannot seem to find information about this on the web.
When considering a RDBMS such as SQL Server, the core component is a service/engine which acts as an interface between the database (files) and end users or applications allowing database functions to be carried out.
SSMS (SQL Server Management Studio) is just one of many possible end users of the SQL Server Database, and happens to have be part of the SQL Server software suite. It should not, however, be confused with the database itself as SQL Server operates perfectly happily without ever seeing SSMS.
Any form of user interface tool for a database needs to know how to connect to the database it is going to manage. In your case you most likely installed the entire software suite with default settings and as such didn't need to know what they were. JetBrains DataGrip however does need these settings.
You can find out what your specific settings are by running the SQL Server Configuration Manager.
JetBrains DataGrip is just a Database IDE to connect to different database engines via only one environment without needing to install management tools for every database that you want to work with.
Previously I was using the SQL Server 2008 Management Studio for my ASP.Net project. Database was on localhost. Now I moved the database to server and tried to connect it with SQL Server Management Studio but it was not working well with server. When I was adding table it said something like indexes are full. When I searched I got to know that it may be the version conflict as server SQL Server version may be different.
So I decided to use HeidiSql to connect to database. All goes well, but when I added a new table, HeidiSql created it like 'NewUser.tablename'. NewUser is the username for database. All the previous tables are like 'dbo.tablename'.
Why HeidiSql is saving like this? I tried every setting in HeidiSql but nothing is happening.
I am working on an Access accdb project and I have all my tables linked to MS SQL Server 2008 R2 via ODBC.
I have one screen with a sub form that always gives me this error message when I enter it:
I've done some research and it it supposed to be related to the server's authentication method, but if all my tables are linked the same way, why does it happen?
What's even more weird is that if I refresh my table's connections via the linked table manager, everything works fine for some time, and then I get the same error again. I look through my code to see if I play with any connection string, but I don't.
Any thought/ideas? Any (educated) guess you have will be appreciated :)
Thanks,
Yotam
Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode.
The server must be stopped and re-started before this will take effect.
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.
The company I work for has an old Access 2000 application that was using a SQL Server 2000 back-end. We were tasked with moving the back-end to a SQL Server 2005 database on a new server. Unfortunately, the application was not functioning correctly while trying to do any inserts or updates. My research has found many forum posts that Access 2000 -> SQL 2005 is not supported by Microsoft, but I cannot find any Microsoft documentation to verify that.
Can anyone either link me to some official documentation, or has anyone used this setup and can confirm that this should be working and our problems lie somewhere else?
Not sure if it matters, but the app is an ADP compiled into an ADE.
I've had a similar problem before when using ODBC linked tables to connect to an Sql Server. The solution was to relink the tables and specify the primary key to the table. If Access doesn't know the primary key it cannot perform inserts or updates.
I haven't any experience with ADPs but it could be a similar thing, theres a knowledge base article about it here http://support.microsoft.com/?scid=kb%3Ben-us%3B235267&x=15&y=13
I'd say check the VBA in the Macros to see how it is doing it. It is probably using some form of VB connection to the Database in the back. I love the fact a Database is contacting a Database for it's data... :)
All I've read about Access 2000 -> SQL Server 2005 is that the upsizing wizard isn't supported.
If only the inserts and updates aren't functioning, it sounds like a permissions issue. Make sure the sql server login you are using in your connection string has read/write permission on your database.
Please avoid using the "sa" account for this purpose!
If only the inserts and updates aren't
functioning, it sounds like a
permissions issue. Make sure the sql
server login you are using in your
connection string has read/write
permission on your database.
Please avoid using the "sa" account
for this purpose!
We wanted to use a generic apps account but that login "could not find" any of the stored procedures even though they existed and the login has explicit permissions to run them (and was also tested successfully, as that user, in SQL Management Studio). It wasn't until we granted that login "sa" privileges that we could actually access the database at all through the application.
but have you tried setting the
compatibilty mode for the database to
sql server 2000.
I'm not really sure how this is done. Could you explain?
Also of note, if we upgrade the app to Access 2003, everything works fine. Unfortunately, our IT dept does not want to upgrade everyone from Office 2000 to 2003, so this is not an option.
Thanks for your help.
I'm not sure about that particular combination being supported, but have you tried setting the compatibilty mode for the database to sql server 2000. Maybe that will resolve your issues.
Edit: To do this run the following SQL:
EXEC sp_dbcmptlevel Name_of_your_database, 80;
More details here: http://blog.sqlauthority.com/2007/05/29/sql-server-2005-change-database-compatible-level-backward-compatibility/
but have you tried setting the
compatibilty mode for the database to
sql server 2000.
I just checked the 2005 database, I selected the database, and clicked Properties->Options, and it says the db is already in 2000 compatibility mode.
Access ADPs are very closely tied to SQL Server versions, and MS has done a really poor job of fixing and breaking ADPs in the 3 major versions that have been released (2000, 2002 and 2003).
If you are trying to use the compiled ADE, I'd suggest that first you find the original ADP and see if you can get it to work. You may need to do some work there before creating your ADE.
Caveat: I don't do ADPs, and am glad I made the decision not to, as Microsoft is now deprecating them in favor of MDB=>ODBC=>SQL Server.