Backward Compatability in Yukon using backup devices?

My peers have informed me that I should no longer code my backup routine
using a backup alias via sp_addumpdevice because it is 1) Provided only for
backward compatability and 2) Will not be supported in the future.
Should I not be using a backup alias for these reasons? Yukon provides the
commands but no where have I seen where it's only there to support backward
compatability and that it is targeted to be phased out. Can someone show me
this?
Thanks.
-Cqlboy
I know nothing of dump devices going away any time soon.
Andrew J. Kelly SQL MVP
"Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
news:4332439A-418D-450F-BD94-5579374C40F3@.microsoft.com...
> My peers have informed me that I should no longer code my backup routine
> using a backup alias via sp_addumpdevice because it is 1) Provided only
> for
> backward compatability and 2) Will not be supported in the future.
> Should I not be using a backup alias for these reasons? Yukon provides
> the
> commands but no where have I seen where it's only there to support
> backward
> compatability and that it is targeted to be phased out. Can someone show
> me
> this?
> Thanks.
> -Cqlboy
|||Thanx. Thought so. My fellow peers
are misinformed.
-Cqlboy
"Andrew J. Kelly" wrote:

> I know nothing of dump devices going away any time soon.
> --
> Andrew J. Kelly SQL MVP
>
> "Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
> news:4332439A-418D-450F-BD94-5579374C40F3@.microsoft.com...
>
>
|||I'm with Andrew. Ask your colleagues for a reference. It is easy to make claims you can't back up...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
news:B4044417-68A3-401F-B1AF-7BCE37AE1BC9@.microsoft.com...[vbcol=seagreen]
> Thanx. Thought so. My fellow peers
> are misinformed.
> -Cqlboy
> "Andrew J. Kelly" wrote:

Backward Compatability in Yukon using backup devices?

My peers have informed me that I should no longer code my backup routine
using a backup alias via sp_addumpdevice because it is 1) Provided only for
backward compatability and 2) Will not be supported in the future.
Should I not be using a backup alias for these reasons? Yukon provides the
commands but no where have I seen where it's only there to support backward
compatability and that it is targeted to be phased out. Can someone show me
this?
Thanks.
-CqlboyI know nothing of dump devices going away any time soon.
Andrew J. Kelly SQL MVP
"Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
news:4332439A-418D-450F-BD94-5579374C40F3@.microsoft.com...
> My peers have informed me that I should no longer code my backup routine
> using a backup alias via sp_addumpdevice because it is 1) Provided only
> for
> backward compatability and 2) Will not be supported in the future.
> Should I not be using a backup alias for these reasons? Yukon provides
> the
> commands but no where have I seen where it's only there to support
> backward
> compatability and that it is targeted to be phased out. Can someone show
> me
> this?
> Thanks.
> -Cqlboy|||Thanx. Thought so. My fellow peers
are misinformed.
-Cqlboy
"Andrew J. Kelly" wrote:

> I know nothing of dump devices going away any time soon.
> --
> Andrew J. Kelly SQL MVP
>
> "Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
> news:4332439A-418D-450F-BD94-5579374C40F3@.microsoft.com...
>
>|||I'm with Andrew. Ask your colleagues for a reference. It is easy to make cla
ims you can't back up...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
news:B4044417-68A3-401F-B1AF-7BCE37AE1BC9@.microsoft.com...[vbcol=seagreen]
> Thanx. Thought so. My fellow peers
> are misinformed.
> -Cqlboy
> "Andrew J. Kelly" wrote:
>

Backward Compatability in Yukon using backup devices?

