There are ten DB Servers in live network. Out of 10 DB servers, one of them
has the database and the contents are replicated throughout. The size of
the database is about 20 GB and it is to be updated on weekly basis. The
time frame for replication is limited to 2 hours and all the data must be
updated from the Update DB server within 2 hours given.
What is the best data replication method on this scenario?
Jason,
transactional would be the fastest. Log shipping might be of alternative
interest. I'm assuming that the subscribers don't need to update the data.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Showing posts with label live. Show all posts
Showing posts with label live. Show all posts
Sunday, March 25, 2012
Thursday, March 22, 2012
Best practices to transfer data/tables from TEST to LIVE
HI all,
I'm definately a newbie and have what is probably a simple question
but I want to make sure I'm following good practices.
What is the best way to update a LIVE database with data being created
on a TEST/DEV database?
I want to send a few new records I created on a test environment onto
a live environment to a few different tables. It is only a couple
records and could probably manually do it in like 10 minutes. But I
assume eventually I'll have larger qualities of data to move and
tables to update and I don't want to forget to include soemthing.
What is the best way to handle this kind of stuff? Scripts? Any
other suggestions or different ideas?
Kind Regards,
Ray
You can achieve your goal scripting or using SSIS; scripting could seem the
simplest way for the job you described, but if you think that the same job
could be reused or subsequently implemented, you can build a package using
Business Intelligence Development Studio (BIDS). For more (really more!)
details, look at the Books on Line "SQL Server Integration Services (SSIS)"
chapter.
Gilberto Zampatti
"bcap" wrote:
> HI all,
> I'm definately a newbie and have what is probably a simple question
> but I want to make sure I'm following good practices.
> What is the best way to update a LIVE database with data being created
> on a TEST/DEV database?
> I want to send a few new records I created on a test environment onto
> a live environment to a few different tables. It is only a couple
> records and could probably manually do it in like 10 minutes. But I
> assume eventually I'll have larger qualities of data to move and
> tables to update and I don't want to forget to include soemthing.
> What is the best way to handle this kind of stuff? Scripts? Any
> other suggestions or different ideas?
> Kind Regards,
> Ray
>
|||On Jun 9, 3:24 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> You can achieve your goal scripting or using SSIS; scripting could seem the
> simplest way for the job you described, but if you think that the same job
> could be reused or subsequently implemented, you can build a package using
> Business Intelligence Development Studio (BIDS). For more (really more!)
> details, look at the Books on Line "SQL Server Integration Services (SSIS)"
> chapter.
> Gilberto Zampatti
>
> "bcap" wrote:
>
>
>
> - Show quoted text -
Thank you very much!
I'm definately a newbie and have what is probably a simple question
but I want to make sure I'm following good practices.
What is the best way to update a LIVE database with data being created
on a TEST/DEV database?
I want to send a few new records I created on a test environment onto
a live environment to a few different tables. It is only a couple
records and could probably manually do it in like 10 minutes. But I
assume eventually I'll have larger qualities of data to move and
tables to update and I don't want to forget to include soemthing.
What is the best way to handle this kind of stuff? Scripts? Any
other suggestions or different ideas?
Kind Regards,
Ray
You can achieve your goal scripting or using SSIS; scripting could seem the
simplest way for the job you described, but if you think that the same job
could be reused or subsequently implemented, you can build a package using
Business Intelligence Development Studio (BIDS). For more (really more!)
details, look at the Books on Line "SQL Server Integration Services (SSIS)"
chapter.
Gilberto Zampatti
"bcap" wrote:
> HI all,
> I'm definately a newbie and have what is probably a simple question
> but I want to make sure I'm following good practices.
> What is the best way to update a LIVE database with data being created
> on a TEST/DEV database?
> I want to send a few new records I created on a test environment onto
> a live environment to a few different tables. It is only a couple
> records and could probably manually do it in like 10 minutes. But I
> assume eventually I'll have larger qualities of data to move and
> tables to update and I don't want to forget to include soemthing.
> What is the best way to handle this kind of stuff? Scripts? Any
> other suggestions or different ideas?
> Kind Regards,
> Ray
>
|||On Jun 9, 3:24 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> You can achieve your goal scripting or using SSIS; scripting could seem the
> simplest way for the job you described, but if you think that the same job
> could be reused or subsequently implemented, you can build a package using
> Business Intelligence Development Studio (BIDS). For more (really more!)
> details, look at the Books on Line "SQL Server Integration Services (SSIS)"
> chapter.
> Gilberto Zampatti
>
> "bcap" wrote:
>
>
>
> - Show quoted text -
Thank you very much!
Best practices to transfer data/tables from TEST to LIVE
HI all,
I'm definately a newbie and have what is probably a simple question
but I want to make sure I'm following good practices.
What is the best way to update a LIVE database with data being created
on a TEST/DEV database?
I want to send a few new records I created on a test environment onto
a live environment to a few different tables. It is only a couple
records and could probably manually do it in like 10 minutes. But I
assume eventually I'll have larger qualities of data to move and
tables to update and I don't want to forget to include soemthing.
What is the best way to handle this kind of stuff? Scripts? Any
other suggestions or different ideas?
Kind Regards,
RayYou can achieve your goal scripting or using SSIS; scripting could seem the
simplest way for the job you described, but if you think that the same job
could be reused or subsequently implemented, you can build a package using
Business Intelligence Development Studio (BIDS). For more (really more!)
details, look at the Books on Line "SQL Server Integration Services (SSIS)"
chapter.
Gilberto Zampatti
"bcap" wrote:
> HI all,
> I'm definately a newbie and have what is probably a simple question
> but I want to make sure I'm following good practices.
> What is the best way to update a LIVE database with data being created
> on a TEST/DEV database?
> I want to send a few new records I created on a test environment onto
> a live environment to a few different tables. It is only a couple
> records and could probably manually do it in like 10 minutes. But I
> assume eventually I'll have larger qualities of data to move and
> tables to update and I don't want to forget to include soemthing.
> What is the best way to handle this kind of stuff? Scripts? Any
> other suggestions or different ideas?
> Kind Regards,
> Ray
>|||On Jun 9, 3:24 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> You can achieve your goal scripting or using SSIS; scripting could seem th
e
> simplest way for the job you described, but if you think that the same job
> could be reused or subsequently implemented, you can build a package using
> Business Intelligence Development Studio (BIDS). For more (really more!)
> details, look at the Books on Line "SQL Server Integration Services (SSIS)
"
> chapter.
> Gilberto Zampatti
>
> "bcap" wrote:
>
>
>
>
>
>
> - Show quoted text -
Thank you very much!
I'm definately a newbie and have what is probably a simple question
but I want to make sure I'm following good practices.
What is the best way to update a LIVE database with data being created
on a TEST/DEV database?
I want to send a few new records I created on a test environment onto
a live environment to a few different tables. It is only a couple
records and could probably manually do it in like 10 minutes. But I
assume eventually I'll have larger qualities of data to move and
tables to update and I don't want to forget to include soemthing.
What is the best way to handle this kind of stuff? Scripts? Any
other suggestions or different ideas?
Kind Regards,
RayYou can achieve your goal scripting or using SSIS; scripting could seem the
simplest way for the job you described, but if you think that the same job
could be reused or subsequently implemented, you can build a package using
Business Intelligence Development Studio (BIDS). For more (really more!)
details, look at the Books on Line "SQL Server Integration Services (SSIS)"
chapter.
Gilberto Zampatti
"bcap" wrote:
> HI all,
> I'm definately a newbie and have what is probably a simple question
> but I want to make sure I'm following good practices.
> What is the best way to update a LIVE database with data being created
> on a TEST/DEV database?
> I want to send a few new records I created on a test environment onto
> a live environment to a few different tables. It is only a couple
> records and could probably manually do it in like 10 minutes. But I
> assume eventually I'll have larger qualities of data to move and
> tables to update and I don't want to forget to include soemthing.
> What is the best way to handle this kind of stuff? Scripts? Any
> other suggestions or different ideas?
> Kind Regards,
> Ray
>|||On Jun 9, 3:24 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> You can achieve your goal scripting or using SSIS; scripting could seem th
e
> simplest way for the job you described, but if you think that the same job
> could be reused or subsequently implemented, you can build a package using
> Business Intelligence Development Studio (BIDS). For more (really more!)
> details, look at the Books on Line "SQL Server Integration Services (SSIS)
"
> chapter.
> Gilberto Zampatti
>
> "bcap" wrote:
>
>
>
>
>
>
> - Show quoted text -
Thank you very much!
Best practices to transfer data/tables from TEST to LIVE
HI all,
I'm definately a newbie and have what is probably a simple question
but I want to make sure I'm following good practices.
What is the best way to update a LIVE database with data being created
on a TEST/DEV database?
I want to send a few new records I created on a test environment onto
a live environment to a few different tables. It is only a couple
records and could probably manually do it in like 10 minutes. But I
assume eventually I'll have larger qualities of data to move and
tables to update and I don't want to forget to include soemthing.
What is the best way to handle this kind of stuff? Scripts? Any
other suggestions or different ideas?
Kind Regards,
RayYou can achieve your goal scripting or using SSIS; scripting could seem the
simplest way for the job you described, but if you think that the same job
could be reused or subsequently implemented, you can build a package using
Business Intelligence Development Studio (BIDS). For more (really more!)
details, look at the Books on Line "SQL Server Integration Services (SSIS)"
chapter.
Gilberto Zampatti
"bcap" wrote:
> HI all,
> I'm definately a newbie and have what is probably a simple question
> but I want to make sure I'm following good practices.
> What is the best way to update a LIVE database with data being created
> on a TEST/DEV database?
> I want to send a few new records I created on a test environment onto
> a live environment to a few different tables. It is only a couple
> records and could probably manually do it in like 10 minutes. But I
> assume eventually I'll have larger qualities of data to move and
> tables to update and I don't want to forget to include soemthing.
> What is the best way to handle this kind of stuff? Scripts? Any
> other suggestions or different ideas?
> Kind Regards,
> Ray
>|||On Jun 9, 3:24 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> You can achieve your goal scripting or using SSIS; scripting could seem the
> simplest way for the job you described, but if you think that the same job
> could be reused or subsequently implemented, you can build a package using
> Business Intelligence Development Studio (BIDS). For more (really more!)
> details, look at the Books on Line "SQL Server Integration Services (SSIS)"
> chapter.
> Gilberto Zampatti
>
> "bcap" wrote:
> > HI all,
> > I'm definately a newbie and have what is probably a simple question
> > but I want to make sure I'm following good practices.
> > What is the best way to update a LIVE database with data being created
> > on a TEST/DEV database?
> > I want to send a few new records I created on a test environment onto
> > a live environment to a few different tables. It is only a couple
> > records and could probably manually do it in like 10 minutes. But I
> > assume eventually I'll have larger qualities of data to move and
> > tables to update and I don't want to forget to include soemthing.
> > What is the best way to handle this kind of stuff? Scripts? Any
> > other suggestions or different ideas?
> > Kind Regards,
> > Ray- Hide quoted text -
> - Show quoted text -
Thank you very much!
I'm definately a newbie and have what is probably a simple question
but I want to make sure I'm following good practices.
What is the best way to update a LIVE database with data being created
on a TEST/DEV database?
I want to send a few new records I created on a test environment onto
a live environment to a few different tables. It is only a couple
records and could probably manually do it in like 10 minutes. But I
assume eventually I'll have larger qualities of data to move and
tables to update and I don't want to forget to include soemthing.
What is the best way to handle this kind of stuff? Scripts? Any
other suggestions or different ideas?
Kind Regards,
RayYou can achieve your goal scripting or using SSIS; scripting could seem the
simplest way for the job you described, but if you think that the same job
could be reused or subsequently implemented, you can build a package using
Business Intelligence Development Studio (BIDS). For more (really more!)
details, look at the Books on Line "SQL Server Integration Services (SSIS)"
chapter.
Gilberto Zampatti
"bcap" wrote:
> HI all,
> I'm definately a newbie and have what is probably a simple question
> but I want to make sure I'm following good practices.
> What is the best way to update a LIVE database with data being created
> on a TEST/DEV database?
> I want to send a few new records I created on a test environment onto
> a live environment to a few different tables. It is only a couple
> records and could probably manually do it in like 10 minutes. But I
> assume eventually I'll have larger qualities of data to move and
> tables to update and I don't want to forget to include soemthing.
> What is the best way to handle this kind of stuff? Scripts? Any
> other suggestions or different ideas?
> Kind Regards,
> Ray
>|||On Jun 9, 3:24 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> You can achieve your goal scripting or using SSIS; scripting could seem the
> simplest way for the job you described, but if you think that the same job
> could be reused or subsequently implemented, you can build a package using
> Business Intelligence Development Studio (BIDS). For more (really more!)
> details, look at the Books on Line "SQL Server Integration Services (SSIS)"
> chapter.
> Gilberto Zampatti
>
> "bcap" wrote:
> > HI all,
> > I'm definately a newbie and have what is probably a simple question
> > but I want to make sure I'm following good practices.
> > What is the best way to update a LIVE database with data being created
> > on a TEST/DEV database?
> > I want to send a few new records I created on a test environment onto
> > a live environment to a few different tables. It is only a couple
> > records and could probably manually do it in like 10 minutes. But I
> > assume eventually I'll have larger qualities of data to move and
> > tables to update and I don't want to forget to include soemthing.
> > What is the best way to handle this kind of stuff? Scripts? Any
> > other suggestions or different ideas?
> > Kind Regards,
> > Ray- Hide quoted text -
> - Show quoted text -
Thank you very much!
Monday, March 19, 2012
Best Practice Question (clustering and remote locations access)
We have a SQL server here in Portland, we have a new office in Philadelphia
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
Scott
Hi
If your comms are reliable and have the capacity and response times then
maintaining the single cluster will be the simplest solutions.
Having an internet/intranet based application would be an alternative,
similar a citrix type solution may be another option to consider.
John
"Scott McDonald" wrote:
> We have a SQL server here in Portland, we have a new office in Philadelphia
> and we need to have both locations working off the same live data.
> Regardless we will be clustering the SQL server here, but if we have a fibre
> line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
> would be the best thing to do, have just the cluster here and phili works
> off of that, or add another SQL server to the phili office and have it sync
> with the ones here?
> Just wondering pros and cons of both, what would be faster & more efficient
> etc and wanted to get the opinions of some folks here. I'm not real
> concerned about redundancy or uptime at this point, we will tackle that once
> we get this first question decided on.
> Thanks!
> Scott
>
>
|||this might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
Scott
Hi
If your comms are reliable and have the capacity and response times then
maintaining the single cluster will be the simplest solutions.
Having an internet/intranet based application would be an alternative,
similar a citrix type solution may be another option to consider.
John
"Scott McDonald" wrote:
> We have a SQL server here in Portland, we have a new office in Philadelphia
> and we need to have both locations working off the same live data.
> Regardless we will be clustering the SQL server here, but if we have a fibre
> line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
> would be the best thing to do, have just the cluster here and phili works
> off of that, or add another SQL server to the phili office and have it sync
> with the ones here?
> Just wondering pros and cons of both, what would be faster & more efficient
> etc and wanted to get the opinions of some folks here. I'm not real
> concerned about redundancy or uptime at this point, we will tackle that once
> we get this first question decided on.
> Thanks!
> Scott
>
>
|||this might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
Best Practice Question (clustering and remote locations access)
We have a SQL server here in Portland, we have a new office in Philadelphia
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
Scott
Hi
If your comms are reliable and have the capacity and response times then
maintaining the single cluster will be the simplest solutions.
Having an internet/intranet based application would be an alternative,
similar a citrix type solution may be another option to consider.
John
"Scott McDonald" wrote:
> We have a SQL server here in Portland, we have a new office in Philadelphia
> and we need to have both locations working off the same live data.
> Regardless we will be clustering the SQL server here, but if we have a fibre
> line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
> would be the best thing to do, have just the cluster here and phili works
> off of that, or add another SQL server to the phili office and have it sync
> with the ones here?
> Just wondering pros and cons of both, what would be faster & more efficient
> etc and wanted to get the opinions of some folks here. I'm not real
> concerned about redundancy or uptime at this point, we will tackle that once
> we get this first question decided on.
> Thanks!
> Scott
>
>
|||this might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
Scott
Hi
If your comms are reliable and have the capacity and response times then
maintaining the single cluster will be the simplest solutions.
Having an internet/intranet based application would be an alternative,
similar a citrix type solution may be another option to consider.
John
"Scott McDonald" wrote:
> We have a SQL server here in Portland, we have a new office in Philadelphia
> and we need to have both locations working off the same live data.
> Regardless we will be clustering the SQL server here, but if we have a fibre
> line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
> would be the best thing to do, have just the cluster here and phili works
> off of that, or add another SQL server to the phili office and have it sync
> with the ones here?
> Just wondering pros and cons of both, what would be faster & more efficient
> etc and wanted to get the opinions of some folks here. I'm not real
> concerned about redundancy or uptime at this point, we will tackle that once
> we get this first question decided on.
> Thanks!
> Scott
>
>
|||this might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
Best Practice Question (clustering and remote locations access)
We have a SQL server here in Portland, we have a new office in Philadelphia
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
Scott
Hi
If your comms are reliable and have the capacity and response times then
maintaining the single cluster will be the simplest solutions.
Having an internet/intranet based application would be an alternative,
similar a citrix type solution may be another option to consider.
John
"Scott McDonald" wrote:
> We have a SQL server here in Portland, we have a new office in Philadelphia
> and we need to have both locations working off the same live data.
> Regardless we will be clustering the SQL server here, but if we have a fibre
> line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
> would be the best thing to do, have just the cluster here and phili works
> off of that, or add another SQL server to the phili office and have it sync
> with the ones here?
> Just wondering pros and cons of both, what would be faster & more efficient
> etc and wanted to get the opinions of some folks here. I'm not real
> concerned about redundancy or uptime at this point, we will tackle that once
> we get this first question decided on.
> Thanks!
> Scott
>
>
|||this might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
Scott
Hi
If your comms are reliable and have the capacity and response times then
maintaining the single cluster will be the simplest solutions.
Having an internet/intranet based application would be an alternative,
similar a citrix type solution may be another option to consider.
John
"Scott McDonald" wrote:
> We have a SQL server here in Portland, we have a new office in Philadelphia
> and we need to have both locations working off the same live data.
> Regardless we will be clustering the SQL server here, but if we have a fibre
> line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
> would be the best thing to do, have just the cluster here and phili works
> off of that, or add another SQL server to the phili office and have it sync
> with the ones here?
> Just wondering pros and cons of both, what would be faster & more efficient
> etc and wanted to get the opinions of some folks here. I'm not real
> concerned about redundancy or uptime at this point, we will tackle that once
> we get this first question decided on.
> Thanks!
> Scott
>
>
|||this might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
Best Practice Question (clustering and remote locations access)
We have a SQL server here in Portland, we have a new office in Philadelphia
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
ScottHi
If your comms are reliable and have the capacity and response times then
maintaining the single cluster will be the simplest solutions.
Having an internet/intranet based application would be an alternative,
similar a citrix type solution may be another option to consider.
John
"Scott McDonald" wrote:
> We have a SQL server here in Portland, we have a new office in Philadelphi
a
> and we need to have both locations working off the same live data.
> Regardless we will be clustering the SQL server here, but if we have a fib
re
> line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
> would be the best thing to do, have just the cluster here and phili works
> off of that, or add another SQL server to the phili office and have it syn
c
> with the ones here?
> Just wondering pros and cons of both, what would be faster & more efficien
t
> etc and wanted to get the opinions of some folks here. I'm not real
> concerned about redundancy or uptime at this point, we will tackle that on
ce
> we get this first question decided on.
> Thanks!
> Scott
>
>|||this might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
ScottHi
If your comms are reliable and have the capacity and response times then
maintaining the single cluster will be the simplest solutions.
Having an internet/intranet based application would be an alternative,
similar a citrix type solution may be another option to consider.
John
"Scott McDonald" wrote:
> We have a SQL server here in Portland, we have a new office in Philadelphi
a
> and we need to have both locations working off the same live data.
> Regardless we will be clustering the SQL server here, but if we have a fib
re
> line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
> would be the best thing to do, have just the cluster here and phili works
> off of that, or add another SQL server to the phili office and have it syn
c
> with the ones here?
> Just wondering pros and cons of both, what would be faster & more efficien
t
> etc and wanted to get the opinions of some folks here. I'm not real
> concerned about redundancy or uptime at this point, we will tackle that on
ce
> we get this first question decided on.
> Thanks!
> Scott
>
>|||this might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
Best Practice Question (clustering and remote locations access)
We have a SQL server here in Portland, we have a new office in Philadelphia
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
Scottthis might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
and we need to have both locations working off the same live data.
Regardless we will be clustering the SQL server here, but if we have a fibre
line (either will be DS3 45MB or OC3 155MB) connecting the two sites what
would be the best thing to do, have just the cluster here and phili works
off of that, or add another SQL server to the phili office and have it sync
with the ones here?
Just wondering pros and cons of both, what would be faster & more efficient
etc and wanted to get the opinions of some folks here. I'm not real
concerned about redundancy or uptime at this point, we will tackle that once
we get this first question decided on.
Thanks!
Scottthis might be a situation in which you would consider Merge Replication.
Not sure, it's a tough question.
Greg Jackson
PDX, Oregon
Thursday, March 8, 2012
Best practice
i have two databases on two different servers, one which is a live server.
What i want to do is run a query to update a table in the second server wit
h
records from the first database. would this be a select if not exists ?It can be an insert followed by a subquery which is based on a NOT exists, a
ssuming that you want to
add the rows that doesn't exist (based on some key column).
Or, it can be an update based on a JOIN (or an update with a number of corre
lated subqueries in SET,
as well as an EXISTS), if you want to update rows that already exists in the
other table, picking
column values from that other table.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Newman" <PeterNewman@.discussions.microsoft.com> wrote in message
news:B13DDBFC-4697-4DA6-B9C0-5F7A575BC8DF@.microsoft.com...
>i have two databases on two different servers, one which is a live server.
> What i want to do is run a query to update a table in the second server w
ith
> records from the first database. would this be a select if not exists ?
>
What i want to do is run a query to update a table in the second server wit
h
records from the first database. would this be a select if not exists ?It can be an insert followed by a subquery which is based on a NOT exists, a
ssuming that you want to
add the rows that doesn't exist (based on some key column).
Or, it can be an update based on a JOIN (or an update with a number of corre
lated subqueries in SET,
as well as an EXISTS), if you want to update rows that already exists in the
other table, picking
column values from that other table.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Newman" <PeterNewman@.discussions.microsoft.com> wrote in message
news:B13DDBFC-4697-4DA6-B9C0-5F7A575BC8DF@.microsoft.com...
>i have two databases on two different servers, one which is a live server.
> What i want to do is run a query to update a table in the second server w
ith
> records from the first database. would this be a select if not exists ?
>
Thursday, February 16, 2012
Being able to watch different processes from a web server.
I've got a web server that has many connections going to it. When I'm doing
debugging (sometimes I have to debug on the live server - get over it!) I'll
start up profiler to be able to see the exact SQL statement that is being
sent. Problem is, since there are a lot of users on the system and profiler
tracks them all, it just flies by and it's almost impossible to find
anything.
Is there an easy way to track the specific task for me? Remembering that
every time I connect/disconnect I'll get a different connection ID. About
the only thing I can think of is in my web site do something different when
it's me debugging (like log in as a different user) except this would be
heinous to have to go through and change all my code.
Anybody have any suggestions?
TIA - Jeff.
Hello,
Best way is to load the profiler log data in to a table and do the analysis.
As well as take a look into the server side trace.
http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
Thanks
Hari
"UJ" <fred@.nowhere.com> wrote in message
news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
> I've got a web server that has many connections going to it. When I'm
> doing debugging (sometimes I have to debug on the live server - get over
> it!) I'll start up profiler to be able to see the exact SQL statement that
> is being sent. Problem is, since there are a lot of users on the system
> and profiler tracks them all, it just flies by and it's almost impossible
> to find anything.
> Is there an easy way to track the specific task for me? Remembering that
> every time I connect/disconnect I'll get a different connection ID. About
> the only thing I can think of is in my web site do something different
> when it's me debugging (like log in as a different user) except this would
> be heinous to have to go through and change all my code.
> Anybody have any suggestions?
> TIA - Jeff.
>
|||I guess I wasn't clear. The problem is that if all of my webservices log in
as the same account, how can I pare it down to just the commands I did?
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ePZRJuyMHHA.4720@.TK2MSFTNGP03.phx.gbl...
> Hello,
> Best way is to load the profiler log data in to a table and do the
> analysis. As well as take a look into the server side trace.
> http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
>
> Thanks
> Hari
> "UJ" <fred@.nowhere.com> wrote in message
> news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
>
debugging (sometimes I have to debug on the live server - get over it!) I'll
start up profiler to be able to see the exact SQL statement that is being
sent. Problem is, since there are a lot of users on the system and profiler
tracks them all, it just flies by and it's almost impossible to find
anything.
Is there an easy way to track the specific task for me? Remembering that
every time I connect/disconnect I'll get a different connection ID. About
the only thing I can think of is in my web site do something different when
it's me debugging (like log in as a different user) except this would be
heinous to have to go through and change all my code.
Anybody have any suggestions?
TIA - Jeff.
Hello,
Best way is to load the profiler log data in to a table and do the analysis.
As well as take a look into the server side trace.
http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
Thanks
Hari
"UJ" <fred@.nowhere.com> wrote in message
news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
> I've got a web server that has many connections going to it. When I'm
> doing debugging (sometimes I have to debug on the live server - get over
> it!) I'll start up profiler to be able to see the exact SQL statement that
> is being sent. Problem is, since there are a lot of users on the system
> and profiler tracks them all, it just flies by and it's almost impossible
> to find anything.
> Is there an easy way to track the specific task for me? Remembering that
> every time I connect/disconnect I'll get a different connection ID. About
> the only thing I can think of is in my web site do something different
> when it's me debugging (like log in as a different user) except this would
> be heinous to have to go through and change all my code.
> Anybody have any suggestions?
> TIA - Jeff.
>
|||I guess I wasn't clear. The problem is that if all of my webservices log in
as the same account, how can I pare it down to just the commands I did?
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ePZRJuyMHHA.4720@.TK2MSFTNGP03.phx.gbl...
> Hello,
> Best way is to load the profiler log data in to a table and do the
> analysis. As well as take a look into the server side trace.
> http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
>
> Thanks
> Hari
> "UJ" <fred@.nowhere.com> wrote in message
> news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
>
Being able to watch different processes from a web server.
I've got a web server that has many connections going to it. When I'm doing
debugging (sometimes I have to debug on the live server - get over it!) I'll
start up profiler to be able to see the exact SQL statement that is being
sent. Problem is, since there are a lot of users on the system and profiler
tracks them all, it just flies by and it's almost impossible to find
anything.
Is there an easy way to track the specific task for me? Remembering that
every time I connect/disconnect I'll get a different connection ID. About
the only thing I can think of is in my web site do something different when
it's me debugging (like log in as a different user) except this would be
heinous to have to go through and change all my code.
Anybody have any suggestions?
TIA - Jeff.Hello,
Best way is to load the profiler log data in to a table and do the analysis.
As well as take a look into the server side trace.
http://vyaskn.tripod.com/server_sid..._sql_server.htm
Thanks
Hari
"UJ" <fred@.nowhere.com> wrote in message
news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
> I've got a web server that has many connections going to it. When I'm
> doing debugging (sometimes I have to debug on the live server - get over
> it!) I'll start up profiler to be able to see the exact SQL statement that
> is being sent. Problem is, since there are a lot of users on the system
> and profiler tracks them all, it just flies by and it's almost impossible
> to find anything.
> Is there an easy way to track the specific task for me? Remembering that
> every time I connect/disconnect I'll get a different connection ID. About
> the only thing I can think of is in my web site do something different
> when it's me debugging (like log in as a different user) except this would
> be heinous to have to go through and change all my code.
> Anybody have any suggestions?
> TIA - Jeff.
>|||I guess I wasn't clear. The problem is that if all of my webservices log in
as the same account, how can I pare it down to just the commands I did?
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ePZRJuyMHHA.4720@.TK2MSFTNGP03.phx.gbl...
> Hello,
> Best way is to load the profiler log data in to a table and do the
> analysis. As well as take a look into the server side trace.
> http://vyaskn.tripod.com/server_sid..._sql_server.htm
>
> Thanks
> Hari
> "UJ" <fred@.nowhere.com> wrote in message
> news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
>
debugging (sometimes I have to debug on the live server - get over it!) I'll
start up profiler to be able to see the exact SQL statement that is being
sent. Problem is, since there are a lot of users on the system and profiler
tracks them all, it just flies by and it's almost impossible to find
anything.
Is there an easy way to track the specific task for me? Remembering that
every time I connect/disconnect I'll get a different connection ID. About
the only thing I can think of is in my web site do something different when
it's me debugging (like log in as a different user) except this would be
heinous to have to go through and change all my code.
Anybody have any suggestions?
TIA - Jeff.Hello,
Best way is to load the profiler log data in to a table and do the analysis.
As well as take a look into the server side trace.
http://vyaskn.tripod.com/server_sid..._sql_server.htm
Thanks
Hari
"UJ" <fred@.nowhere.com> wrote in message
news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
> I've got a web server that has many connections going to it. When I'm
> doing debugging (sometimes I have to debug on the live server - get over
> it!) I'll start up profiler to be able to see the exact SQL statement that
> is being sent. Problem is, since there are a lot of users on the system
> and profiler tracks them all, it just flies by and it's almost impossible
> to find anything.
> Is there an easy way to track the specific task for me? Remembering that
> every time I connect/disconnect I'll get a different connection ID. About
> the only thing I can think of is in my web site do something different
> when it's me debugging (like log in as a different user) except this would
> be heinous to have to go through and change all my code.
> Anybody have any suggestions?
> TIA - Jeff.
>|||I guess I wasn't clear. The problem is that if all of my webservices log in
as the same account, how can I pare it down to just the commands I did?
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ePZRJuyMHHA.4720@.TK2MSFTNGP03.phx.gbl...
> Hello,
> Best way is to load the profiler log data in to a table and do the
> analysis. As well as take a look into the server side trace.
> http://vyaskn.tripod.com/server_sid..._sql_server.htm
>
> Thanks
> Hari
> "UJ" <fred@.nowhere.com> wrote in message
> news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
>
Being able to watch different processes from a web server.
I've got a web server that has many connections going to it. When I'm doing
debugging (sometimes I have to debug on the live server - get over it!) I'll
start up profiler to be able to see the exact SQL statement that is being
sent. Problem is, since there are a lot of users on the system and profiler
tracks them all, it just flies by and it's almost impossible to find
anything.
Is there an easy way to track the specific task for me? Remembering that
every time I connect/disconnect I'll get a different connection ID. About
the only thing I can think of is in my web site do something different when
it's me debugging (like log in as a different user) except this would be
heinous to have to go through and change all my code.
Anybody have any suggestions?
TIA - Jeff.Hello,
Best way is to load the profiler log data in to a table and do the analysis.
As well as take a look into the server side trace.
http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
Thanks
Hari
"UJ" <fred@.nowhere.com> wrote in message
news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
> I've got a web server that has many connections going to it. When I'm
> doing debugging (sometimes I have to debug on the live server - get over
> it!) I'll start up profiler to be able to see the exact SQL statement that
> is being sent. Problem is, since there are a lot of users on the system
> and profiler tracks them all, it just flies by and it's almost impossible
> to find anything.
> Is there an easy way to track the specific task for me? Remembering that
> every time I connect/disconnect I'll get a different connection ID. About
> the only thing I can think of is in my web site do something different
> when it's me debugging (like log in as a different user) except this would
> be heinous to have to go through and change all my code.
> Anybody have any suggestions?
> TIA - Jeff.
>|||I guess I wasn't clear. The problem is that if all of my webservices log in
as the same account, how can I pare it down to just the commands I did?
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ePZRJuyMHHA.4720@.TK2MSFTNGP03.phx.gbl...
> Hello,
> Best way is to load the profiler log data in to a table and do the
> analysis. As well as take a look into the server side trace.
> http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
>
> Thanks
> Hari
> "UJ" <fred@.nowhere.com> wrote in message
> news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
>> I've got a web server that has many connections going to it. When I'm
>> doing debugging (sometimes I have to debug on the live server - get over
>> it!) I'll start up profiler to be able to see the exact SQL statement
>> that is being sent. Problem is, since there are a lot of users on the
>> system and profiler tracks them all, it just flies by and it's almost
>> impossible to find anything.
>> Is there an easy way to track the specific task for me? Remembering that
>> every time I connect/disconnect I'll get a different connection ID. About
>> the only thing I can think of is in my web site do something different
>> when it's me debugging (like log in as a different user) except this
>> would be heinous to have to go through and change all my code.
>> Anybody have any suggestions?
>> TIA - Jeff.
>
debugging (sometimes I have to debug on the live server - get over it!) I'll
start up profiler to be able to see the exact SQL statement that is being
sent. Problem is, since there are a lot of users on the system and profiler
tracks them all, it just flies by and it's almost impossible to find
anything.
Is there an easy way to track the specific task for me? Remembering that
every time I connect/disconnect I'll get a different connection ID. About
the only thing I can think of is in my web site do something different when
it's me debugging (like log in as a different user) except this would be
heinous to have to go through and change all my code.
Anybody have any suggestions?
TIA - Jeff.Hello,
Best way is to load the profiler log data in to a table and do the analysis.
As well as take a look into the server side trace.
http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
Thanks
Hari
"UJ" <fred@.nowhere.com> wrote in message
news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
> I've got a web server that has many connections going to it. When I'm
> doing debugging (sometimes I have to debug on the live server - get over
> it!) I'll start up profiler to be able to see the exact SQL statement that
> is being sent. Problem is, since there are a lot of users on the system
> and profiler tracks them all, it just flies by and it's almost impossible
> to find anything.
> Is there an easy way to track the specific task for me? Remembering that
> every time I connect/disconnect I'll get a different connection ID. About
> the only thing I can think of is in my web site do something different
> when it's me debugging (like log in as a different user) except this would
> be heinous to have to go through and change all my code.
> Anybody have any suggestions?
> TIA - Jeff.
>|||I guess I wasn't clear. The problem is that if all of my webservices log in
as the same account, how can I pare it down to just the commands I did?
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ePZRJuyMHHA.4720@.TK2MSFTNGP03.phx.gbl...
> Hello,
> Best way is to load the profiler log data in to a table and do the
> analysis. As well as take a look into the server side trace.
> http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
>
> Thanks
> Hari
> "UJ" <fred@.nowhere.com> wrote in message
> news:OZ1vCpyMHHA.4712@.TK2MSFTNGP04.phx.gbl...
>> I've got a web server that has many connections going to it. When I'm
>> doing debugging (sometimes I have to debug on the live server - get over
>> it!) I'll start up profiler to be able to see the exact SQL statement
>> that is being sent. Problem is, since there are a lot of users on the
>> system and profiler tracks them all, it just flies by and it's almost
>> impossible to find anything.
>> Is there an easy way to track the specific task for me? Remembering that
>> every time I connect/disconnect I'll get a different connection ID. About
>> the only thing I can think of is in my web site do something different
>> when it's me debugging (like log in as a different user) except this
>> would be heinous to have to go through and change all my code.
>> Anybody have any suggestions?
>> TIA - Jeff.
>
Subscribe to:
Posts (Atom)