newbie question

You want me to send my resume' where? What your asking for is not a
small task and is probably out of scope for one posting. Try breaking
your project above down in to individual tasks, do your homework
first, and then post if you can't find the answer.
If you are the one that's going to be doing this...I would start with
Linked Servers and go from there. Also, in my opinion, wipe Views
complete from your chain of thought. Think Stored Procedures!
You have one nice project in front of you! Good Luck!
On Dec 1, 4:34 am, "R.A.F." <noem...@.nospam.com> wrote:
> Hi,
> i've just finished MOC 2779B and i would like to play with the "monster"...
> at work we have 2 MS SQL server 2005 RDBMS installed on 2 PCs.
> let's say that DB-PC1 is the source DB where a certain application runs
> on PC1.
> DB-PC2 is a test DB on PC2.
> I would like to do the following things :
> 1- create a view on DB-PC1 to retrieve only the necessary data for DB-PC2.
> 2- everytime this data view is updated (deleted, inserted or updated
> records) i would like to send the complete vdata view to DB-PC2 (test DB)
> 3- in this test DB, everytime that it receives data from DB-PC1, it
> should split data records (fields, ...) into several parts and insert
> them into tables availables on DB-PC2.
> Like that we totally split data and risks to damage them.
> I want to do that because i'm preparing a web portal on test DB-PC2
> which should use a partial data information from DB-PC1.
> So i do not want this web portal (in case of mistake into code) to
> destroy partially DB-PC1.
> so i though that for point 1 i could create a view and triggers to
> detects update, inserts or delete actions.
> However, how can i send this information (data view) from DB-PC1 tp DB-PC2 ?
> Do you have any suggestion ?
> thanks a lot,
> R.A.F.
SQL Server 2005 Books Online (September 2007)
Linking Servers:
http://msdn2.microsoft.com/en-us/library/ms188279.aspx
Ekrem nsoy
"R.A.F." <noemail@.nospam.com> wrote in message
news:OQncU$FNIHA.5360@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> thanks Dave.
> this is the kind of help i needed : linked servers.
> how ? :-)
> are there some requirements, or suggestions from MS ?
> Dave wrote:

Newbie Entity Relationship Advice

Dear All,
Firstly since the first time posting on this group, I apologise if this is
posted on the wrong newsgroup but could someone please help me with the
question below.
I have received a database designed by a colleague who has since left the
organisation and I was wondering if there were any tools or techniques that
could help create an entity relationship diagram of the database. With Acces
s
you had a utility called database documentor, which could help me with my
task. If this is not possible I would like to get a list of all tables and
Primary/Foreign key constraints.
There are over 100 tables and it would take a long time to go through each
one looking at primary keys and foreign keys. Is there anyone out there that
can offer this SQL Server 2000 newbie some helping advice?
p.s. What newsgroup should I have posted a general question on?
Thanks.
Alastair MacFarlaneYes. You can do this in SQL Server 2000. Look in the Database and you will
see a "Diagrams" icon. Use that to create the entity relationship.
"Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote
in message news:477DE3D1-0457-4AF3-B067-BA5A880364F0@.microsoft.com...
> Dear All,
> Firstly since the first time posting on this group, I apologise if this is
> posted on the wrong newsgroup but could someone please help me with the
> question below.
> I have received a database designed by a colleague who has since left the
> organisation and I was wondering if there were any tools or techniques
> that
> could help create an entity relationship diagram of the database. With
> Access
> you had a utility called database documentor, which could help me with my
> task. If this is not possible I would like to get a list of all tables
> and
> Primary/Foreign key constraints.
> There are over 100 tables and it would take a long time to go through each
> one looking at primary keys and foreign keys. Is there anyone out there
> that
> can offer this SQL Server 2000 newbie some helping advice?
> p.s. What newsgroup should I have posted a general question on?
> Thanks.
> Alastair MacFarlane|||The Database Diagram tool within Enterprise Manager allows you to create a
visual diagram of the database that can also be used to create, edit or
delete tables. You can launch the wizard by right-cling on the Diagrams
node under the desired database and selecting 'new database diagram'. See
the Books Online for details on usage.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote
in message news:477DE3D1-0457-4AF3-B067-BA5A880364F0@.microsoft.com...
> Dear All,
> Firstly since the first time posting on this group, I apologise if this is
> posted on the wrong newsgroup but could someone please help me with the
> question below.
> I have received a database designed by a colleague who has since left the
> organisation and I was wondering if there were any tools or techniques
> that
> could help create an entity relationship diagram of the database. With
> Access
> you had a utility called database documentor, which could help me with my
> task. If this is not possible I would like to get a list of all tables
> and
> Primary/Foreign key constraints.
> There are over 100 tables and it would take a long time to go through each
> one looking at primary keys and foreign keys. Is there anyone out there
> that
> can offer this SQL Server 2000 newbie some helping advice?
> p.s. What newsgroup should I have posted a general question on?
> Thanks.
> Alastair MacFarlane|||With SQL Server, create a DB diagram via Enterprise manager by selecting all
the tables. This will get u the ERD along with all existing relationships...
R
"Alastair MacFarlane" wrote:

> Dear All,
> Firstly since the first time posting on this group, I apologise if this is
> posted on the wrong newsgroup but could someone please help me with the
> question below.
> I have received a database designed by a colleague who has since left the
> organisation and I was wondering if there were any tools or techniques tha
t
> could help create an entity relationship diagram of the database. With Acc
ess
> you had a utility called database documentor, which could help me with my
> task. If this is not possible I would like to get a list of all tables an
d
> Primary/Foreign key constraints.
> There are over 100 tables and it would take a long time to go through each
> one looking at primary keys and foreign keys. Is there anyone out there th
at
> can offer this SQL Server 2000 newbie some helping advice?
> p.s. What newsgroup should I have posted a general question on?
> Thanks.
> Alastair MacFarlane|||Thanks Yosh, Dan and Rakesh. I didn't realise that the wizard would create
the entity diagram for you. This is better that Access!
Alastair
"Yosh" wrote:

> Yes. You can do this in SQL Server 2000. Look in the Database and you will
> see a "Diagrams" icon. Use that to create the entity relationship.
>
> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote
> in message news:477DE3D1-0457-4AF3-B067-BA5A880364F0@.microsoft.com...
>
>|||The Diagram will automatically draw connecting lines only if referential
integrity constraints were implemented on the tables.
"Yosh" <Yosh@.nospam.com> wrote in message
news:u3iMO5irFHA.3788@.TK2MSFTNGP12.phx.gbl...
> Yes. You can do this in SQL Server 2000. Look in the Database and you will
> see a "Diagrams" icon. Use that to create the entity relationship.
>
> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote
> in message news:477DE3D1-0457-4AF3-B067-BA5A880364F0@.microsoft.com...
>