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.
Related
I am using SSMS 17 and are trying to create a temporal table in SQL Azure but for some reason the option Tables -> New -> Temporal Table is disabled.
I have created a basic Azure database which currently has no tables.
Does anybody know how to enable this feature or what I may be doing wrong?
The grayed out option in Object Explorer that you are seeing was an unintentional limitation in SSMS, which was probably true in the early days of Azure SQLDB.
The issue has been fixed quite some time ago, but it was never (and never will) be ported back to SSMS 17.x. Could you install the latest SSMS 18.x (currently SSMS 18.2) and give it a try?
If you are still having issues, please reach out to us on UserVoice (https://aka.ms/sqlfeedback).
In my case, that option only appears if you connect to the SQL on Azure VM using "sa" account ( sql 2017 - 14.0.2072.2 ) , but not to Azure SQLDB ( 12.0.2000.8 ). So it could be a version issue although SQLDB supposedly is SQL 2016 plus, and this temporal table was there since 2016 ) Please try T-SQL as explained in the documentation snippet ( https://learn.microsoft.com/en-us/sql/relational-databases/tables/creating-a-system-versioned-temporal-table?view=sql-server-2017#creating-a-temporal-table-with-a-user-defined-history-table ) that works.
You can use below screen shot also
just right click on table and follow below screen shot
On SQL Server Management Studio, make a right click to Tables --> Select New --> Choose "System-Versioned Table".
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 ?
Is anybody else having an issue when they right click on an SP, and not seeing the option to execute the SP? Only option that I have is to script as execute. I am running SQL Server 2016 express.
Too long for comment!
I suggest that you back up the database now. Full and transaction.
Then check the Compatibility level. Change it back to your previous version of SQL server. Take another back up (to a new file!!).
Now did you upgrade the whole of SQL server or just SSMS? You could just install another earlier version of SSMS and leave the existing server in place and running, test to see if the functionality is all still there with the new (older) SSMS and the old (Ok most recently installed SQL Server).
Microsoft are doing monthly releases of SSMS so it is changing fast - which can mean bugs, but the server should be more stable, so the problem could just be a SSMS issue and your database could be fine.
New patch came out. It works wonderfully now. My issue was resolved. Thanks for the help...
The background to my problem is based on distributed computing. I want to have a database with some numbers in them and then a number of computers go through each row calculating another number (a little bit of an over simplification).
The problems I'm having are routed in my poor understanding of SQL servers (I think). I've got Microsoft SQL server 2012 (and 2008) installed on this machine and I've somehow managed to make a server for this task but then the problems arise.
I can't add a table to the server (I'm trying to do this in VS2010). When I expand the server and right click on tables and select add new table i get the following error:
"The server version is not supported. Only servers up to Microsoft SQL Server 2008 are supported."
That stops me making a table and from there I can't move on. I've downloaded and installed the VS2010 SP1 (and re-installed it again when it didn't fix the problem) as I found this suggested for similar issues.
Any help on this would be greatly appreciated. I've read around but nothing seems to work, people suggest using "SQL Management Studio" but I don't seem to have this installed!
Also, I haven't gotten to this step yet, but if this gets fixed any advice/links on how to access the database from a different machine (over the same local network) would be greatly appreciated!
Many thanks,
Fraser
R Harvey gave you the pointer to SSMS - that's the ideal tool to use.
As for other computers accessing your local database - the name of your computer (where MSSQL is installed) is the name of the server in your connection string.
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