My peers have informed me that I should no longer code my backup routine
using a backup alias via sp_addumpdevice because it is 1) Provided only for
backward compatability and 2) Will not be supported in the future.
Should I not be using a backup alias for these reasons? Yukon provides the
commands but no where have I seen where it's only there to support backward
compatability and that it is targeted to be phased out. Can someone show me
this?
Thanks.
-CqlboyI know nothing of dump devices going away any time soon.
--
Andrew J. Kelly SQL MVP
"Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
news:4332439A-418D-450F-BD94-5579374C40F3@.microsoft.com...
> My peers have informed me that I should no longer code my backup routine
> using a backup alias via sp_addumpdevice because it is 1) Provided only
> for
> backward compatability and 2) Will not be supported in the future.
> Should I not be using a backup alias for these reasons? Yukon provides
> the
> commands but no where have I seen where it's only there to support
> backward
> compatability and that it is targeted to be phased out. Can someone show
> me
> this?
> Thanks.
> -Cqlboy|||Thanx. Thought so. My fellow peers
are misinformed.
-Cqlboy
"Andrew J. Kelly" wrote:
> I know nothing of dump devices going away any time soon.
> --
> Andrew J. Kelly SQL MVP
>
> "Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
> news:4332439A-418D-450F-BD94-5579374C40F3@.microsoft.com...
> > My peers have informed me that I should no longer code my backup routine
> > using a backup alias via sp_addumpdevice because it is 1) Provided only
> > for
> > backward compatability and 2) Will not be supported in the future.
> >
> > Should I not be using a backup alias for these reasons? Yukon provides
> > the
> > commands but no where have I seen where it's only there to support
> > backward
> > compatability and that it is targeted to be phased out. Can someone show
> > me
> > this?
> >
> > Thanks.
> >
> > -Cqlboy
>
>|||I'm with Andrew. Ask your colleagues for a reference. It is easy to make claims you can't back up...
:-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
news:B4044417-68A3-401F-B1AF-7BCE37AE1BC9@.microsoft.com...
> Thanx. Thought so. My fellow peers
> are misinformed.
> -Cqlboy
> "Andrew J. Kelly" wrote:
>> I know nothing of dump devices going away any time soon.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
>> news:4332439A-418D-450F-BD94-5579374C40F3@.microsoft.com...
>> > My peers have informed me that I should no longer code my backup routine
>> > using a backup alias via sp_addumpdevice because it is 1) Provided only
>> > for
>> > backward compatability and 2) Will not be supported in the future.
>> >
>> > Should I not be using a backup alias for these reasons? Yukon provides
>> > the
>> > commands but no where have I seen where it's only there to support
>> > backward
>> > compatability and that it is targeted to be phased out. Can someone show
>> > me
>> > this?
>> >
>> > Thanks.
>> >
>> > -Cqlboy
>>

Backup Up Remote Database

Our database is on a server provided by the web host. I would like to
backup the data from this database more often than our web host performs
backups. But since our database shares space on its server with other
companies, we are not permitted to use the Enterprise Manager Backup
utility. (The same limitation occurs with the Copy Database Wizard and with
Detach/Attach methods of backing up.)
We considered using DTS to perform the backup on a scheduled basis; we could
copy the database content to a text or Excel file, and then regenerate the
database when it necessary to recover from a lost database. However, DTS
does not completely satisfy our needs, because the structure of the database
(tables and fields) will change occasionally, and we would prefer not to
have to make corresponding changes to the DTS package (and then retest the
package) when this happens. In other words, it would be ideal if DTS could
be used to copy all fields from the database table.
What do other companies do to ensure the integrity of their data without
relying upon the hosting company?Hi
You could create your own scheduled job that runs the T-SQL backup command!
Jasper's expressmaint procedure does this an more!
http://www.sqldbatips.com/showcode.asp?ID=26
John
"Hondo" wrote:

> Our database is on a server provided by the web host. I would like to
> backup the data from this database more often than our web host performs
> backups. But since our database shares space on its server with other
> companies, we are not permitted to use the Enterprise Manager Backup
> utility. (The same limitation occurs with the Copy Database Wizard and wi
th
> Detach/Attach methods of backing up.)
> We considered using DTS to perform the backup on a scheduled basis; we cou
ld
> copy the database content to a text or Excel file, and then regenerate the
> database when it necessary to recover from a lost database. However, DTS
> does not completely satisfy our needs, because the structure of the databa
se
> (tables and fields) will change occasionally, and we would prefer not to
> have to make corresponding changes to the DTS package (and then retest the
> package) when this happens. In other words, it would be ideal if DTS coul
d
> be used to copy all fields from the database table.
> What do other companies do to ensure the integrity of their data without
> relying upon the hosting company?
>
>

Backup Up Remote Database

Our database is on a server provided by the web host. I would like to
backup the data from this database more often than our web host performs
backups. But since our database shares space on its server with other
companies, we are not permitted to use the Enterprise Manager Backup
utility. (The same limitation occurs with the Copy Database Wizard and with
Detach/Attach methods of backing up.)
We considered using DTS to perform the backup on a scheduled basis; we could
copy the database content to a text or Excel file, and then regenerate the
database when it necessary to recover from a lost database. However, DTS
does not completely satisfy our needs, because the structure of the database
(tables and fields) will change occasionally, and we would prefer not to
have to make corresponding changes to the DTS package (and then retest the
package) when this happens. In other words, it would be ideal if DTS could
be used to copy all fields from the database table.
What do other companies do to ensure the integrity of their data without
relying upon the hosting company?Hi
You could create your own scheduled job that runs the T-SQL backup command!
Jasper's expressmaint procedure does this an more!
http://www.sqldbatips.com/showcode.asp?ID=26
John
"Hondo" wrote:

