In Oracle SQL Developer Modeler I have an existing model. When I create a new table, I can do it, add new columns and so on. But I cannot alter existing tables, they are all locked. I see a icon on top left corner that they are locked. How to unlock it?
screenshot with locked and unlocked table
Related
When clicked the 'View -> SQL History' in the Oracle SQL Developer, there will be a small flat window popped up and placed at the end of the whole window. And in this flat window, all my recent queries that have been executed are displayed there. How can I delete these SQL history records in this flat window? Thanks in advance.
I have just observed that there is a clear history button available which can be used to either delete specific query by selecting one or all by selecting all using ctrl+A.
P.S. I didn't try to delete or validate it as I want to keep my history.
Each "history query" is saved as an XML file. It is located (on MS Windows) in a (hidden - set the Explorer to view hidden files!) folder whose name is e.g.
C:\Users\littlefoot\AppData\Roaming\SQL Developer\SqlHistory
Go in there and delete its contents.
Is it possible to add new tables to an existing MS Access database from the Server Explorer window in Visual Studio?
I've seen videos on how to do exactly that with a SQL server database connection. You just right-click the table folder in the tree of database object types below the Database Connection item in server explorer. The choices on the context menu include "Add a New Table." Once you fill out all the details of the table columns in the associated VS table definition tab, you click something and run the auto-generated CREATE TABLE command against the database, and the table is created.
But when I try that with my MS Access database (connection successful, all the tables show up, etc.), the right-click menu does not show Add a New Table. I'm thinking that there is no way to create tables in an Access database through Visual Studio wizards or designers. Maybe all the database creation, structure, field definitions, and such things must be created through the MS Access program itself.
Am I missing something obvious? Is there a way to do it through VS? (I hope; it would be nice to create the tables through VS). Thank you.
After spending a long time on it, I conclude that there is no way to create new tables in an MS Access database by using Visual Studio designers and tools. Maybe this will help someone one day.
I am working on an application with a project that uses Sql Schema Compare to update the database.
So to update the database I right click the project and select Schema Compare and I see the changes to be made, but the button to update the database is disabled (which I have circled in the image below). How do I fix this?
I believe you might need to resolve all the errors displayed in the Error List first before the update button is enabled.
Hope this helps
How do I update a Linq to SQL .dbml file?
There are three ways to keep the model in sync.
Delete the modified tables from the designer, and drag them back onto the designer surface from the Database Explorer. I have found that, for this to work reliably, you have to:
a. Refresh the database schema in the Database Explorer (right-click, refresh)
b. Save the designer after deleting the tables
c. Save again after dragging the tables back.
Note though that if you have modified any properties (for instance, turning off the child property of an association), this will obviously lose those modifications — you'll have to make them again.
Use SQLMetal to regenerate the schema from your database. I have seen a number of blog posts that show how to script this.
Make changes directly in the Properties pane of the DBML. This works for simple changes, like allowing nulls on a field.
The DBML designer is not installed by default in Visual Studio 2015, 2017 or 2019. You will have to close VS, start the VS installer and modify your installation. The LINQ to SQL tools is the feature you must install. For VS 2017/2019, you can find it under Individual Components > Code Tools.
To update a table in your .dbml-diagram with, for example, added columns, do this:
Update your SQL Server Explorer window.
Drag the "new" version of your table into the .dbml-diagram (report1 in the picture below).
Mark the added columns in the new version of the table, press Ctrl+C to copy the added columns.
Click the "old" version of your table and press Ctrl+V to paste the added columns into the already present version of the table.
Delete the dragged table from step 2 and save the .dbml file.
You could also check out the PLINQO set of code generation templates, based on CodeSmith, which allow you to do a lot of neat things for and with Linq-to-SQL:
generate one file per class (instead of a single, huge file)
update your model as needed
many more features
Check out the PLINQO site at http://www.plinqo.com and have a look at the intro videos.
The second tool I know of are the Huagati DBML/EDMX tools, which allow update of DBML (Linq-to-SQL) and EDMX (Entity Framework) mapping files, and more (like naming conventions etc.).
Marc
We use a custom written T4 template that dynamically queries the information_schema model for each table in all of our .DBML files, and then overwrites parts of the .DBML file with fresh schema info from the database. I highly recommend implementing a solution like this - it has saved me oodles of time, and unlike deleting and re-adding your tables to your model you get to keep your associations. With this solution, you'll get compile-time errors when your schema changes. You want to make sure that you're using a version control system though, because diffing is really handy. This is a great solution that works well if you're developing with a DB schema first approach. Of course, I can't share my company's code so you're on your own for writing this yourself. But if you know some Linq-to-XML and can go to school on this project, you can get to where you want to be.
I would recommend using the visual designer built into VS2008, as updating the dbml also updates the code that is generated for you. Modifying the dbml outside of the visual designer would result in the underlying code being out of sync.
There is a nuance to updating tables then updating the DBML... Foreign key relationships are not immediately always brought over if changes are made to existing tables. The work around is to do a build of the project and then re-add the tables again. I reported this to MS and its being fixed for VS2010.
DBML display does not show new foreign key constraints
Note that the instructions given in the main answer are not clear. To update the table
Open up the dbml design surface
Select all tables with Right->Click->Select All or CTRLa
CTRLx (Cut)
CTRLv (Paste)
Save and rebuild solution.
In the case of stored procedure update, you should delete it from the .dbml file and reinsert it again. But if the stored procedure have two paths (ex: if something; display some columns; else display some other columns), make sure the two paths have the same columns aliases!!! Otherwise only the first path columns will exist.
Here is the complete step-by-step method that worked for me in order to update the LINQ to SQL dbml and associated files to include a new column that I added to one of the database tables.
You need to make the changes to your design surface as suggested by other above; however, you need to do some extra steps. These are the complete steps:
Drag your updated table from Server Explorer onto the design surface
Copy the new column from this "new" table to the "old" table (see M463 answer for details on this step)
Delete the "new" table that you just dragged over
Click and highlight the stored procedure, then delete it
Drag the new stored procedure and drop into place.
Delete the .designer.vb file in the code-behind of the .dbml
(if you do not delete this, your code-behind containing the schema will
not update even if you rebuild and the new table field will not be included)
Clean and Rebuild the solution (this will rebuild the .designer.vb file to include all the new changes!).
Use Visual Studio 2019 open DBML files in graphic designer to update DBML files.
when not working:https://developercommunity.visualstudio.com/t/dbml-files-not-opening-in-graphic-designer-in-vs-2/1659675
Just for the record
So I have my edmx made.
Then I change my database a little bit, changing a column to from being a NOT NULL to allowing NULL.
I go into my edmx, right click and choose "Update Model from Database"
Now I go into my program and it hasnt actually updated... I can't put a null in the column. What do I have to do to update the edmx properly? Thank you.
Update/delete from the EDMX is not always functional. If the model doesn't get updated on clicking Update Model from Database let's say when you have updated a view/table in the DB, do the following:
1) Delete the view/table from the model diagram
2) Switch the EDMX to xml view (right click the edmx file and select "Open With")
3) Search and delete the xml entity elements
4) Switch back to EDMX view
5) Click Update Model from Database
This should reflect any kind of change you made to the DB to your EDMX. It's cumbersome, but works flawlessly.
In an ideal world, i would expect the Update Model from Database to sync the changes from DB to EDMX. But, it doesn't work most of the time.
What I have successfully done is this (VB.Net).
make updates to the database as desired/ required
Choose "Update from database" in the EDMX model, the graphical model will correctly show the new structure/tables
Expand the project so that it shows all related files
The two files with the "tt" extension are the ones that matter: first take the one WITHOUT the .Context. before the tt extension. right click on it and choose Run Custom Tool:
Do the same for the .tt file with the .Context. in its name. All of your code and logical model classes will be updated.
Choosing the Update Model from Database is the best method for updating your EDMX. There are certain properties that don't get updated on the Conceptual layer.
Ensure that your Store layer has been updated by viewing it in the Model Viewer toolbox. If the Store has properly been updated then you're okay, and your database is in sync. If so, go into the visual designer, click the field, go to properties, and update the NotNull property on the Conceptual side.
Yes, It doesn't work most of the time :-/
The "best method" (because it works systematically) is to delete the EDMX file and generate it again.
But don't forget to remove the connection string in App.config (else VS2008 wizzard will add a suffix to the default entity name), and clear the cache.
I hope that these tools will work better in a next release, because it decreases the productivity dramatically...
THIS IS THE QUICKEST EASIEST WAY:
Delete the view/table from the .edmx diagram.
NOW use the Update Model from Database to add the table back in.
1.Build the project after updating EDMX file.
2.Right click your .tt file in solution explorer.
3.Select "Run Custom Tool" option.
This will update the .tt file.
Source : here!
Open the edmx file in the VS's XML editor and check to see if there were errors genned when the update was attempted.
<!--Errors Found During Generation:
warning 6013: The table/view 'foo.dbo.snafu' does not have a primary key
defined and no valid primary key could be inferred. This table/view has
been excluded. To use the entity you will need to review your schema,
add the correct keys and uncomment it.
<EntityType Name="snafu">
<Property Name="snafu_column" Type="smallint" />
</EntityType>-->
In the above case...Adding a primary key to the table in question caused the "Update Model from Database" to work.
This answer is better: https://stackoverflow.com/a/23886016/1014884
Any manual editing is ripe for errors or will be lost when someone uses any tool like the wizard. Deleting and updating with the wizard is much better.
It doesnt update for example max length for string attributes!
If you work with TFS it is not good to delete the file, you want to keep the history and not affect others.
For me it works having a tiniy separate project that I can use to completely recreate the edmx file, I open it in xml, copy paste to the existing one, and move one shape in the model in order for VS to recreate the .cs file. Voila, it is now updated.
A view I created in the database was not appearing in the designer (after choosing "Update model from database..." and adding a check next to the name of the view). I saw no error message until I switched the EDMX to xml view:
Right click the edmx file
Select "Open With..."
Select "Automatic Editor Selector (XML)"
Click Find and search for your view name
In the edmx xml I found:
"Errors Found During Generation: warning 6013: The table/view '(view
name)' does not have a primary key defined and no valid primary key
could be inferred. This table/view has been excluded. To use the
entity, you will need to review your schema, add the correct keys, and
uncomment it."
I modified the view to have a primary key. Then I opened the edmx designer and ran "Update model from database..." and the view then appeared in the designer as expected with no errors.
Removing all tables from designer view and Updating after that works for me