<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Development
»
Development and Production Database
15 posts, Page 1 of 2
1
2
»»
Development and Production Database
Rate Topic
Display Mode
Topic Options
Author
Message
kurin123
kurin123
Posted Friday, November 28, 2008 1:54 AM
Forum Newbie
Group: General Forum Members
Last Login: 2 days ago @ 6:41 AM
Points: 4,
Visits: 34
Hi,
I have 2 databases - one Development and one Production.
About 50 applications insert data into Production DB. I would like to test my Development DB and insert the data that go into Production into Development DB as well.
What is the best way how to do it?
Thanks
kurin
Post #610149
ChiragNS
ChiragNS
Posted Friday, November 28, 2008 2:16 AM
SSCrazy
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 5:02 AM
Points: 2,365,
Visits: 1,825
Are both the databases identical in every way - table structures , constraints etc
How much data are you looking at?
I assume you would want to port the data from production to development. You could use SSIS or BulkImport.
"Keep Trying"
Post #610160
kurin123
kurin123
Posted Friday, November 28, 2008 5:31 AM
Forum Newbie
Group: General Forum Members
Last Login: 2 days ago @ 6:41 AM
Points: 4,
Visits: 34
The structure is identical. What I want to test are new triggers and scheduled tasks.
Data are inserted into Production DB every minute from different applications. For each insert trigger is fired. When new row is inserted into Production DB I want to insert the same row into Development DB as well and that way test new triggers and performance.
Post #610287
ChiragNS
ChiragNS
Posted Monday, December 01, 2008 12:26 AM
SSCrazy
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 5:02 AM
Points: 2,365,
Visits: 1,825
Hi
Why do you want to insert the production data in to development. ? And what are the triggers for? Do they have any purpose other than inserting data into devlopment db.
Is it possible for you take a backup of the production db and restore in development. These triggers will slow down your production system.
"Keep Trying"
Post #611059
grapefruitmoon
grapefruitmoon
Posted Monday, December 01, 2008 5:05 AM
SSC-Addicted
Group: General Forum Members
Last Login: Friday, May 10, 2013 11:59 AM
Points: 445,
Visits: 896
This does not sound like a good idea, as the other posters say, you should import the data into development from your production system using SSIS or a bulk method.
But to answer the question better, we need a bit of background information;
What are the triggers you want to test? What do they do?
Why do you want to get the data into development?
-----------------------------------------------
SQL Server posts at my blog, Grapefruitmoon.Net
Post #611193
kurin123
kurin123
Posted Wednesday, December 03, 2008 1:33 PM
Forum Newbie
Group: General Forum Members
Last Login: 2 days ago @ 6:41 AM
Points: 4,
Visits: 34
Background: From few manufacturing lines i'm getting data every minute. There are few triggers those fire on insert and they do some calculation and based on them they insert data into new table, send email etc.
I know it's not the best way to do it. But its the way it has been done... I want to change it to work better, remove most of the triggers and replace them with sheduled tasks and so on.
Because this change is quite big, so I would like to test it for a while. The best way for me is to insert real production data (as they are comming from the manufacturing line) into my development DB and see how it behaves and if the performance is better or not.
Post #613139
noeld
noeld
Posted Wednesday, December 03, 2008 2:33 PM
SSCertifiable
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 4:39 PM
Points: 6,260,
Visits: 1,977
I think you want to probably capture an SQL "trace" and then replay it on the "development" database at will.
* Noel
Post #613202
ChiragNS
ChiragNS
Posted Wednesday, December 03, 2008 11:43 PM
SSCrazy
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 5:02 AM
Points: 2,365,
Visits: 1,825
Do you mean to say insert real time production data into development db. Then how will you put the data back to production?
What i would suggest is
Create a development db as close to production db.
Simulate the same kind of activity that happens on production in your development environment.
Make the changes and test it properly
If test goes fine deploy to production.
"Keep Trying"
Post #613426
kurin123
kurin123
Posted Thursday, December 04, 2008 6:47 AM
Forum Newbie
Group: General Forum Members
Last Login: 2 days ago @ 6:41 AM
Points: 4,
Visits: 34
noeld (12/3/2008)
I think you want to probably capture an SQL "trace" and then replay it on the "development" database at will.
THX man!! That wont be easy to automaticaly process the trace script, but it is worth a try.
Post #613629
WILLIAM MITCHELL
WILLIAM MITCHELL
Posted Friday, December 05, 2008 5:08 AM
UDP Broadcaster
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:45 AM
Points: 1,441,
Visits: 2,485
Here's what you might do.
Take a backup from production and restore it as a TEST database. Then run Profiler on the production db and save the trace to a new table in the TEST db. There are 100's of events that you can trace, but you'll probably be most interested in the T-SQL events like Statement start / end, Batch start / end and so on.
Then, you can go into your TEST db and review the trace table. You can copy the SQL statements from the trace table and execute them one-by-one in your TEST db.
Profiler will have some impact on the performance of the production db so you'll probably want to run it only for brief periods, but during times of fairly high activity so you can get a complete picture of the workload.
Post #614393
« Prev Topic
|
Next Topic »
15 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
