Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
abacusdotcom
Posting Yak Master
133 Posts |
 Posted - 2010-10-15 : 04:49:28
|
| Good morning good people of ST,This amazes me, I have 2 working SQL SERVER database environments, test and production. I noticed that for every operations done on test, it reflects on productions environment which is not suppose to be. The whole thing suppose to be after test is certified okay, we then move the solution to production.1. what can be the connection between test and production which are different instances.2. For every updates in test, it reflects in production verbatim. How?3. Is it possible for SQL files (dbf and log) created in test environment and copied to production environment, and that linked the two dbs.many thanks.I sign for fame not for shame but all the same, I sign my name. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-10-15 : 05:53:19
|
| There's some trigger or replication or something in the app that's moving changes to prod. The two SQL instances won't have decided to do this themselves--Gail ShawSQL Server MVP |
 |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-10-15 : 06:06:15
|
The two SQL instances won't have decided to do this themselvesThis would be artificial intelligenceor artificial stupidity
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
Jasons
Starting Member
2 Posts |
Posted - 2010-10-20 : 17:03:46
|
| you may want to search if the instance name is coded in any of your scripts. I think the qery below could be a good start,select * from syscomments where ctext like '%YourTestInstanceName%'And you should also check the connection manager in all the DTS/SSIS to see if the test instance is used instead.J.S |
|
|
|
|
|
|
Test and Production db clashes.