When I first started using plsql developer, it would allow each window to have a separate connection to a different database.
At the time I found that annoying, so I turned it off.
But now I need to compare objects across databases - ie : how is the view on dev4 different than the same view on dev5.
I can't find the setting / preference I changed.
Help.
Ok the quick answer to this is Configure -> Preferences -> Connection ( under Oracle grouping) -> uncheck/check 'Allow Multiple Connections'.
With this checked, you have an option at the bottom of every SQL window to choose a separate connection to a database ( a downward facing triangle). You ALSO have the 'Connect as Main' option when you right click on a db connection, which will connect all subsequent SQL windows to that db.
With this unchecked, the 'Connect' option goes away - leaving you with only 'Connect as Main', and the option at the bottom of each SQL window goes away.
FYI
Related
So we have a writable database that a lot of our product / data people use. This database has recently been migrated to Managed Instance.
We're working on getting them connected to be able to write/update DB records via Access, a functionality they've had before.
Currently, we're looking at starting them from scratch.
We can't seem to find a way to create a connection that allows for updating or changing records. The connection we're setting up allows them to insert / create new records, but the second that create goes through, even the newly created record can't be edited. We get a standard MSAccess writelock error. This is the case on EVERY table we open. Even ones that are essentially never touched.
Here's how we're connecting:
Network: The machines running msAccess are on our "main office" connection, which is peered with a vnet to the Sql Managed Instanfce. We CAN connect to the sql managed instance via ssms from this place, so it shouldn't be a networking issue (we can also insert records, so same thing)
Permissions: I've made sure that I have full sysadmin permissions via our az-sqlprod01-admin AAD group. I can do this same action in SSMS
Method:
Access > External Data > Linked Table Manager > Add:
Next Screen is Table Import, So that once that's finished we have the full table import list. We import those tables without issue.
Once there, I can bring up any table, try to edit anything, and it gives me the write-lock error at the top of this screen.
My Need: is there a way to connect MSAccess to a SQL Managed Instance without getting write-locks 100% of the time?
I have recently taken a job that involves using an Access database to find information. The database in question was built by a developer who left before it was completed. He also didn't leave any documentation behind.
The database uses queries, forms, and VBA. Some of the queries are no longer valid since the source data has a different format than what it was when the database was developed. I know SQL and some basic VBA so I'm trying to modify the SQL; however, I cannot view the SQL behind the queries. I can't open it in Design View or SQL View. I can't even right-click on any object. Not only that but when I open an object, I can't right click on the top tab to close it. There's a red x that populates on the top-right that I have to use. I've tried holding shift when opening the DB, but it still happens. I also went to: menu option Tools -> Startup -> to see if 'Allow Default ShortCut Menus' was unchecked; however, it wasn't. I've checked other forums but haven't been able to find a solution. I think it may be in the VBA somewhere but there are tons of modules and each module has a boat-load of sub procedures in it. I have no idea what else it could be. Any and all insight would be greatly appreciated!
#Andre and #Comintern both provided correct answers. The culprit was in the Auto Exec function and it had a loop that went through each CommandBar and set Enabled = False.
I have an issue. I have an Access Project (currently in access 2007), and the project connection properties are set to point to a hosted SQL database on our network. Unfortunately we had to move the databasem and now I have to change the connection properties as well.
However, when I open the adp file, the first thing it does is try to connect to the old database. I never get prompted or anything, the screen just sits there, and the title bar eventually indicates "not responding".
Anyone know how I can get to the connection properties, since Access never gives me a chance to do so?
Have you tried keeping the shift key held down while the database is opening to prevent any start-up forms or macros from running? If that does not help, you can change all the connections from VBScript.
This is regarding SQL server 2008 management studio..
I connect to different environment DB and every time I launch the Sql management console, I have to sign up every time to get those connections back in object explorer. Is there a way I could persist the connection so I don't have to login every time to different environments?
You can register the servers, type CTRL + ALT + G, add the server you want and next time, go to registered servers, right click the one you want and select new query
As #SQLMenace said, you can register the servers.
Look at View -> Registered Servers option.
I often have multiple databases open in SQL Server 2008. Often they are prod, dev, and dr. It is annoying because each window says something generic like SQLQuery1.sql... (sa(200))*. So I have to hover over the tab and make sure I am in the correct window.
Is there a way to color code each window, or in some way to make it instantly knowable which database or server I am in?
Jonathan
Yes, you can color-code connections in SQL 2008, by modified the properties of the registered server. There is a "Use Custom Color" option on the Connection Properties tab.
See this cool tutorial video by the Midnight DBA
I'm not sure about changing the colors, but I got tired of the small tab truncating the window name. As a result I run them as windows, so the entire DB name shows in the window's frame.
I have 2005 (shouldn't be that different than 2008) and this is where I made the change:
tools - options:
environment
general
MDI Environment