Well, I have a database running on shared hosting and have successfully connected to it. However, i cannot see the database but when i run i.e.
SELECT * FROM Item
Item is a table in it, i get correct result.
Further more, when connected via Visual Studio 2010 with the same credentials, i see it.
Ive had this issue before and resolved it by applying the current Service Pack to SSMS
It looks like a bug in Microsoft SQL Server Management Studio. See https://connect.microsoft.com/SQLServer/feedback/details/387616/tables-node-does-not-show-all-schemas-in-ssmse-2008
Related
I'm having a strange issue with MSSQL Management Studio 18.12.1 (I just updated it to the last version to try to fix it). It is not showing the tables of a database.
When I click to expand the tables it starts the process:
But after a little bit it gives up and does not show anything:
The tables are not new as the server is more than an year old and I can access the data with normal queries:
Does anybody know what am I missing? Is there a timeout setting to adjust?
I tried both with SA and normal users.
Thanks in advance.
I am having a problem with a SSIS project that downloads data from a MySQL database and insert it in a SQL Server 2014 Database.
So I have two versions of the same project, one for SQL Server 2016 and another one for SQL Server 2014. They have the same scripts and data flows, but for some reason, only the one made for SQL Server 2016 works. The issues resides in the ODBC Driver connector. I can preview data in both project, but for the SQL Server 2014 version, it simply won't load it. So I get 0 rows every time I run it. Sadly, I need the 2014 version for our SQL Server, since when I deploy the project with 2016 as target version, it fails.
This pretty much sum up the whole problem and I have try quite a few things. Including, changing the ODBC connector's version. It all seems it has something to do with Visual Studio, when the target version is change from 2016 to 2014. Still, I can't find a solution to this issue.
I am using a query to source data, but I also tried with the table name, but still didn't work. I am not using any function. I am running directly from Visual Studio in debug mode.
Has anyone gone through the same error? I can't find anything related.
Please, let me know if you need anything else to understand the issue.
Ok I had similar issue but it was in Source query where one of function was not behaving same between 2016 and 2014 version.
When you say 0 rows, does package failed or successful ?
Are you using a query to source data ? If yes, does it have any functions used ?
Are you running from BIDS or SQL Agent ? If Sql Agent, Check if agent job configured to run in same 32bit or 63 bit version ?
I have connected to my SQL azure server using SQL Server 2012 Management Studio and I cannot edit any of my table's schema or the data in it. When I right click on the table the options are missing. Am I doing something wrong?
Not that I am using SSMS 2012, but in 2008 R2 is generally the same. There is no GUI for neither table designer, nor "Edit top 200 records". You have to begin diving into the DDL and DML for SQL Server and give up GUIs. One way you could use GUI to some extend, especially for DDL is to use the portal provided Windows Azure SQL Database manager. You can find a link to it when you go to your database from either the new or the old portal (Manage). Other way is to use some third party tool, which I am not aware of.
Here is the link to that manager from the new portal:
Another option some people may find helpful, if you have and use Visual Studio then you can link to the server in ServerManager, connect to the database, and then design and edit data directly.
My 2008 R2 version of SSMS had the same problem. I downloaded 2016 CTP3 SSMS which has Azure support and everything is normal for the Azure Databases.
https://msdn.microsoft.com/en-us/library/mt238290.aspx
I did lose my connection history information so beware.
I have created a linked server from one SQL Server 2005 to Another 2005. When I run an update query through the SQL Server Management Studio (SSMS), it runs in under a second. If I run the query through a asp webpage it times out. I ran SQL Profiler to see if I noticed anything as well as the Activity Monitor in SSMS and all I found was that a lock was being created (Wait type LOCK_M_U), but I can't find what is locking it. Any help would be appreciated.
Wade
It could be that the user account that you run under in SSMS and from the ASP page have different permissions on the linked server, which could lead to a difference in which query plans it uses when running your update. See this answer to a more generic question about linked server performance.
The issue seems to be with the ADO activeX component, since I used ASP.Net and it worked flawlessly. Oh well.
I'm currently working on a reporting tool for a company that conducts the same survey at different clients. So the analysis and report would be the same, except for the conclusions. The ultimate goal of the project would be a tool that automatically extracts, analyses the data and creates the report. SQL Server and Visual Studio are mandatory programs.
I'm completely new to all of this except for the SQL-language. After reading up on this and asking around the usage of stored procedures seemed the best option. If I interpret correct these should be stored in SQL Server and could then be envoked in Visual Studio
However, my problem is, I can't figure out how to connect to the external ODBC-server that holds the data in SQL Server 2005. It seems to me there is no way to connect to a remote server in SQL Server 2005. On the other hand, in Visual Studio 2005 I did manage to connect and extract data from the server.
Is this the right way to achieve my goal (repeatable/automated report)? If so, what am I doing/thinking wrong? If not, please enlighten me.
Thx in advance
Another way to do this is to use bcp...you can check this article to see if there are any answers here for you. There would be no remote server connections if you are able to run the command and the local box that contains the sql server.
You might be able to set up a linked server in SQL Server 2005 to connect to your remote server/database.