Linking databases on same SQL Server

Hi,
I am building an application for a client. The App has two separate .adp
frontends connecting to two differenet SQL databases. Now I have to get data
from each of the SQL databases for reporting.
It is possible to create another SQL database that links to the two existing
databases, mentioned above?
--
Regards,
AlanIt is possible, but not necessary. To get data from both dbs for reporting,
simply preface your query with the dbs name.
For example:
USE master
GO
SELECT TOP 5 * FROM Northwind.dbo.Customers
Andre|||This is a pretty open question. What do you mean, link exactly? Like do
you want to query them together? Or combine the data for reporting? And
how much data do you have?
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"steel" <steel@.community.nospam> wrote in message
news:36AD2F00-AEC9-47DE-BFA4-65F0F886764D@.microsoft.com...
> Hi,
> I am building an application for a client. The App has two separate .adp
> frontends connecting to two differenet SQL databases. Now I have to get
> data
> from each of the SQL databases for reporting.
> It is possible to create another SQL database that links to the two
> existing
> databases, mentioned above?
> --
> Regards,
> Alan|||Hi Alan,
How are things going? If there are two different data source, you could
also Linked Table both. I would appreciate it if you could post here to let
us know the detail scenario of the issue. If you have any questions or
concerns, please don't hesitate to let me know. I look forward to hearing
from you, and I am happy to be of assistance.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
I am developing two Access .adp projects. The intention is to have them both
as separate marketable databases. A company purchasing one or both projects
would either setup a SQL server or a single project using MSDE.
One company would like to purchase both databases (i.e., purchase .adp
projects plus setup/purchase of SQL Server). The company would like to have
data flow between the two databases. So rather than make changes to our
databases I thougt we could develop a third database that stores or links th
e
other two databases together. Maybe this database would only contain Queries
linking the data. If the company required any table modifications these to
could be stored in the third database.
One problem we may encounter is during replication of the .adp projects as
the company has an off-site use for the projects but would like to merge the
data into the main SQL db's.
What are your thoughts?
p.s: Sorry if this type of advice isn't covered by MSDN support.
Alan
--
Regards,
Alan
"Michael Cheng [MSFT]" wrote:

> Hi Alan,
> How are things going? If there are two different data source, you could
> also Linked Table both. I would appreciate it if you could post here to le
t
> us know the detail scenario of the issue. If you have any questions or
> concerns, please don't hesitate to let me know. I look forward to hearing
> from you, and I am happy to be of assistance.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>|||My advice would actually be to only have one database,especially if they are
very tightly bound to one another. Your install scripts could create the
database and or the objects at install time. The queries you create in the
database could be morphed as products are installed/deinstalled. This would
make it easier for the user to maintain in terms of backups and such, and
easier for you to create and everything.
You also might consider letting the database be any database, and give the
user scripts to add if they are advanced.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"steel" <steel@.community.nospam> wrote in message
news:1B6BDFFD-671C-4B6F-ABFE-73C7C4E69666@.microsoft.com...
> Hi Michael,
> I am developing two Access .adp projects. The intention is to have them
> both
> as separate marketable databases. A company purchasing one or both
> projects
> would either setup a SQL server or a single project using MSDE.
> One company would like to purchase both databases (i.e., purchase .adp
> projects plus setup/purchase of SQL Server). The company would like to
> have
> data flow between the two databases. So rather than make changes to our
> databases I thougt we could develop a third database that stores or links
> the
> other two databases together. Maybe this database would only contain
> Queries
> linking the data. If the company required any table modifications these to
> could be stored in the third database.
> One problem we may encounter is during replication of the .adp projects as
> the company has an off-site use for the projects but would like to merge
> the
> data into the main SQL db's.
> What are your thoughts?
> p.s: Sorry if this type of advice isn't covered by MSDN support.
> Alan
> --
> Regards,
> Alan
>
> "Michael Cheng [MSFT]" wrote:
>|||Hi Alan,
Thanks for your questions and kindly understanding.
Yes, for this issue is more likely an Advisory Services issue. Microsoft
Advisory Services provides short-term advice and guidance for problems not
covered by Problem Resolution Service as well as requests for consultative
assistance for design, development and deployment issues. You may call this
number to get Advisory Services: (800) 936-5200.
I understood your scenario as when customer want a customization table, you
would like to put it in another database other than your project. If I have
misunderstood your concern, please feel free to point it out.
Personally, I agreed with MVP Louis Davidson's suggestion having only one
database.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.