SQL Server Diagrams?

SQL Server Diagrams?

• suamikim

  hi duane, can u get deeper with that sounds cool. :P
  
  

• Guido79

  mig16 wrote:

  lol, today in the morning i was having fun with sql and i discovered that it changes the things, u can relate tables using diagrams , so when u modify a cell on table 1 it automaticly modify it on table 2 :P :)

  it looks like you've already answered the question that you asked me. to me, diagrams is one of the coolest features in sql server. as you observed, you can create and change referential integrity in a diagram. but the magic doesn't end there. you can also create, alter and drop tables, columns, indexes and constraints.
  
  
  

• Andrey Basko

  Brent Mills wrote:

  Same reason you diagram anything else, to help you visualize what's going on. The ability to do it in sql server is IMHO only there so the marketing department can say "hey look, diagramming is included". It doesn't change anything as far as how the database operates.

  
  um...sql server diagrams can dramatically impact how a database operates. database objects can be created, altered, and dropped...all within a diagram.
  
  
  

• Jossef Goldberg

  Brent Mills wrote:

  Duane Douglas wrote: Brent Mills wrote: Same reason you diagram anything else, to help you visualize what's going on. The ability to do it in sql server is IMHO only there so the marketing department can say "hey look, diagramming is included". It doesn't change anything as far as how the database operates. um...sql server diagrams can dramatically impact how a database operates. database objects can be created, altered, and dropped...all within a diagram. No, creating diagrams doesn't change how a db operates. It only helps you to visualize what's going on. If you choose to start changing stuff from there then it will let you but that's not what their primary purpose is. You are much better off modifying objects in tsql.

  obviously, you haven't spent much time (if any) working with diagrams. diagrams provide a graphical representation of a database. when a diagram changes, the underlying database that it represents also changes. i'm not going to debate whether modifying databases via a diagram is better or worse than using t-sql because that's a moot point.
  
  
  

• Arnoldio

  lol, today in the morning i was having fun with sql and i discovered that it changes the things, u can relate tables using diagrams , so when u modify a cell on table 1 it automaticly modify it on table 2 :P :)
  
  

• FirstDivision

  Yes, I actually work with er studio quite frequently but I think you're misunderstanding me. What I'm saying (and I took his original post to mean he had absolutely no clue what a diagram was) is that creating a diagram is not like creating a trigger. The presence of it doesn't affect how a db operates. I should have clarified that you are able to change the internals by modifying it. And yes, diagram vs tsql is a moot point, however, it is a good idea to understand what code gets generated when you do change something because it can be very bad.
  

• fafan_iran

  Duane Douglas wrote:

  Brent Mills wrote: Same reason you diagram anything else, to help you visualize what's going on. The ability to do it in sql server is IMHO only there so the marketing department can say "hey look, diagramming is included". It doesn't change anything as far as how the database operates. um...sql server diagrams can dramatically impact how a database operates. database objects can be created, altered, and dropped...all within a diagram.

  No, creating diagrams doesn't change how a db operates. It only helps you to visualize what's going on. If you choose to start changing stuff from there then it will let you but that's not what their primary purpose is. You are much better off modifying objects in tsql.

  
  

• Saviourmachine

  Same reason you diagram anything else, to help you visualize what's going on.  The ability to do it in sql server is IMHO only there so the marketing department can say "hey look, diagramming is included".  It doesn't change anything as far as how the database operates.
  

• Karthik987

  brent,
  
  ok. i think i understand what you're trying to say. the mere creation of a diagram doesn't affect how a db operates. but modifications made to a diagram can affect how a db operates. it is misleading to suggest that a diagram has absolutely no effect on the operation of the db it represents.
  
  
  
• SQL Server Diagrams?