|
>My first question is are the three different databases
actually on different machines, or are they just different datasources on one
machine?
3
different databases same machine 3 datasources
>My
second question is have you thought about what security holes you could be
creating by using the same login for 3 different applications?
I
think so. What i did not show was there is a permissions table that is a child
of the members table that controls access to the differnt
apps.
I
actually ment memberID i changed somethings and forgot to edit the
statement.
>SQLSERVER_1.DATABASE_X.dbo.TABLE table1
Ive
never actually seen this before. Do I have this right? The only thing that needs
to stay the same is the TABLE everything else I fill in with server specific
info yes?
>It seems like
you're planning a workaround with code that might better be addressed as a
single database application with three apps running off the same datasource.
I had considered that. I think it was the lazyness in
me that wanted to keep as much in place as possible to minimize bugs that may
crop up in the switch. That and you know not like i got some wiz bang stuff
going on over here but all together that would be like 60 tables. The ERD would
go crawling accross the wall. The realationships would look like one of those
matching excercises you did as a kid. Id be homocidal in no time trying to keep
track of it.
>(which we discussed at the meeting last
month).
I gotta get me a new job so I can make it to KC on
time! ;-)
Adaryl Wakefield
Aviator by passion Programmer by sheer force of will
|
- [KCFusion] system intergration Adaryl Wakefield
- RE: [KCFusion] system intergration Bruce Dunwiddie
- RE: [KCFusion] system intergration Adaryl Wakefield
- RE: [KCFusion] system intergration Templin, Luke
- Re: [KCFusion] system intergration Adaryl Wakefield
- RE: [KCFusion] system intergration Matt Jones
- RE: [KCFusion] system intergration Templin, Luke
- RE: [KCFusion] system intergration hartwichr
