I've run into an instance where I created a new query window, right-clicked to connect to a server and found the following options:
Come to find out the reason this happened was because I created the new query window from a multi-instanced registered server such as below:
Just make sure to create your new query window from a single instanced registered server.
Related
I have never faced such a problem. On the remote server outside our domain was created a new SSRS server. Everything seems to working fine, I could connect to ReportServer via https also to Reports.
Then I opened my Report Builder write connection there and it was also properly connected.
But after I tried creating new Data Source the problem begins.
In build connection function its all OK.
After that in Data Source Properties when I tried to test connection it gives me this error.
OKay I still decided to try create something in Dataset with simple query and it connect to SQL server to specified database and also I can see a fields in field list !
But after all that hope I'm still unable to run any report here. So can anyone please help me or guide me to any solution ? Thanks !
In Visual Studio's Server Explorer, I right-clicked Data Connections and selected Create New SQL Server Database.
In the same-named dialog that is then invoked, I entered a ServerName, a New Database Name, accepted the default of Windows authorization, but get this:
I'm pretty sure I installed MS SQL Server when I installed VS (2019). What is causing this error and what do I need to do to fix it?
Am I not allowed to create a Server Name and must use a specific one? If so, what?
UPDATE
I'm also getting problems now with MySql. I recently created MySql Databases (they are displaying on the left -- "movies" and "statesdb" and I've got connections to them, as indicated by the green connector icon), but now trying to create a new Database also fails (after I hit the "Test Connection" button):
UPDATE 2
I still get the same exact err msg after installing SQL Server Express.
And that's even though I do have a bunch of SQLExpress services running now (the only non-new one is the last one):
Do I need to use SQL Server Authentication instead of Windows?
To see if you have sql server installed and it’s running, you can open services.msc and look for SQL Server. The name in between the brackets is the instance name, I.e.: SQLEXPRESS.
To connect to a localhost instance you simply do .\instancename or for SQLEXPRESS: .\SQLEXPRESS
I successfully installed MySQL server (I can connect to it manually through the MySQL shell). When I try to establish a connection through MySQL Workbench, the test connection goes through as well. But when I try to view the server's info or interact with the server, an error message pops up that says, "Current profile has no WMI enabled." I have searched for a solution to this problem, and found a few threads like this one: https://www.quora.com/MySQL-Workbench-How-can-I-solve-the-Current-Profile-Has-no-WMI-enable-error-message. However, I just can't find the 'Manage Server Instances' dialog or button anywhere. I am running workbench version 6.3. If anyone has run into this problem then I would appreciate a workaround.
It's unusual that you get that error again. I haven't heard since years of such a problem. Anyway, the solution is still to configure the connection properly. That "configure server instances" link is very old (from WB 5.x). Instead look for the connection editor (titled: Manage Server Connections). You can open the dialog either via the main menu or the small wrench button on the homescreen:
I have 3 connections configured in the MySQL Workbench and lately as soon as I run the workbench I get this "Open SQL Script" dialog.
Steps:
1) Right click MySQL Notifier (1.1.4)
2) Click on "SQL Editor..."
3) Expected: Workbench Home (1 tab open)
Actual result: the tab for the 3rd connection is automatically open and on top of that I get this "Open SQL Script" dialog.
Additionally I would love to be able to change the default connection that opens, but I could not find any of this anywhere.
Help is appreciated! Thanks,
Simon
Take a closer look where you are clicking in MySQL Notifier. For each instance MySQL Workbench (and hence MySQL Notifier) found there's a separate menu entry which you can use to open the application for. The notifier is just trying to help you to get quicker to some standard work. If you just want to open MySQL Workbench then don't use the notifier. Create a shortcut for it and put in a good place instead.
Update
In order to clarify look at this image:
As you can see there's more than one "SQL Editor..." entry (one for each connection in MySQL Workbench). But even if you only have one connection, the menu entry "SQL Editor..." is meant to open ... well... the SQL editor. In addition it asks for an SQL file you may want to open. That's just how it is designed. If you don't want that click Cancel. There's no dedicated menu entry to just open MySQL Workbench with the home screen. If you want that better place a shortcut to the application on your desktop.
Regarding a "default connection": there's no such thing as a default connection. You can pass in a connection name on the command line if you want to open a specific connection. You can use the shortcut you can create and add the parameter "-query " to it.
Normally when I want to change the connection for a Query Editor Window in SQL Server Management Studio, I can select a new connection from the menus at the top - Query > Connection > Change Connection.
However, when I am working on cubes with an analysis services connection - and then open a saved SQL script (such as the underlying SQL view) the Available Databases combobox is blank, and the "Change Connection" and other 3 options in that menu (Connect, Disconnect, Disconnect all queries) are all greyed out.
The only workaround I have found to be able to run the saved SQL script, is to open a "New Query" from the SQL Database I want to access in the Object Explorer, and either copy my script into it, or reopen the script - which now opens as normal, with the new query's database.
It seems to be taking the last Query Editor Window's database connection as the default connection for any new queries - and when your last "query" is browsing a cube then it breaks? Does anyone have a fix to un-grey out the "Change Connection" option properly?
I am using SQL Server 2008 R2, and opening the saved SQL script by the File > Open > File menu
Luckily in SSMS 2008-R2, 2012 There is a change connection function. Placed just before the DB dropdown.
Or via menu Query>Connection>Change Connection.
Well, SSMS does not allow to manage connections easily (particulary, when you want to switch connections between servers). I have developed add-in for SSMS: SSMSBoost - it adds additional combobox to the toolbar with your favorite connections (you have to define them). In your case, after opening the script you will have to pick the right connection from this new combobox and it will be established. Addin is currently free.