Efficient SQL Backup?

Hi all,
I am having issues of efficiency of backing up data from one SQL data
base to another.
The two servers in questions are on different networks , behind
different firewalls. We have MS SQL 2000.
On the source data i run a job with the following steps:
1> take trans backup every 4 hrs
2> ftp to the remote server
3> if ftp fails , disable the whole job
On the target server I run a job which does the following
1> restore the trans backup with NORECOVERY.
If the job fails at target. I will have to go through the whole process
of doing a complete backup of the source , restoring it at the other
ens and then starting trans-backup again.
Also, if we do a failover to the target server, then when we roll back
to the source server again we have to da a back-up of the target and
restore it on the source server.
Is ther a more efficent way of doing this'Actually, no. This is pretty much what Log Shipping does. If you failover
to the remote and then want to failback to the primary, then you have to get
all of the data from the remote to the primary which means a backup/restore
cycle.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
<bajaj.vishal@.gmail.com> wrote in message
news:1145456580.413687.286110@.t31g2000cwb.googlegroups.com...
> Hi all,
> I am having issues of efficiency of backing up data from one SQL data
> base to another.
> The two servers in questions are on different networks , behind
> different firewalls. We have MS SQL 2000.
> On the source data i run a job with the following steps:
> 1> take trans backup every 4 hrs
> 2> ftp to the remote server
> 3> if ftp fails , disable the whole job
> On the target server I run a job which does the following
> 1> restore the trans backup with NORECOVERY.
> If the job fails at target. I will have to go through the whole process
> of doing a complete backup of the source , restoring it at the other
> ens and then starting trans-backup again.
> Also, if we do a failover to the target server, then when we roll back
> to the source server again we have to da a back-up of the target and
> restore it on the source server.
> Is ther a more efficent way of doing this'
>

Editing User Defined Data type

Is there an easy way to edit an existing User Defined Data type ? For instance i have a custom data type address of base type nvarchar with a length of 40, I want to increase this custom data types length to 50, is there a way to do it or is it even supported?

The SQL Server 2005 Mangement Studio does not allow you do it..is there a work around for this?

Thanks,

Krishna

There is no easy way to do this without dropping and recreating the user-defined data type. You can do this via TSQL. I do not know about the GUI. You might want to ask this question in the SQL Server Tools forum.|||

Thanks, its the same with GUI, its not editable, it just allows us to either delete them and re-create them. Also before deleting them it makes us to remove all references, so its a bit of work..

Regards,

Krishna