how to modify this erd diagram? - sql

I'm sorry i couldn't form the question to be clear enough to describe the problem but I'm not a pro at this.
I'd like to ask
-how should I make this ERD format in the correct way ?
scenario is the salesman chooses an expert depending on what the expert days are and months will be available on + the kind of job like :part-time or full time ?
any ideas to modify the erd diagram ? maybe a new entity relationship ? i'm not sure
problem is underlined in the first picture please check it out>>
how can i solve this erd diagram , check this picture of erd diagram
class diagram

Related

ERD design for multiple same shaped table

Hello we are now working on international site design ,so many table need to have relation to the same shaped small translation table , which store translation for each langueges like left side of the image (Design#1).
Currently we have an idea to merge translation table like right side of the image (Design#2), but I'm not clear this design is good or bad. Could you tell me Design#2 is good or bad idea ?
Also if you have another solution for this case , please give me an advice.

Postgres - DB Design & Spring-Data-JPA query related suggestion required

Hello Friends,
I have a kind of requirement like, Student & Question are entities.
Both Entity are in many-to-many relation.
I would like to represent my idea is something likewise(refer below screen-shot. please correct me if any improvement is possible).
I would like to know from you guys is that,
1) is the above mentioned DB-design is good ? is there any improvement
then let me know.
And second one is related to query(JPQL),
2) it's most important, in spring-data-jpa, how would I implement in
such a way so that, even though user has not answered question then
also, those question needs to reflect under user-profile page that
this question is still not answered. Refer below screen-shot about
an expectation of this(second one) question.
Any help would be really appreciable!!

Building a map/flowchart to better understand a database

I am interested in creating a map of my database, so that I may understand it better. I am having difficulties understanding which tables relate to other tables, and I think a map, or flowchart would help me greatly. Has anyone done this? If so, how did you accomplish it?
You can try SQL Server Management Studio Express. Just right click on Database Diagrams and create a new diagram. You can select existing tables that you desire.
You can follow an excellent guide step by step here.
If you have Microsoft visio, that's a good software in creating a flowchart.
I use Lucid Chart (www.lucidchart.com) occasionally because we don't have Visio either. They offer a free account, which works pretty well, apart from the limit on the number of items you can put in one document (I want to say it's a limit of 60 entities).

Create ERD Of MS CRM Database

Is there any way to auto create ERD of any existing CRM applicaton.
I have MS CRM 11 On Premise and want to take a short look on entities and their relationship diagram. Do we need to create it manually by digging one by one entity and their relationship or is there any other way or any tool do it ?
OR This is not a valid question at all ?
Ideas will be appreciated if any.
Thanks in advance.
You should check out this article on MSDN. The section at the bottom titled Generate Entity Diagrams with the Metadata Diagram Tool describes how to use a program from the SDK to generate an ERD.

SQL Database Data Dictionary Inquiry

I'm a university student who is completely new to SQL and I don't know what I'm doing, so go easy on me. I have been given an assignment to design a Facebook-like database for a website for people who read books. I have made a very basic data dictionary which gives the general idea.
Is this a valid approach? Is there a better way of doing this? I'd appreciate any feedback I can get.
First of all, I would say good to see your efforts.
Here I would suggests you bit enhancements. Instead of maintaining different tables for
books_liked,books_read,wish_list, etc., you can maintain same with the help of flags in the master table books. This is to normalize your data.
eg. flg_liked, flg_wish_list, flg_read