Previously in Azure Data Studio, when clicking on a saved connection the application immediately opened the database specified in the connection details. But, now (in recent update?) when clicking on one of the saved connections ADS instead open just the server - where you then have to find the right database by performing a lot of scrolling (which for me is an issue, as the server contains a large number of databases). Is it possible to configure the application so that the connection leads directly to the database (as it did before) - which would save me a lot of time.
Is it possible to configure the Azure Data Studio Connection to again only open the database specified in the Connection Details?
It seems this was just a bug in the application, and has been solved in 1.10.0.
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 have a Spotfire 7.5 setup on my machine. I am using SQL server of another machine to keep the Spotfire database. Now I need to move my Spotfire database on another machine. I took the backup of my Spotfire database and restored on the SQL server of another machine.
Now I want to edit the bootstrap.xml to point my 'Spotfire' db which is now on new SQL server. But I am unable to do this as when I open the configuration tool by giving the password, it gets opened but the bootstrap tab(in which I need to edit the database server) shows disabled. And if I am directly editing the file' bootdtrap.xml' in notepad then it not works.
Can anyone help me, how to achieve this?
Also do I need to perform some other steps? Please share that as well.
I am able to move the database using the configuration tool. I have clicked on the New bootstrap file creation option and created a new one. It automatically took my last changes for other tabs i.e. Configuration tab, Administration tab etc. And my Spotfire database moved successfully and it is working.
I have an ASP.Net MVC 3 application. I have created a setup for it and installed on my webserver.
When I access the application from a web browser at "http://localhost/myapp", it works.
But when I tried from another machine, like "http://mywebserver/myapp" it's giving an error:
The model item passed into the dictionary is of type 'System.Web.Mvc.HandleErrorInfo', but this dictionary requires a model item of type myapp.Models.ErrorModel'.`
As per:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2012/08/09/error-quot-the-underlying-provider-failed-on-open-quot-in-entity-framework-application.aspx
It could be a permissions issue on the new server, etc
Solution 1:
In the existing connection string to remove the “user Instance=true” and it works.
Probable cause of the issue could be as below:
The user instance cannot attach the database because the user does not have the required permissions. The user instance executes in the context of the user who opened the connection—not the normal SQL Server service account. The user who opened the user instance connection must have write permissions on the .mdf and .ldf files that are specified in the AttachDbFilename option of the connection string.
Another common issue is when you open a database file successfully when the database is attached to the SQL Server Express instance, but fails when you try to open it from the Visual Studio IDE. This might occur because the SQL Server Express instance is running as "NT AUTHORITY\NETWORK SERVICE," while the IDE is running as windows account. Therefore, the permissions may not work.
A variation of this issue is when the user that opens the user instance connection has read permissions on the database files but does not have write permissions. If you get a message saying that the database is opened as read only, you need to change the permissions on the database file.
The other main issue with user instances occurs because SQL Server opens database files with exclusive access. This is necessary because SQL Server manages the locking of the database data in its memory. Thus, if more than one SQL Server instance has the same file open, there is the potential for data corruption. If two different user instances use the same database file, one instance must close the file before the other instance can open it. There are two common ways to close database files, as follows.
User instance databases have the Auto Close option set so that if there are no connections to a database for 8-10 minutes, the database shuts down and the file is closed. This happens automatically, but it can take a while, especially if connection pooling is enabled for your connections.
Detaching the database from the instance by calling sp_detach_db will close the file. This is the method Visual Studio uses to ensure that the database file is closed when the IDE switches between user instances. For example, you are using the IDE to design a data-enabled Web page. You press F5 to run the application. The IDE detaches the database so that ASP.NET can open the database files. If you leave the database attached to the IDE and try to run the ASP page from your browser, ASP.NET cannot open the database because the file is still in use by the IDE.
I have a spreadsheet located on a centrally hosted server. Each day, a view on my Oracle database exports a report to this excel. To access the document, various users across a number of locations can login and review the doc. However, for no obvious reason, a number of locations have started being requested for the server name. Most of the locations have the 3 fields filled in by default, but in the problem locations they have to enter the server name each time.
Does anyone have an idea how I can solve this? No configuration changes have been made recently, and I am fairly new to the system as a whole, and cannot come up with an explanation.
See attached screenshot for what I mean.
Thanks!
http://i.imgur.com/eymlE.jpg
I browsed to Admin Tools > Data Sources (ODBC) and created a File DSN. From here I was able to specify the following:
[ODBC]
DRIVER=Microsoft ODBC for Oracle
UID=xxxxxxxxx
PWD=***************
server=xxxx.xxx.xx
This meant creating new database queries inside excel, I could point to this as reference and connect externally. But more importantly for my issue, remote users could now access a server based excel, without being prompted for the server-name. I still don't know how they lost this functionality in the first place, but this solved my issue. :)
Turns out this doesn't work - I was opening a different version of the file. Still no sure how the connection box with excel is populated from!
We have some databases in a single SQL Server 2000 instance, one of them being a sandbox. My boss needs to be able to restore fresh data over the sandbox using a utility I don't have the source to. Such restores fail if anyone is connected to the sandbox.
Another app I have accessing it uses connection pooling, and also there might be people using other apps to access the sandbox that I can't control.
How can I boot everyone off the sandbox, including the pooled connections, without touching any of the other databases running on the same instance?
(I've seen solutions out there that use Management Studio 2008 (from 2008 Express), but a) I need to be able to do it from the command line or a script somehow so my boss can run it without installing Management Studio, and b) the context menu options they talked about didn't seem to be there anyway.)
I've found it on the web:
ALTER DATABASE db SET SINGLE_USER WITH ROLLBACK IMMEDIATE
create a sp that run this restores, and then restore it to regular.
(ALTER DATABASE foo SET MULTI_USER;)