MS SQL Farm

Hi all, thank in advance for your help.
The company I work for have been predominately using Oracle and IBM DB2. We
do use Sql Server on case by case basis, but there is no well implemented
infrastructure that will help us leverage MS Sql server. There has been
initiative between us (developers) to implement a structured proactively
managed Sql farm, so that we could continue developing MS Sql reliant
solutions. Unfortunately, there is not full time DBA and most of the
implementation and design will be done by us developers. More over we would
have to sell the idea to the management.
Would anyone be able to point to any source of documentation or study cases
that we could learn from? Products that will help implement and manage some
aspects of the environment such as monitoring/notification agents, backup
agents.
We were looking at implementation a solution that will be comprised of the
development/test and production servers with stand by servers . All data for
both the production and test environments will placed on the Network
Appliance storage (Filer iSCSI attached storage).
Regards,
Dominic
Ruski
http://www.microsoft.com/sql/evaluat...s/default.mspx
http://www.microsoft.com/technet/pro.../logship1.mspx
http://www.microsoft.com/sql/default.mspx
Hope this helps
Regards
CT
"Ruski" wrote:

> Hi all, thank in advance for your help.
> The company I work for have been predominately using Oracle and IBM DB2. We
> do use Sql Server on case by case basis, but there is no well implemented
> infrastructure that will help us leverage MS Sql server. There has been
> initiative between us (developers) to implement a structured proactively
> managed Sql farm, so that we could continue developing MS Sql reliant
> solutions. Unfortunately, there is not full time DBA and most of the
> implementation and design will be done by us developers. More over we would
> have to sell the idea to the management.
> Would anyone be able to point to any source of documentation or study cases
> that we could learn from? Products that will help implement and manage some
> aspects of the environment such as monitoring/notification agents, backup
> agents.
> We were looking at implementation a solution that will be comprised of the
> development/test and production servers with stand by servers . All data for
> both the production and test environments will placed on the Network
> Appliance storage (Filer iSCSI attached storage).
> Regards,
> Dominic

MS SQL 2000 - How to reflect table updates

Hello!
I have 2 database (DB1 and DB2) in 1 server. I want to reflect new changes made in DB1.tbl_pm_project to DB2.tbl_pm_project. Any idea on how to do it.
Thank you
JJ-honHello!

I have 2 database (DB1 and DB2) in 1 server. I want to reflect new changes made in DB1.tbl_pm_project to DB2.tbl_pm_project. Any idea on how to do it.

Thank you
JJ-hon

What kind of changes? Structural changes or data changes? How often do the changes need to be reflected (real time, near real time or batch)?

I'll assume data changes (insert, update, delete) and that the requirement is for real time.

For two databases on the same server, your best bet is probably going to be a trigger. I do not like triggers that affect data across schema boundaries (ie, from one db to another), but this will probably be your quickest solution.

See SQL BOL.

Regards,

hmscott|||Triggers or DTS or Replication... according to your requirement.

As you have only one table and if data is not huge then Trigger is fine else normally it is not preferred.

It's all about how fast & consistent data changes you want to reflect.|||Or let a stored procedure update both databases in a transaction since they are on the same server.