Tables No Longer Appear in Connections List - Azure Data Studio 1.41, Azure SQL Server Database - azure-sql-database

Specifically for my connection to an Azure SQL Server Database after upgrading to Azure Data Studio v1.41.
When I connect into my Server/Database, and expand the Tables section from the left side menu, none of my tables appear. (Also my Views and Stored Procedures are not visible.)
They do still exist. They appear when the Manage option is selected, and I can access the data.
This means I am without access to Table Design for existing tables and other quick actions that would appear there.
Please help, it was all there when I had v1.40 installed earlier!
I have tried to log in using different accounts (server admin, Azure AD and another user account), none of which showed the tables under server connection. I have also restarted, refreshed and tried the Insider v1.42 build, all with the same outcome.

This has been fixed in the latest release of Azure Data Studio 1.41.1:
Bug fixes in 1.41.1
New Item
Details
Connection
Fixed a bug causing incorrect Azure account tenant selection when connecting to server through the Azure view.
Object Explorer
Fixed a regression which caused Object Explorer to not show database objects for Azure SQL DB Basic SLO.
I can confirmed, as well, that the regression no longer occurs:

Related

How to delete a corrupt database from azure sql

I have tried to delete a SQL database from the azure portal. It looks like it has failed part way though. The database doesn't show up under the list of SQL servers in the Azure portal. However if I login to the server through SSMS it is still there. I now can't delete the database or create a new one with that name.
I've tried deleting the database with a query and get an error saying the database doesn't exits. If I try to create it either from the Azure portal or SSMS it gets an error saying it already exists.
I had a similar problem once, with SSL settings, where it would return that it is linked to the app even tho it wasn't, hence I was not able to delete it. After a couple of weeks of back and forward with the support, we removed it through azure resource explorer.
How to:
Once you are logged in, set read/write
In serach box find your resource
Click actions (POST/DELETE) // these should be available now since you have set read/write
Click Delete
Hopefully, this would help anyone who has any corrupted resources in Azure.

SSDT tabular model data loading / ID error

I am new to Visual studio, and I am in the process of building my first tabular model in Visual studio, have been using powerBI for a year or so.
I have an Azure SQL database setup, with data tables. I can access the database fine through SSMS, Power BI etc fine. I can also access the data fine when using the data model on the workspace server rather than an integrated workspace with VS.
When using the model in integrated workspace mode, when I use "Getting data" through power query in my tabular project in visual studio, I can login into the database fine, I can preview the various data tables and open them in power query / transform etc. However, when I try to import the data - it can get past stage one of the processing - and I get the following error
“Failed to save modifications to the server. Error returned: 'OLE DB
or ODBC error: We're sorry, an error occurred during evaluation..”
Which leaves me with a table with headers for the columns - but no actual rows of data.
When I revert the data model back to workspace server (i.e. integrated workspace set to false) - I can upload / refresh the data.
So I was happily building my model on the workspace server - HOWEVER - when I came to adding roles and user to those roles - I cannot use the workspace server - or I get an ID error - as I am using an Azure AD. - see below
An error occurred while opening the model on the workspace database.
Reason: Failed to save modifications to the server. Error returned:
'ID cannot be specified for Azure Analysis Services role member:
'member#domain'.
This ID error is fixed when I use an integrated workspace - as recommended - but then I can't load the data in.
So I am stuck between:
integrated workspace with no data
workspace server - without the ability to add AzureAD IDs
Any help with either of the issues would be much appreciated
Thanks,
Laurence
I work with VS 2017 and experience exactly the same issue. I use SSDT compability level 1400.
I appears that simply run Visual Studio as administrator solves the issue with Integrated server.
Accidentally found this solution, I saw earlier some people had solved inability to connect to workspace server without admin rights.

editing database for azure mobile services using Azure SQL management portal

I am developing windows 8.1 application and using AZURE mobile services to communicate with. I need have some data in azure mobile services database which will be dumped to application when it's installed on any device. So I tried to add records in the database using azure management portal SQL_database but seems like I cant do that it gives me error
"Cannot add a row in the Table Data Editor because one or more columns are required but their SQL types are not supported in Table Data Editor. Use the Transact-SQL Editor to add a row."
This is probably due to the --version column that has binary type . So I tried deleting this column but then there was following error
"The target table 'ShoppingListPro.Category' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause."
I googled this issue and what I found is Link .
Please guide me if it is possible to edit the azure mobile service data base using management portal that will make my life bit easy , other wise I need to write an app to feed data to azure mobile database.
Thanks
You can connect to the DB from SSMS. Just check what your connection string is below 'Connect to your database':

Login Failed for user [sql server user]