> Our database is on a server provided by the web host. I would like to
> backup the data from this database more often than our web host performs
> backups. But since our database shares space on its server with other
> companies, we are not permitted to use the Enterprise Manager Backup
> utility. (The same limitation occurs with the Copy Database Wizard and wi
th
> Detach/Attach methods of backing up.)
> We considered using DTS to perform the backup on a scheduled basis; we cou
ld
> copy the database content to a text or Excel file, and then regenerate the
> database when it necessary to recover from a lost database. However, DTS
> does not completely satisfy our needs, because the structure of the databa
se
> (tables and fields) will change occasionally, and we would prefer not to
> have to make corresponding changes to the DTS package (and then retest the
> package) when this happens. In other words, it would be ideal if DTS coul
d
> be used to copy all fields from the database table.
> What do other companies do to ensure the integrity of their data without
> relying upon the hosting company?
>
>

Backup Up Remote Database

Our database is on a server provided by the web host. I would like to
backup the data from this database more often than our web host performs
backups. But since our database shares space on its server with other
companies, we are not permitted to use the Enterprise Manager Backup
utility. (The same limitation occurs with the Copy Database Wizard and with
Detach/Attach methods of backing up.)
We considered using DTS to perform the backup on a scheduled basis; we could
copy the database content to a text or Excel file, and then regenerate the
database when it necessary to recover from a lost database. However, DTS
does not completely satisfy our needs, because the structure of the database
(tables and fields) will change occasionally, and we would prefer not to
have to make corresponding changes to the DTS package (and then retest the
package) when this happens. In other words, it would be ideal if DTS could
be used to copy all fields from the database table.
What do other companies do to ensure the integrity of their data without
relying upon the hosting company?
Hi
You could create your own scheduled job that runs the T-SQL backup command!
Jasper's expressmaint procedure does this an more!
http://www.sqldbatips.com/showcode.asp?ID=26
John
"Hondo" wrote:

> Our database is on a server provided by the web host. I would like to
> backup the data from this database more often than our web host performs
> backups. But since our database shares space on its server with other
> companies, we are not permitted to use the Enterprise Manager Backup
> utility. (The same limitation occurs with the Copy Database Wizard and with
> Detach/Attach methods of backing up.)
> We considered using DTS to perform the backup on a scheduled basis; we could
> copy the database content to a text or Excel file, and then regenerate the
> database when it necessary to recover from a lost database. However, DTS
> does not completely satisfy our needs, because the structure of the database
> (tables and fields) will change occasionally, and we would prefer not to
> have to make corresponding changes to the DTS package (and then retest the
> package) when this happens. In other words, it would be ideal if DTS could
> be used to copy all fields from the database table.
> What do other companies do to ensure the integrity of their data without
> relying upon the hosting company?
>
>

Backup Up Remote Database

Our database is on a server provided by the web host. I would like to
backup the data from this database more often than our web host performs
backups. But since our database shares space on its server with other
companies, we are not permitted to use the Enterprise Manager Backup
utility. (The same limitation occurs with the Copy Database Wizard and with
Detach/Attach methods of backing up.)
We considered using DTS to perform the backup on a scheduled basis; we could
copy the database content to a text or Excel file, and then regenerate the
database when it necessary to recover from a lost database. However, DTS
does not completely satisfy our needs, because the structure of the database
(tables and fields) will change occasionally, and we would prefer not to
have to make corresponding changes to the DTS package (and then retest the
package) when this happens. In other words, it would be ideal if DTS could
be used to copy all fields from the database table.
What do other companies do to ensure the integrity of their data without
relying upon the hosting company?Hi
You could create your own scheduled job that runs the T-SQL backup command!
Jasper's expressmaint procedure does this an more!
http://www.sqldbatips.com/showcode.asp?ID=26
John
"Hondo" wrote:
> Our database is on a server provided by the web host. I would like to
> backup the data from this database more often than our web host performs
> backups. But since our database shares space on its server with other
> companies, we are not permitted to use the Enterprise Manager Backup
> utility. (The same limitation occurs with the Copy Database Wizard and with
> Detach/Attach methods of backing up.)
> We considered using DTS to perform the backup on a scheduled basis; we could
> copy the database content to a text or Excel file, and then regenerate the
> database when it necessary to recover from a lost database. However, DTS
> does not completely satisfy our needs, because the structure of the database
> (tables and fields) will change occasionally, and we would prefer not to
> have to make corresponding changes to the DTS package (and then retest the
> package) when this happens. In other words, it would be ideal if DTS could
> be used to copy all fields from the database table.
> What do other companies do to ensure the integrity of their data without
> relying upon the hosting company?
>
>