best way to set up development and test databases

Hi,
I would like to set up 2 copies of my database - one as a development
database and another for testing.
I have tried to use the Transfer database option but it fails consistently.
Could I simply backup my "live" database and restore it onto a blank database.
Yes.
"lindab" <lindab@.discussions.microsoft.com> wrote in message
news:133A5514-D004-4187-B3F6-CD6F724AA5D9@.microsoft.com...
> Hi,
> I would like to set up 2 copies of my database - one as a development
> database and another for testing.
> I have tried to use the Transfer database option but it fails
> consistently.
> Could I simply backup my "live" database and restore it onto a blank
> database.
>
|||If on the same machine, be sure & use the "with move" option on the
restore, so you have different mdf & ldf filenames for the OS to work
with.
ChrisR wrote:[vbcol=seagreen]
> Yes.
> "lindab" <lindab@.discussions.microsoft.com> wrote in message
> news:133A5514-D004-4187-B3F6-CD6F724AA5D9@.microsoft.com...
|||The same would apply if on different machines, and SQL was installed in a
different location.
<unc27932@.yahoo.com> wrote in message
news:1123608429.243967.43720@.g44g2000cwa.googlegro ups.com...
> If on the same machine, be sure & use the "with move" option on the
> restore, so you have different mdf & ldf filenames for the OS to work
> with.
> ChrisR wrote:
>

best way to set up development and test databases

Hi,
I would like to set up 2 copies of my database - one as a development
database and another for testing.
I have tried to use the Transfer database option but it fails consistently.
Could I simply backup my "live" database and restore it onto a blank databas
e.Yes.
"lindab" <lindab@.discussions.microsoft.com> wrote in message
news:133A5514-D004-4187-B3F6-CD6F724AA5D9@.microsoft.com...
> Hi,
> I would like to set up 2 copies of my database - one as a development
> database and another for testing.
> I have tried to use the Transfer database option but it fails
> consistently.
> Could I simply backup my "live" database and restore it onto a blank
> database.
>|||If on the same machine, be sure & use the "with move" option on the
restore, so you have different mdf & ldf filenames for the OS to work
with.
ChrisR wrote:[vbcol=seagreen]
> Yes.
> "lindab" <lindab@.discussions.microsoft.com> wrote in message
> news:133A5514-D004-4187-B3F6-CD6F724AA5D9@.microsoft.com...|||The same would apply if on different machines, and SQL was installed in a
different location.
<unc27932@.yahoo.com> wrote in message
news:1123608429.243967.43720@.g44g2000cwa.googlegroups.com...
> If on the same machine, be sure & use the "with move" option on the
> restore, so you have different mdf & ldf filenames for the OS to work
> with.
> ChrisR wrote:
>

best way to set up development and test databases

Hi,
I would like to set up 2 copies of my database - one as a development
database and another for testing.
I have tried to use the Transfer database option but it fails consistently.
Could I simply backup my "live" database and restore it onto a blank database.Yes.
"lindab" <lindab@.discussions.microsoft.com> wrote in message
news:133A5514-D004-4187-B3F6-CD6F724AA5D9@.microsoft.com...
> Hi,
> I would like to set up 2 copies of my database - one as a development
> database and another for testing.
> I have tried to use the Transfer database option but it fails
> consistently.
> Could I simply backup my "live" database and restore it onto a blank
> database.
>|||If on the same machine, be sure & use the "with move" option on the
restore, so you have different mdf & ldf filenames for the OS to work
with.
ChrisR wrote:
> Yes.
> "lindab" <lindab@.discussions.microsoft.com> wrote in message
> news:133A5514-D004-4187-B3F6-CD6F724AA5D9@.microsoft.com...
> > Hi,
> > I would like to set up 2 copies of my database - one as a development
> > database and another for testing.
> > I have tried to use the Transfer database option but it fails
> > consistently.
> > Could I simply backup my "live" database and restore it onto a blank
> > database.
> >|||The same would apply if on different machines, and SQL was installed in a
different location.
<unc27932@.yahoo.com> wrote in message
news:1123608429.243967.43720@.g44g2000cwa.googlegroups.com...
> If on the same machine, be sure & use the "with move" option on the
> restore, so you have different mdf & ldf filenames for the OS to work
> with.
> ChrisR wrote:
>> Yes.
>> "lindab" <lindab@.discussions.microsoft.com> wrote in message
>> news:133A5514-D004-4187-B3F6-CD6F724AA5D9@.microsoft.com...
>> > Hi,
>> > I would like to set up 2 copies of my database - one as a development
>> > database and another for testing.
>> > I have tried to use the Transfer database option but it fails
>> > consistently.
>> > Could I simply backup my "live" database and restore it onto a blank
>> > database.
>> >
>

Best way to handle existing rows

I need to create a fairly simple package that copies data from one database using a sql querie and inserts it into another. what's the best way to handle rows that already exist in the destination table? The package needs to run once a day and ignore rows inserted from previous runs.You can pass the data through a lookup transform and compare them to the destination dataset. The rows that don't match will be marked as errors so click on the "configure the error output" and set it to redirect rows instead of failure. Then you can connect the red arrow to your destination and map the rows. There will be two extra columns but you don't need to worry about them as they are just for error tracking and you don't technically have errors.|||

The method brent describes is discussed in more detail here: http://www.sqlis.com/default.aspx?311

Its also worth saying that if the data in the source is timestamped when it canges then you can use that timestamp to only pull out data changed since previous load. i.e. Reduce the amount of data that you have to process.

-Jamie