I'm testing Master Data Services on SQL 2016 CTP 3.3 (azure VM). I've got a MDS model up and running. I can browse the model in Excel 2016 with the Master Data Services add-in.
If I create a new entity (table), it creates the new table and I can go into SQL server management studio to see the stg.NewTable with the column names I set.
When I add rows, and hit the publish button, I don't see the rows being added to the stage table for me to see in the database. Am I missing something ?
Thanks !
I'm an idiot.. MDS puts many many tables in by default, I wasn't looking in the obscurely named tables at the top. Just need to stop and look at the database structure!
When you load the data in MDS using Excel Add-in, the data is directly loaded into the entity table and not in the staging table. You can either extract the data using subscription view created on your entity or you can get the name of the entity table from mdm.tblEntity table and execute a select query on that table.
When you enter any data from MDS UI it gets stored in the mdm tables in MDM database. To get the data, you need Subscription Views and ETL(SSIS or any other tool)
Related
I have been using Oracle Catalog Manager to determine which reports are being affected by RPD columns. I'm wondering if there is any ORACLE table where all these data is kept.
For example, by using SQL, am I able to get these data:
How are the report columns defined back in metadata?
What are the OBIEE objects (Analysis, BIP Reports, Prompts and filters etc.) that are being referenced by a column(s)?
How are columns mapped through metadata?
Who are the owners of reports?
Presentation Catalog objects are not stored in a database. They are XML files on the file system in the folder structure holding your catalog!
What you want to get you get through Catalog Manager the fat client tool or through the command line runcat.sh/cmd which is basically Catalog Manager wihtout a GUI
I have 2 SQL Server databases. The reason is because I created an ASP.NET MVC project using "Individual User Accounts" for authentication. This created a default connection with a database that includes the following tables:
AspNetUserClaims, AspNetUserLogins, AspNetUsers, _MigrationHistory
I then went a step further and built out my own custom roles with a RoleController. So I also have a table for AspNetRoles and AspNetUserRoles. Everything with this is working.
I also have another database that I built in Management Studio that is holding all of the data of my application. I am using Entity Framework to communicate with the database.
I currently reference both databases in my web.config connection strings.
But I would like to migrate the database from the default connection (with my AspNetUsers) into the one in Management Studio.
Is it as simple as copying the tables and putting them in my other database in Management Studio or can I copy the whole schema? Just trying to figure out the best approach here.
You can migrate tables from a database to a diferent one. On SSMS, just right click on a database, select Tasks -> Generate Scripts, and use the wizard to create a script with the table definition and data (optional) to be executed on the new database.
I have created a Database in MS SQL and loaded the Database in my Server Explorer. In my MVC application, I wish to simply populate a single entity inside my database (Customer Name for example), does anyone know how I can send data to the database I have loaded? I can't seem to figure it out.
Any help will be highly appreciated.
If you're asking about how to insert data in Visual Studio itself, open Server Explorer, add a Data Connection to your database, expand the Tables node, right click on your table and select Show Table Data. This opens up a screen where you can add data.
If you only want to connect and populate one entity you should consider using Code First Entity Framework to drive your model using a plain C# class on the entity.
Scott Guthrie has a post on how to do that: Using EF Code First with an Existing Database, and Ralph Lavelle has a post that's more specific to MVC and includes migrations in the second part: Using Entity Framework Code First with an Existing Database (1/2) and Using Entity Framework Code First with an Existing Database (2/2).
When I create any new database It automatically create some tables in new database.
Details:
I created a new database "TestDatabase" using below command
Create database TestDatabase
When I expand the Tables folder, I found that there are already some tables created automatically.
These are those tables which I was using in some other database.
Table names:
1. Employee
2. Admin
etc
How can I create new fresh database to make sure that no tables created in it?
Presumably at some point you accidentally created these tables in the model database.
This is used as the template for creating new databases. Simply delete them from model to stop them appearing in every freshly created database.
SQL Server uses the model database as the basis for new databases. Check and see if these tables exist in model - and if they do, delete them.
You should probably check for other objects in modeltoo (stored procedures, views etc).
I have Visual Studio 2008:
I can create Entity Framework models on existing tables in a SQL Server 2005 database.
I can create Entity Framework models on tables I create in a local SQL Server 2008 database files.
However, when I add a new table to the SQL Server 2005 database, then try to create an Entity Framework model on it, it lets me click the little checkbox next to the table and finish, but the .edmx/...Designer.cs file consists only of four methods but nothing about the table that I selected, as if the I hadn't selected it.
What could be causing code not to be generated on the table I selected?
Where could I look for error messages regarding the attempted creation of code for this table?
0) I think, you have added and then deleted this table before. In this case you should open model file (Designer.cs), remove all this table related records (manualy) and then refresh the model.
1) Maybe you have many-to-many relationship tables. EF decides no to add "link" table in this case.
2) Maybe you have a table that has two fields (PK and FK to other one) ONLY. In this case EF does the same.
3) Install later SP to VS and framework.
4) Check connection string.