Showing posts with label shipping. Show all posts
Showing posts with label shipping. Show all posts

Friday, March 30, 2012

Role change in log shipping

As a last step to implementing a log shipping role change...i..e making the
secondary the primary and the primary the secondary, do users change the
servernames so that apps that are referring the SQL server by host name
reflect the actual name .
We would like to implement some kind of disaster recovery using SQL 2000 log
shipping and wanted to know when we do role changes , what are the best ways
to allow the clients to still communicate to the now secondary server that
has been promoted to be the primary.I prefer the application being prepared for this. The app can for instance read the server name in a
configuration file somewhere and you quite simply change the config file to change roles.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:%232MdTFolDHA.372@.TK2MSFTNGP11.phx.gbl...
> As a last step to implementing a log shipping role change...i..e making the
> secondary the primary and the primary the secondary, do users change the
> servernames so that apps that are referring the SQL server by host name
> reflect the actual name .
> We would like to implement some kind of disaster recovery using SQL 2000 log
> shipping and wanted to know when we do role changes , what are the best ways
> to allow the clients to still communicate to the now secondary server that
> has been promoted to be the primary.
>
>|||Heelo
> As a last step to implementing a log shipping role change...i..e making
the
> secondary the primary and the primary the secondary, do users change the
> servernames so that apps that are referring the SQL server by host name
> reflect the actual name .
Sure. I'd recommend you to make an alias on DNS server
wich will always lead to your production server. In this case
you'll need to change only this alias. (But if you use large
network you'll need to propagate modifications across all
DNS servers your clients use).
Serge Shakhov

Friday, March 23, 2012

Right edition for Log shipping

We have
Svr1 - Production - SQL2K Ent Edition.(sp3a)
Svr 2 -Satellite - SQL2K Std Edition.(sp3a)
We currently have replication between Svr1 and Svr2 on a database called
'Sales' (some tables).
Now we want to have an additional 'Instance' in Svr2 to act as a Disaster
Recovery for the database Sales from Svr1 using Log shipping.
Questions:
Do we need to upgrade to Enterprise edition in Svr 2 to make Log shipping to
work? (Can I manage it with just the Resource kit)
Are there any issues to watch out for?
Thanks,
Suresh KumarI believe you Enterprise Edition for Log Shipping to work.
HTH
DeeJay
>--Original Message--
>We have
>Svr1 - Production - SQL2K Ent Edition.(sp3a)
>Svr 2 -Satellite - SQL2K Std Edition.(sp3a)
>We currently have replication between Svr1 and Svr2 on a
database called
>'Sales' (some tables).
>Now we want to have an additional 'Instance' in Svr2 to
act as a Disaster
>Recovery for the database Sales from Svr1 using Log
shipping.
>Questions:
>Do we need to upgrade to Enterprise edition in Svr 2 to
make Log shipping to
>work? (Can I manage it with just the Resource kit)
>Are there any issues to watch out for?
>Thanks,
>Suresh Kumar
>
>.
>

Monday, March 12, 2012

Reverse log shipping

We are in the planning stage of a redundant SQL environment and had a
question about log shipping.
We would like to double our use of the standby server and use it as a
pre-production server from time to time. Meaning, we would like to import
and test data on our standby server and then be able to log ship the changes
over to the primary server. Is this possible/recommended? If so, how would
it be done ?
Thanks
Nick
No.
Your better option is to move the DDL changes by script, or by using a 3rd
party tool such as Red Gate's SQL Compare.
You can move data using Script, DTS/SSIS, Red Gate's SQL Data Compare, etc.
You cannot change the data/schema in a Log Shipping Destination server
(whether its the Prod box or the standby) without Recovering it first, which
stops the Log Shipping part.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"N." <larosan@.yahoo.com> wrote in message news:wR6wh.1$_i4.0@.newsfe09.lga...
> We are in the planning stage of a redundant SQL environment and had a
> question about log shipping.
> We would like to double our use of the standby server and use it as a
> pre-production server from time to time. Meaning, we would like to import
> and test data on our standby server and then be able to log ship the
> changes over to the primary server. Is this possible/recommended? If so,
> how would it be done ?
> Thanks
> Nick
>

Tuesday, February 21, 2012

Returning different table results based upon variable

I hope this is simple and I'm just not seeing the answer.

Problem: I have two tables one with Shipping Address and one with Home Address. I want to return the Home Address unless it's empty and then I want to return the Shipping Address. The query is going to be by the stae field to narrow down results, so state=CA. If the Home Address state in not empty and state is 'CA' return address, if it is empty the return shipping address if state is 'CA'.

This is for MS SQL 2000 for planned stored procedure to display results on a webpage; Latest Service Pack also.

If I didn't need to check the null status and failover I have it working for me now. But not all records are filled out correctly and I don't want to auto-populate them.

Thank you.Okay I think I figured it out with a union statement and two selects...