dbTalk Databases Forums  

Updating an Instance from the production database

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools


Discuss Updating an Instance from the production database in the microsoft.public.sqlserver.tools forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Hoardling1 via SQLMonster.com
 
Posts: n/a

Default Updating an Instance from the production database - 05-28-2008 , 12:15 PM






I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com


Reply With Quote
  #2  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM






I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
  #3  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM



I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
  #4  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM



I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
  #5  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM



I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
  #6  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM



I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
  #7  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM



I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
  #8  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM



I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
  #9  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM



I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
  #10  
Old   
Tom Moreau
 
Posts: n/a

Default Re: Updating an Instance from the production database - 05-28-2008 , 01:27 PM



I think you are using terms incorrectly. Any installation of SQL Server is
an instance. You can have a named instance or a default instance. You can
have several instances on a server, but only one of them can be a default
instance.

That said, it appears that you want to keep 2 DB's in synch. Consider
transactional replication. The prod DB would be the publisher and the other
DB would be the subscriber.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote

I am currently using SQL Server 2000. I have a production database and an
instance. The instance is mainly for web display. What I would like to do
is when the production database has an insert or update a trigger, or any
other option, activates and inserts or updates the instance database
immediately. I am mainly looking at this process, but if anyone has any
other ideas I am willing to listen. I have thought about DTS and doing
truncate then copy the database into the set, but clearing and copying seems
like a lot of overhead.

--
Message posted via http://www.sqlmonster.com



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.