I am new to SSRS and have deployed several reports. When I force windows authentication, everything works fine, but when I do this:
I am getting this error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DataSet1'.
(rsErrorExecutingCommand) Login failed for user 'DWH_Reporting_User'.
I've configured the DWH_Reporting_User like this:
here are the details on DWH_Reporting_User for the ReportServer database:
here is the security on the server:
when i try to set security for that specific folder:
i am getting this error msg:
is there something obviously wrong with the way I've configured things?
The answer to this question was a series of comments. I went ahead and put it in the chat as well as an answer.
Go to the security of the server not the database and map the user to that database.
Can you recycle the application pool on the server where reporting services is running? Or reboot the IIS server if possible.
Another thing that comes to mind, when you launch this report it goes into the report server "Portal". Does this user have access to the actual report to view it? Click the details section of this "Portal" and assign this user as a content manager role.
DWH_REPORTING_USER is this an admin account on your domain?
Local admin on the server, so did you grant \COMPUTER_NAME\DWH_Reporting_User rights as a content manager in the roles section? Why dont you use a domain admin account?
So how do you access the actual report - that is your issue.
Do me a favor aprem, write up a stored procedure or sql query in the first tab of reporting services and run it using that user. Meaning in the shared data source it should be using this user DWH_Reporting_user. Test the connection then write a small sql statement to retrieve some data. Run the SQL script from within RS do you see any data?
#Aprem look at the three tabs at the top of rs, its the first tab to define datasets, this is where you can create an SQL query (and run it using the red exclamation mark). – JonH 20 mins ago
i defined a new dataset as "select top 1000 * from mytable", i rebuilt the project, deployed it, and now what do id o? – Артём Царионов 16 mins ago
In the "Shared Datasets" you have a dataset right? Double click on it and go to "Query Designer" it is a button on this form. Click on it and "Execute" the query (red exclamation mark). You dont need to deploy it right now, just do it on a test machine.ago
You specify the user in the datasource section "Shared Data Sources", that account is the account being used to "pull" the data. You really need to experiement with RS some more or read some material on it. This is as basic as it gets.
*Ok aprem do you understand your issue now, the user you are using to get the data has no issues, in addition, it is functioning correctly. Now you have to view the report. To view the report is to view the webpage, and to view a web page means you need to either use "Anon" access or windows authentication. So you need a domain or local WINDOWS account to view the report. This account needs to be setup on the RS portal as a content manager role. *
You are dealing with two beasts, one is the database (db server) and one is IIS (web server) each serve a specific purpose. The database serves to allow you to pull data while the web server hosts the pages.
The reportserver database is very important, it keeps a listing of all your reports and the meta data associated with your reports in the database. It also stores job ids and subscriptions associated with your reports. Basically it is the backend database for all reporting services stuff like reports, datasets, and datasources. Think of it this way when you create a new "Report Project" you are allowed to create reports, datasets, and datasources. Without the reportserver database how would the system remember your datasets, datasources, and report names? It is the heart of rs.
your data set is not used to connect to the reporting services databse, it is used to connect to the database you are getting the data to display on your report.
Does that user exist on the database the report is accessing?

Permissions Problems Prevent Database Access

Recently I inherited a database from another programmer (created / stored with SQL Management Studio 2008), and I am having massive difficulties accessing, modifying, or even viewing the previously created databases.
Specifically, when I try to load one of the databases in SQL Management Studio I get the following error message:
"The database [database name] is not
accessible. (Object Explorer)"
I am connecting to the SQL server with windows authentication.
Anyway, is this a permissions issue left over from the last dev? (he's unavailable, unfortunately) And is there an easy work-around short of completely reinstalling SQL Management Studio?
Edit: Update:
Upon trying to access User Mapping, as suggested below, I got the following error message:
"One or more databases are inaccessible and will not be displayed in list."
Unfortunately, none of the databases I am trying to access appeared in the list, so I assume they are still inaccessible.
It could very well be a permissions problem. If you open Object Explorer in SQL Server Management Studio and expand the Security node (the one under the server instance, not the Security tab under the individual databases) and then expand the Logins node you'll see the list of logins that have been created on the server. Have a look at the properties of each of those and check out the User Mapping information. You'll be able to see which logins are mapped to which databases. It's possible the previous programmer only granted access to the database to certain logins. If you find a login that's mapped to the database you want, try changing the password of the login and then connecting to the database with that login and password. NOTE: be careful when changing the password as it may affect production applications that are using that login and password!
This message:
"One or more databases are inaccessible and will not be displayed in list."
Means that the user you are using right now cannot access to that db. If you can enter with a user that does have access and from that user change your actual user's rights through User Mapping, then you will see it.
You need a dba (or someone with dba equivalent access) to give you rights to the database.