I'm trying to use Azure Data Studio to connect to a SQL Server database.
I am able to connect to the database and view the list of objects (tables, stored procedures, etc.).
When I click to expand the "Columns" group inside a table, I get the following error from Azure Data Studio:
unknown property IsColumnSet
I am able to expand the Keys, Constraints, Triggers, Indexes, etc. but I can't expand the Columns.
I am able to right-click and query the table to see all the columns, but I'd like to know what to do to get the columns list expanded in the server side bar tree.
I tried uninstalling and reinstalling Azure Data Studio. No luck.
FWIW, while this error persists in the UI when drilling down a table to view the columns, you can still get this information via SQL like so:
select * from INFORMATION_SCHEMA.COLUMNS where TABLE_NAME = 'someTable';
Verified this works with ADS on Mac, connected to SQL Server 2005.
Apparently Azure Data Services "only officially supports SQL Server 2014+" and this problem would seem to be due to lack of support for older servers.
https://github.com/Microsoft/azuredatastudio/issues/3774
So although they might improve the error message to indicate lack of support, I think otherwise we're out of luck. A long-overdue server upgrade is in order methinks...
Related
I'm writing a webtest in Visual Studio 2015. The webtest I currently have allows me to run a static test.
I would like to spice things up and therefore add more realistic data. The data I want to use is stored in an Oracle Database 12c.
So I'm trying to add a new Data Source to the webtest. I enter the TNSName, Username and Password for which I would like to connect and test the connection. The connection can be established, but the list with tables I can choose from is empty.
Connecting to the same Database using the "Server Explorer" in Visual Studio 2015 works. And using this method I do get the full list of Tables contained in that Database. I can even query any of the tables.
So how can I fix my webtest to have access to a specific database table (row)?
If you can connect to the DB but you don't see the needed tables it should be a permission issue.
Do you use same credentials from "VS->Server Explorer" to connect to the DB?
If this is not the case, do you have more than one Oracle clients installed in your system? If yes, then most probably, the DataSource control uses the wrong client and the "Server Explorer" the correct one.
Are you using synonyms as proxies for your tables (e.g. for permission reasons)? synonyms will not show up when querying the list of tables that the user can access. They need be queried separately. When only the available tables are queried but not the vendor specific aliases this might lead to an empty list.
You need to install ODAC for Visual Studio 2015 to view the database tables. Here is the link for it.
http://www.oracle.com/technetwork/topics/dotnet/downloads/odacmsidownload-2745497.html
i try to use Datagrip as my primary sql server query tools, bit i meet a problem that i can not move forward.
When i setup the project data source, i have to choose a Database, otherwise it will goto the default tempdb, how i can work like sql server management studio, that i can see all database list.
i have tried both jTds and Microsoft drivers, both not works.
or can i choose multi-database? i do not want to create one data source for one database.
if i connect to mysql, it works like expected.
tks
It is possible to connect without specifying the database. Just leave this field blank. After entering other settings (host, port, user, password), go to Schemas tab in Data Source properties and select all the Databases and schemas you want to work with. Then invoke Synchronize action for this Data Source in Database tool window.
DataGrip 2016.2 EAP claims to have support for showing multiple databases. See https://blog.jetbrains.com/datagrip/ and find for "Database View". Unfortunately, as of the date I'm writing this, it doesn't seem to work at all.
Unfortunately, Andrey's suggestion did not work for me.
This came up once before: Use DataContext.CreateDatabase in SQL Azure
The answer accepted was "maybe it's not possible". Didn't seem like a full answer.
I have a set of classes fully defined and I am wanting to create a database on Azure for this. It's not working because the USE statement does not work: http://msdn.microsoft.com/en-us/library/azure/ee336288.aspx
So, the database gets created as blank, and internally Linq generates a USE statement to move to that database and start adding tables. This fails and it throws an exception.
So how can I create my database? Can I use Linq to add tables to an existing database? Can I enable USE on Azure somehow? Seems ridiculous this does not work.
After messing around for a while on this, I ended up creating the database against a local SQL Server instance. Then used SQL Server Management Studio -> Tasks -> Script Database, and turned on the export type to be Microsoft Azure. Then I had the script file needed to run on the Azure server. I'll leave the question open for a day or two because I am curious if this can work with Azure directly somehow. If I don't hear anything, I will close it.
The USE statement does not switch between databases in Azure SQL Database. You will have to connect to the database to create a table on that database.
Regards
Dhruv
I have installed SQL Server 2012 Express Edition Advanced Services which states that it includes Full-text indexing. Here is a link that states this:
http://msdn.microsoft.com/en-us/library/cc645993.aspx
I have confirmed that Full-text service is running, however when I try to create a full-text catalog, it fails. I get the message "Full-text is not supported on this edition of SQL Server. (Microsoft.SqlServer.Smo)"
Anyone have any ideas?
You can't do this through the wizard, because there are a couple of bugs. Even if I chose not to track changes and not to populate the index when it was finished, I still got an error about SQL Agent:
Cannot load 'Select or Create Population Schedules' Full-Text Wizard
form. SQL Server Agent is not supported on this edition of SQL Server.
(Microsoft.SqlServer.Smo)
In spite of the error, I was able to proceed, but at a further step I finally did receive the error you did. However I had no problem doing the following in DDL:
CREATE TABLE dbo.x
(
x NVARCHAR(255) NOT NULL CONSTRAINT uq_x UNIQUE(x)
);
GO
CREATE FULLTEXT CATALOG x_catalog;
GO
CREATE FULLTEXT INDEX
ON dbo.x(x LANGUAGE 1033)
KEY INDEX uq_x ON x_catalog;
GO
This shows that Express certainly does support Full-Text, it's just the UI that is a little confused. I suspect it doesn't know how to tell which version of Express you actually have running.
So in the short term I would recommend using DDL instead of the UI. In fact, since the UI only seems to trip on creating the catalog, you can use the UI to create the indexes if you first create the catalog via DDL...
CREATE FULLTEXT CATALOG x_catalog;
...and then pick that catalog when stepping through the wizard, instead of creating a new one. Of course you'll also have to ignore the exception regarding SQL Server Agent, but it does not stop the wizard, you can just click OK and ignore it.
I've filed a Connect item against Management Studio, please vote for it and hopefully this will be corrected:
Management Studio does not fully manage Full-Text in SQL Server Express
I don't know if that item has been addressed or if it made it over to the new feedback system. I started to search for it but good luck.
I'm working on a legacy application using VB6 and Classic ASP. We're using disconnected ADO recordsets to pass data back and forth. Normally this works. But what has started happening recently is for any inner/outer join, ADO is including these in the available records to choose from. So when were specifying a column to update (in the cases it errors out, the primary key column), it in turns updates the wrong column (with the same name). I know it's normal for ADO to pull the primary keys for any joined tables, but the default for this is for ADO to hide them. In our case ADO isn't hiding them.
What I've narrowed it down to is the SQL Native Client driver is not working correctly. I can go back to the SQL Server driver (SQL 2000) and it works great, but as soon as I switch back to SQL Native Client, it exhibits the behavior above. I've checked the properties on the open connection and the properties of the recordsets themselves, they match in every instance except one (the count of how many hidden columns there are which makes sense, as SQL Native isn't hiding them).
I've tried everything from deleting the MSADC folder from IIS and re-adding it, I've uninstalled SQL Native and reinstalled it (and subsequently upgraded it to the newest version). I've recreated the ODBC connection several times as well in the process of troubleshooting it. At this point I'm at a loss.
Also one thing to add, it appears SQL Native Client works fine on our other servers and no one else is having this issue. Anyone might have an idea of what could be happening? Thanks!
Edit : Example of what's happening (this occurs on for any query (stored procedures if it matters) and with >= 1 joins of any kind)
select temp_id, temp_value on temp_test
inner join another_table on another_table.temp_id = temp_test.temp_id
inner join yet_another_table on yet_another_table.another_id = another_table.another_id
this'll produce in the ado recordset :
SQL Native Client
(0) temp_id
(1) temp_value
(2) temp_id (primary key of another_table)
(3) another_id (primary key of yet another_table)
SQL Server driver
(0) temp_id
(1) temp_value
SQL Server 2005 will show it as it should be as : temp_id, temp_value
this occurs on for any query (stored procedures if it matters)
It's not the issue described here is it? :
If a change in the connection string changes the behavior, I would suppose that you have two different schemas, and then two versions of the same stored procedure; and the one that is executed with SQL Nativ Client is the incorrect one.
I have exactly the same scenario, and have had it for over a year on our servers and servers at our client. I never found a solution and as a result we simply have to use the SQL Server driver, which is a shame as SQL Native seems to connect significantly faster.
It's nothing to do with different schemas or different versions of the same stored proceedure as suggested above. I use a file dsn and simply changing the driver name changes the behaviour to/from that mentioned above. It seems to happen to all views (probably stored proceedures too as indicated)
If anyone does find a solution I'd be keen to hear about it.
Warwick