Basic DTS service problems, i guess...

I try to access a remote SP.
Server1 has a working DTS-service running
Server2 cannot start the DTS due to the following error:
"An error 1060 - (the specified service does not exist as an installes service) occured while performing this service operation on the MSDTC service".

Ok, I got it, the service isn't running (since I get this mess. when I'm tryin to start the service).
Can't find any service in the opsys services. Tried to reinstall the MSSQL but the MSDTC was/is allready installed.

Please help!
By the way, I'm running MSSQL 2000.

thanksIs the dtc service started ?|||Originally posted by rnealejr
Is the dtc service started ?

Nope, and that's the problem. I get the errormessage when I try to start the service in enterprise manager.
I can't find any corresponding service in the opsys services. It seems like the service isn't installed...but it is??!!

Bandwidth required for remote sites to use Sharepoint Portal se

If I have a sharepoint installation at my head office and remote
sites with users from about 20-80 need to access this Intranet.
How much bandwith is suggested to accomodate users of that size ? At
two sites I have a 768k frame relay and at the largest remote site with
about 80 users there is a 10MB wan connection to head office.
This question should be posted to the sharepoint newsgroup.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"scuba19" <scuba19@.discussions.microsoft.com> wrote in message
news:A335E9FE-5EF5-4416-8E89-6E6137A9F90A@.microsoft.com...
> If I have a sharepoint installation at my head office and remote
> sites with users from about 20-80 need to access this Intranet.
> How much bandwith is suggested to accomodate users of that size ?
> At
> two sites I have a 768k frame relay and at the largest remote site
> with
> about 80 users there is a 10MB wan connection to head office.
>

Bandwidth Required For ODBC Access

Hi,
I need to setup an ODBC link over our Internet connection between MS Access
(local) and a mysql server (Remote - the local PC has the mysql ODBC driver
installed). What kind of bandwidth requirements am I looking at? Will it
function over a 64k leased line? If this would be slow, could there be any
major impact on other uses such as web and email?
Regards,
DominicIn message <c08fh8$fmc$1$8300dec7@.news.demon.co.uk>, Dominic Martin
<dominic.martin@.dplm.co.uk> writes
>Hi,
>I need to setup an ODBC link over our Internet connection between MS Access
>(local) and a mysql server (Remote - the local PC has the mysql ODBC driver
>installed). What kind of bandwidth requirements am I looking at? Will it
>function over a 64k leased line? If this would be slow, could there be any
>major impact on other uses such as web and email?
It's certainly feasible to run an ODBC connection over a 64k link, and I
have done so. You haven't really given enough information to answer the
question. You need to know how many data requests will be issued and how
much data will have to be retrieved for each request.
You may need to consider the time distribution of the requests, will
they all occur at the same time? How long are the users willing to wait
for their data? What else will be using the line at the same time? Will
those users be prepared to wait for their data?
Bernard Peek
London, UK. DBA, Manager, Trainer & Author. Will work for money.|||"Bernard Peek" <bap@.shrdlu.com> wrote in message
> It's certainly feasible to run an ODBC connection over a 64k link, and I
> have done so. You haven't really given enough information to answer the
> question. You need to know how many data requests will be issued and how
> much data will have to be retrieved for each request.
> You may need to consider the time distribution of the requests, will
> they all occur at the same time? How long are the users willing to wait
> for their data? What else will be using the line at the same time? Will
> those users be prepared to wait for their data?
>
Thank you for your response. The ODBC access will supplement web based
access, where the web server will be on the same local network as the MySQL
server. The web access will be used mostly for simple queries. The ODBC
access is to be used for more complex ad-hoc queries. So in answer to your
questions, only one person is ever likely to access the mysql database via
ODBC at a time. The reports do not need to be done instantly, so time is not
too much of a worry.
I'm assuming that these are all good answers. What number of users and level
of data did you pass over the 64k link?
Dominic

> Bernard Peek
> London, UK. DBA, Manager, Trainer & Author. Will work for money.
>|||In message <c08skf$b2a$1$8300dec7@.news.demon.co.uk>, Dominic Martin
<dominic.martin@.dplm.co.uk> writes
>"Bernard Peek" <bap@.shrdlu.com> wrote in message
>Thank you for your response. The ODBC access will supplement web based
>access, where the web server will be on the same local network as the MySQL
>server. The web access will be used mostly for simple queries. The ODBC
>access is to be used for more complex ad-hoc queries. So in answer to your
>questions, only one person is ever likely to access the mysql database via
>ODBC at a time. The reports do not need to be done instantly, so time is no
t
>too much of a worry.
>I'm assuming that these are all good answers. What number of users and leve
l
>of data did you pass over the 64k link?
You can work out the data capacity of the link by looking at the
structure of the tables returned and the number of records retrieved.
The number of users isn't important, just the amount of data they use.
That's very difficult to predict with ad hoc reports. Either the person
creating the reports needs to understand the bandwidth they have
available or you have to find a way of saving bandwidth. Have you
considered replicating the mysql database to a local server?
Bernard Peek
London, UK. DBA, Manager, Trainer & Author. Will work for money.|||I have done some work on a database using ODBC over a 64K leased line. The
people paying the bills thought it was "acceptable", but the actual users
thought it abominable. The users didn't find it acceptable until the lines
(one each to three separate user locations) were upgraded from 64KB to T-1
(which is about 1.5MB, as I recall).
A better-written application would have performed better, but the same
people paying the bills wouldn't pay for some obvious improvements, such as
opening the main/first form on a single record rather than on an entire
15,000 record table. But only parts of the app were so poorly
designed/implemented.
Larry Linson
Microsoft Access MVP|||I have done so over ADSL lines (128k upload).
Adhoc queries that returned resonable amounts of data felt OK to me. The
important point is to send the query to the server and have it do the grunt
work - avoiding queries where raw data is returned to Access while it does
the grunt work. However the typical Access form performed substantially
worst - edge of usability.
When you try going long distances or overseas (large latency in the
internet - distance being defined as #routers, hops etc. as opposed to miles
per-se) then things become very bad, because by default Access does not take
care to minimize the amount of round-tripping. So the time is multiple
latency plus data transfer.
"Dominic Martin" <dominic.martin@.dplm.co.uk> wrote in message
news:c08fh8$fmc$1$8300dec7@.news.demon.co.uk...
> Hi,
> I need to setup an ODBC link over our Internet connection between MS
Access
> (local) and a mysql server (Remote - the local PC has the mysql ODBC
driver
> installed). What kind of bandwidth requirements am I looking at? Will it
> function over a 64k leased line? If this would be slow, could there be any
> major impact on other uses such as web and email?
> Regards,
> Dominic
>|||"Bernard Peek" <bap@.shrdlu.com> wrote in message
news:I2QLbrERt$JAFwgF@.shrdlu.com...
> In message <c08skf$b2a$1$8300dec7@.news.demon.co.uk>, Dominic Martin
> <dominic.martin@.dplm.co.uk> writes
I
how
MySQL
your
via
not
level
> You can work out the data capacity of the link by looking at the
> structure of the tables returned and the number of records retrieved.
> The number of users isn't important, just the amount of data they use.
> That's very difficult to predict with ad hoc reports. Either the person
> creating the reports needs to understand the bandwidth they have
> available or you have to find a way of saving bandwidth. Have you
> considered replicating the mysql database to a local server?
>
Yes, but the mysql server is a hosted solution, so we're limited in the ways
that we can get hold of the data. It's either CSV copies of the tables or
the ODBC read only link to the live data. Apart from setting up a SQL server
locally, I'm not sure what else we would need to do. Are you suggesting that
the local SQL server would use ODBC just to make straight copies of the data
or that we would have to download and manually import the CSV files? Under
the latter, it is more likely that we would just import the CSV files
directly into MS Access.
When you say you can work out the data capacity of the link, is there a
rough formula that can be applied. i.e. a certain number of records from a
certain number of tables would require x amount of bandwidth?
Thank you for your continuing help.
Dominic

> --
> Bernard Peek
> London, UK. DBA, Manager, Trainer & Author. Will work for money.
>|||"User" <User@.aol.com> wrote in message
news:OWEP6Y57DHA.2656@.TK2MSFTNGP11.phx.gbl...
> I have done so over ADSL lines (128k upload).
> Adhoc queries that returned resonable amounts of data felt OK to me. The
> important point is to send the query to the server and have it do the
grunt
> work - avoiding queries where raw data is returned to Access while it does
> the grunt work. However the typical Access form performed substantially
> worst - edge of usability.
Thank you for your comments. How do you ensure that the query is sent to the
server to do the work and not have the raw data returned to Access? Is it
something that you have to build into the query?
Dominic

> When you try going long distances or overseas (large latency in the
> internet - distance being defined as #routers, hops etc. as opposed to
miles
> per-se) then things become very bad, because by default Access does not
take
> care to minimize the amount of round-tripping. So the time is multiple
> latency plus data transfer.
>
> "Dominic Martin" <dominic.martin@.dplm.co.uk> wrote in message
> news:c08fh8$fmc$1$8300dec7@.news.demon.co.uk...
> Access
> driver
any
>|||In message <c0a2mq$onm$1$8300dec7@.news.demon.co.uk>, Dominic Martin
<dominic.martin@.dplm.co.uk> writes

>Yes, but the mysql server is a hosted solution, so we're limited in the way
s
>that we can get hold of the data. It's either CSV copies of the tables or
>the ODBC read only link to the live data. Apart from setting up a SQL serve
r
>locally, I'm not sure what else we would need to do. Are you suggesting tha
t
>the local SQL server would use ODBC just to make straight copies of the dat
a
>or that we would have to download and manually import the CSV files? Under
>the latter, it is more likely that we would just import the CSV files
>directly into MS Access.
MySQL supports replication, so that any changes to a master database are
automatically copied to a slave database. You would keep the master
database on the server and run all of your queries against the slave
kept on your own site. You need to talk to your hosting provider about
that, they may have other customers doing the same thing.
If your data changes slowly it may be OK to copy the data to CVS files
once per day and to copy them when the 64k bandwidth isn't being used
for anything else, perhaps overnight. That way you could run queries
against a database that is less than 24 hours old and not need to use
bandwidth during the day.

>When you say you can work out the data capacity of the link, is there a
>rough formula that can be applied. i.e. a certain number of records from a
>certain number of tables would require x amount of bandwidth?
The amount of data to transfer depends on the size of the records. List
the fields in each table and determine the number of bytes required for
each of them. Multiply that by the number of records retrieved. Decide
how long it will take to transfer that data over a 64Kbit (8Kbyte) per
second link. Take account of other people using the same link for other
purposes.
Bernard Peek
London, UK. DBA, Manager, Trainer & Author. Will work for money.

Backups/Restores of remote hosted SQL Server to Local?

Is there any way to backup a remote SQL Server that is on a hosted account to a local drive? We have a web hosted account that has a SQL Server that we do not have full admin rights on, just dbo access to the data and structure. We would like to be able to do backups and restores to our local development server if possible. Perhaps vis DTS or some similar means? WE cannot use the normal backup/restore as we do not have right to these fucntions nor can we access the servers local drives directly.You could certinly use DTS to transfer all objects from one server to another, presuming that the host allows SQL Server access through their firewall.|||

Yes the yallow that and support DTS packages.

Wha tis the best way to configure these to allow transferrring all data and objects? What needs to be setup first in terms of an empty database, user accounts, etc for this?

Backups using SQL Server

Is it possible to backup a remote SQL Server database to my local system? It is not working for me as I'm getting error as given below

Cannot open backup device 'path'. Device error or device offline

Any idea??

No. MSSQL only backs up locally. You could have it save to an ftp directory and download it that way.

Have a good day.|||

I tried but it didn't worked. Can you post the steps here?

|||I you are using the SQL Manager use should be able to right click on the database that you wish to back up and hover over all tasks. Then select backup, This will bring up the screen for backups. On that screen click the select device button and set the device to the directory that you want to backup to. Then name the file whatever.bak. Start the backup and you are done. Open up the folder and the file will be where you selected it to save to. If that folder is available via FTP then you can download it.

I hope that this helps.

backups through EM on remote registration

I have installed Sql Server 2000 evaluation copy on Windows XP, which I use to monitor other sql server 2000 installations (on Windows 2000) through Enterprise manager version 8.

What has been noticed is that if you try and set up a backup job through enterprise manager you do not get the option to remove inactive transaction log entries (yes the database's use full recovery models). Also if you select the verify backup option, it is not included within the job.

This is the same if you try the above on the local instance. This is not a problem as you can use the server installations, but what I am wondering is:

1. Has anyone come across this before?
2. Is it sql server 2000 on XP?
3. Is it the evaluation copy that is causing the problem?
4. Is it none of the above but indeed a far more complex reason which will mess with my head?

As always your help / knowledge is very much appreciated.As to verify, take a look at Database Maintanace Plans - there you can make it a part of your scheduled job. As to Inactive entries, actually it gets into your scheduled job, it is a default option when backing up transaction log - so you cannot see it in script that was generated by EM. Test for yourself - set up job without checking Remove inactive entries option and you can see that NO_TRUNCATE option is included in your command. Hope that it clears matters up a bit. Regards mojza|||Thanks for the reply mojza. I have no problems setting them up on the actual server, just on my PC through EM.

The verify problem is still an issue (i.e. You select it on your PC through EM but it is not part of the TSQL in the job).

However, the remove inactive transactions has got slightly stranger. On the server itself through EM, it is an option when creating a job and not touching the backup option (i.e. Database - complete is ticked by default). If you reselect it (click on it again or select another option and go back to complete) the option dissappears (which it should). Odd!!

As I said this is not really an issue but if anyone knows why I would appreciate the knowledge.|||I believe that Verify option in EM simply runs RESTORE VERIFYONLY command against backup set just completed so you can include this command plus some logic if you choose backup by T-SQL, otherwise you can set up Backup job in Database Maintanance Plan Wizard (it uses sqlmaint utility to perform its tasks which has -VrfyBackup switch to achieve backup set validation).

If 'remove inactive transactions' option is enabled in other backup type than transaction log, it's strange behavior and I've never seen that or heard about it. Evaluation edition or SQL on XP shouldn't be the cause. mojza|||The actual command it uses to berify if created on the server is:

select @.i = position from msdb..backupset where database_name='??' and type!='F' and backup_set_id=(select max(backup_set_id) from msdb..backupset where database_name='??')
RESTORE VERIFYONLY FROM [??] WITH FILE = @.i

I would be interested to know if anyone else can reproduce the 'remove inactive transactions' with a complete backup problem. Essentially all I did was right-click on the database, select backup database and under the options tab the option is there.

Backuping up Remote Databases

Hello,
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
Brian
That would require some programming. I'd look into the DMO programming API (SMO if you are on 2005).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases using T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on the remote instances and then FTP their
resulting backup files to some other server.

Backuping up Remote Databases

Hello,
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
BrianThat would require some programming. I'd look into the DMO programming API (SMO if you are on 2005).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases using T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on the remote instances and then FTP their
resulting backup files to some other server.

Backuping up Remote Databases

Hello,
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can
I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
BrianThat would require some programming. I'd look into the DMO programming API (
SMO if you are on 2005).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Ca
n I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip the
se
> files into a file so I know which machine it came from. For example after
I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3
.
> Any suggestions?
> Thanks,
> Brian|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Ca
n I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip the
se
> files into a file so I know which machine it came from. For example after
I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3
.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases us
ing T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on t
he remote instances and then FTP their
resulting backup files to some other server.

Backup/Restore MSSQL database from domain host?

My domain host provides Windows hosting, including MS SQL database.
Unfortunately it doesn't provide remote connections to their MS SQL server.
I can see no method of retrieving my database structure, or the database
populated with data, from the hosts control panel.
I'm sure that I could upload a script to my webspace that would allow me to
download and upload my database structures and data, but I have no idea
where to find a script that would allow this.
I'm hoping to be able to develop the database locally, then upload the
changes to the online database. Later I'd like to be able to download the
database to make modifications or just farm the data within them.
Any ideas?You need to ask your provider this. If they don't have a story on how you ca
n backup and get the
database and also upload such a backup, then change provider.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Noozer" <dont.spam@.me.here> wrote in message news:buMTf.164960$H%4.121289@.pd7tw2no...[colo
r=darkred]
> My domain host provides Windows hosting, including MS SQL database. Unfort
unately it doesn't
> provide remote connections to their MS SQL server. I can see no method of
retrieving my database
> structure, or the database populated with data, from the hosts control pan
el.
> I'm sure that I could upload a script to my webspace that would allow me t
o download and upload my
> database structures and data, but I have no idea where to find a script th
at would allow this.
> I'm hoping to be able to develop the database locally, then upload the cha
nges to the online
> database. Later I'd like to be able to download the database to make modif
ications or just farm
> the data within them.
> Any ideas?
>[/color]

Backup/Restore MSSQL database from domain host?

My domain host provides Windows hosting, including MS SQL database.
Unfortunately it doesn't provide remote connections to their MS SQL server.
I can see no method of retrieving my database structure, or the database
populated with data, from the hosts control panel.
I'm sure that I could upload a script to my webspace that would allow me to
download and upload my database structures and data, but I have no idea
where to find a script that would allow this.
I'm hoping to be able to develop the database locally, then upload the
changes to the online database. Later I'd like to be able to download the
database to make modifications or just farm the data within them.
Any ideas?
You need to ask your provider this. If they don't have a story on how you can backup and get the
database and also upload such a backup, then change provider.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Noozer" <dont.spam@.me.here> wrote in message news:buMTf.164960$H%4.121289@.pd7tw2no...
> My domain host provides Windows hosting, including MS SQL database. Unfortunately it doesn't
> provide remote connections to their MS SQL server. I can see no method of retrieving my database
> structure, or the database populated with data, from the hosts control panel.
> I'm sure that I could upload a script to my webspace that would allow me to download and upload my
> database structures and data, but I have no idea where to find a script that would allow this.
> I'm hoping to be able to develop the database locally, then upload the changes to the online
> database. Later I'd like to be able to download the database to make modifications or just farm
> the data within them.
> Any ideas?
>

Backup/restore Databases remotely.

Hi i've tried a few remote administration tools including Microsofts own Web Data Administrator for SQL server... but none of them seem to do what is essential to me and that is backup/restore databases to a file.
Does anyone know of a free tool that can just backup/restore databases remotely. I dont really want to have to use export/import data as things like triggers get lost when using Microsoft Web data administrator.
A free web tool written in ASP.NET or ASP would be ideal. But PHP would also be fine.
Thanks
I don't understand . Why did you say that you can not
backup/restore to a file. As long as SQL server can
access that folder, it can backup/restore to/from that
folder.
>--Original Message--
>Hi i've tried a few remote administration tools
including Microsofts own Web Data Administrator for SQL
server... but none of them seem to do what is essential
to me and that is backup/restore databases to a file.
>Does anyone know of a free tool that can just
backup/restore databases remotely. I dont really want to
have to use export/import data as things like triggers
get lost when using Microsoft Web data administrator.
>A free web tool written in ASP.NET or ASP would be
ideal. But PHP would also be fine.
>Thanks
>.
>
|||SQL server itself can backup/restore yes. But the remote web admin tool cannot.. it can only import/export data which does not include things like triggers.
See this page:
http://www.databasejournal.com/featu...0894_3330301_2
And I quote:
"Database Administration Functions missing from Web Data Administration tool
- Can't create a database backup and restore a database "
|||The article also says:
Even though these are not provided with the tool, some of
these items can be performed by using the Query tool to
submit T-SQL code to perform these tasks.
You can do backups and restores through T-SQL. In many
cases, most of what any of the tools do can be done in
T-SQL.
-Sue
On Thu, 8 Apr 2004 12:46:05 -0700, "GregD"
<anonymous@.discussions.microsoft.com> wrote:

>SQL server itself can backup/restore yes. But the remote web admin tool cannot.. it can only import/export data which does not include things like triggers.
>See this page:
>http://www.databasejournal.com/featu...0894_3330301_2
>And I quote:
>"Database Administration Functions missing from Web Data Administration tool
>- Can't create a database backup and restore a database "
|||Hi Sue,
What would the syntax be for backup/restore in TSQL? Or do you have a link where I can find this out myself?
Thanks for your help.
|||No matter found it myself on MSDN:
BACKUP DATABASE DBNameGoesHere
TO DISK = 'C:\temp\Somefilename.bak'
WITH INIT
RESTORE DATABASE DBNameGoesHere
FROM DISK = 'C:\temp\Somefilename.bak'
WITH REPLACE
|||Books Online is available within the SQL Server program group (assuming =
that you have SQL Server installed). =20
Books Online can be downloaded separately if necessary:
http://www.microsoft.com/sql/downloads/default.asp
Here is the specific link to the BOL download:
http://www.microsoft.com/sql/techinf...2000/books.asp
--=20
Keith
"GregD" <anonymous@.discussions.microsoft.com> wrote in message =
news:FBB86780-E276-4A02-B618-A7360E899FDC@.microsoft.com...
> No matter found it myself on MSDN:
>=20
> BACKUP DATABASE DBNameGoesHere
> TO DISK =3D 'C:\temp\Somefilename.bak'
> WITH INIT
>=20
> RESTORE DATABASE DBNameGoesHere
> FROM DISK =3D 'C:\temp\Somefilename.bak'
> WITH REPLACE

Backup/restore Databases remotely.

Hi i've tried a few remote administration tools including Microsofts own Web Data Administrator for SQL server... but none of them seem to do what is essential to me and that is backup/restore databases to a file.
Does anyone know of a free tool that can just backup/restore databases remotely. I dont really want to have to use export/import data as things like triggers get lost when using Microsoft Web data administrator.
A free web tool written in ASP.NET or ASP would be ideal. But PHP would also be fine.
ThanksI don't understand . Why did you say that you can not
backup/restore to a file. As long as SQL server can
access that folder, it can backup/restore to/from that
folder.
>--Original Message--
>Hi i've tried a few remote administration tools
including Microsofts own Web Data Administrator for SQL
server... but none of them seem to do what is essential
to me and that is backup/restore databases to a file.
>Does anyone know of a free tool that can just
backup/restore databases remotely. I dont really want to
have to use export/import data as things like triggers
get lost when using Microsoft Web data administrator.
>A free web tool written in ASP.NET or ASP would be
ideal. But PHP would also be fine.
>Thanks
>.
>|||SQL server itself can backup/restore yes. But the remote web admin tool cannot.. it can only import/export data which does not include things like triggers.
See this page:
http://www.databasejournal.com/features/mssql/article.php/10894_3330301_2
And I quote:
"Database Administration Functions missing from Web Data Administration tool
- Can't create a database backup and restore a database "|||The article also says:
Even though these are not provided with the tool, some of
these items can be performed by using the Query tool to
submit T-SQL code to perform these tasks.
You can do backups and restores through T-SQL. In many
cases, most of what any of the tools do can be done in
T-SQL.
-Sue
On Thu, 8 Apr 2004 12:46:05 -0700, "GregD"
<anonymous@.discussions.microsoft.com> wrote:
>SQL server itself can backup/restore yes. But the remote web admin tool cannot.. it can only import/export data which does not include things like triggers.
>See this page:
>http://www.databasejournal.com/features/mssql/article.php/10894_3330301_2
>And I quote:
>"Database Administration Functions missing from Web Data Administration tool
>- Can't create a database backup and restore a database "|||Hi Sue
What would the syntax be for backup/restore in TSQL? Or do you have a link where I can find this out myself? :
Thanks for your help.|||No matter found it myself on MSDN
BACKUP DATABASE DBNameGoesHer
TO DISK = 'C:\temp\Somefilename.bak
WITH INI
RESTORE DATABASE DBNameGoesHer
FROM DISK = 'C:\temp\Somefilename.bak
WITH REPLACE|||Books Online is available within the SQL Server program group (assuming =that you have SQL Server installed).
Books Online can be downloaded separately if necessary:
http://www.microsoft.com/sql/downloads/default.asp
Here is the specific link to the BOL download:
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
-- Keith
"GregD" <anonymous@.discussions.microsoft.com> wrote in message =news:FBB86780-E276-4A02-B618-A7360E899FDC@.microsoft.com...
> No matter found it myself on MSDN:
> > BACKUP DATABASE DBNameGoesHere
> TO DISK =3D 'C:\temp\Somefilename.bak'
> WITH INIT
> > RESTORE DATABASE DBNameGoesHere
> FROM DISK =3D 'C:\temp\Somefilename.bak'
> WITH REPLACE

Backup/restore Databases remotely.

Hi i've tried a few remote administration tools including Microsofts own Web
Data Administrator for SQL server... but none of them seem to do what is es
sential to me and that is backup/restore databases to a file.
Does anyone know of a free tool that can just backup/restore databases remot
ely. I dont really want to have to use export/import data as things like tri
ggers get lost when using Microsoft Web data administrator.
A free web tool written in ASP.NET or ASP would be ideal. But php would also
be fine.
ThanksI don't understand . Why did you say that you can not
backup/restore to a file. As long as SQL server can
access that folder, it can backup/restore to/from that
folder.
>--Original Message--
>Hi i've tried a few remote administration tools
including Microsofts own Web Data Administrator for SQL
server... but none of them seem to do what is essential
to me and that is backup/restore databases to a file.
>Does anyone know of a free tool that can just
backup/restore databases remotely. I dont really want to
have to use export/import data as things like triggers
get lost when using Microsoft Web data administrator.
>A free web tool written in ASP.NET or ASP would be
ideal. But php would also be fine.
>Thanks
>.
>|||SQL server itself can backup/restore yes. But the remote web admin tool cann
ot.. it can only import/export data which does not include things like trigg
ers.
See this page:
http://www.databasejournal.com/feat...10894_3330301_2
And I quote:
"Database Administration Functions missing from Web Data Administration tool
- Can't create a database backup and restore a database "|||The article also says:
Even though these are not provided with the tool, some of
these items can be performed by using the Query tool to
submit T-SQL code to perform these tasks.
You can do backups and restores through T-SQL. In many
cases, most of what any of the tools do can be done in
T-SQL.
-Sue
On Thu, 8 Apr 2004 12:46:05 -0700, "GregD"
<anonymous@.discussions.microsoft.com> wrote:

>SQL server itself can backup/restore yes. But the remote web admin tool can
not.. it can only import/export data which does not include things like trig
gers.
>See this page:
>http://www.databasejournal.com/feat...10894_3330301_2
>And I quote:
>"Database Administration Functions missing from Web Data Administration too
l
>- Can't create a database backup and restore a database "|||Hi Sue,
What would the syntax be for backup/restore in TSQL? Or do you have a link w
here I can find this out myself?
Thanks for your help.|||No matter found it myself on MSDN:
BACKUP DATABASE DBNameGoesHere
TO DISK = 'C:\temp\Somefilename.bak'
WITH INIT
RESTORE DATABASE DBNameGoesHere
FROM DISK = 'C:\temp\Somefilename.bak'
WITH REPLACE|||Books Online is available within the SQL Server program group (assuming =
that you have SQL Server installed). =20
Books Online can be downloaded separately if necessary:
http://www.microsoft.com/sql/downloads/default.asp
Here is the specific link to the BOL download:
http://www.microsoft.com/sql/techin.../2000/books.asp
--=20
Keith
"GregD" <anonymous@.discussions.microsoft.com> wrote in message =
news:FBB86780-E276-4A02-B618-A7360E899FDC@.microsoft.com...
> No matter found it myself on MSDN:
>=20
> BACKUP DATABASE DBNameGoesHere
> TO DISK =3D 'C:\temp\Somefilename.bak'
> WITH INIT
>=20
> RESTORE DATABASE DBNameGoesHere
> FROM DISK =3D 'C:\temp\Somefilename.bak'
> WITH REPLACE

Backup/copy to remote server

Hello,
I've spent the afternoon reading old newsgroup posts and BOL but am
still a bit confused about the best way to approach a new backup
scheme.
My organization would like to establish a single repository for backups
from our database servers, by either backing up databases on each
server and then moving them to the new, central server in some
automated fashion, or by simply pointing to the remote server as the
backup device.

>From a network performance standpoint I think backing up locally and
then copying the resulting files to a remote destination may be the
better option, as we have several servers and at least one of the
databases residing on them results in an almost 2GB backup file (with
most of the remainder smaller than that). I'm also unsure of exactly
how to go about this.
I believe SQL Server has been installed by default under the local
system account, so I'm wondering if this will limit my options with
regard to authentication across servers.
I've read about the BACKUP command, "log shipping" and other options,
but am not sure if any match our requirements.
If anyone could shine a light down the right path for me, my blood
pressure would be grateful. ;)vast55555@.yahoo.com wrote:
> Hello,
> I've spent the afternoon reading old newsgroup posts and BOL but am
> still a bit confused about the best way to approach a new backup
> scheme.
> My organization would like to establish a single repository for backups
> from our database servers, by either backing up databases on each
> server and then moving them to the new, central server in some
> automated fashion, or by simply pointing to the remote server as the
> backup device.
>
> then copying the resulting files to a remote destination may be the
> better option, as we have several servers and at least one of the
> databases residing on them results in an almost 2GB backup file (with
> most of the remainder smaller than that). I'm also unsure of exactly
> how to go about this.
> I believe SQL Server has been installed by default under the local
> system account, so I'm wondering if this will limit my options with
> regard to authentication across servers.
> I've read about the BACKUP command, "log shipping" and other options,
> but am not sure if any match our requirements.
> If anyone could shine a light down the right path for me, my blood
> pressure would be grateful. ;)
>
Create a share on your central server, configure SQL to run as a domain
user, grant that domain user permissions to the share, then use the
BACKUP command to backup directly to the UNC for that share. We move a
dozen backups around on our network each night, some of which are
approaching 200GB, there is no noticeable difference between backing up
locally and then copying vs. backing up over the network.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
Thanks for your quick response. That sounds like the way to go. One
potential problem is that this is a hosted situation--not in-house--and
I think there may be no domain, but rather isolated machines (I'm not a
network engineer by trade so I'm a bit ignorant here).
Tracy McKibben wrote:
> Create a share on your central server, configure SQL to run as a domain
> user, grant that domain user permissions to the share, then use the
> BACKUP command to backup directly to the UNC for that share. We move a
> dozen backups around on our network each night, some of which are
> approaching 200GB, there is no noticeable difference between backing up
> locally and then copying vs. backing up over the network.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Performance wise, backing up straight to a remote file share is often faster
than backing up locally and then copying the backup file to the same file
share. But there are other factors to consider. For instance, with backing u
p
straight to the remote file share, if it fails towards to the end due to som
e
network issue, the retry may take longer than just retrying the copy
operation.
Linchi
"vast55555@.yahoo.com" wrote:

> Hello,
> I've spent the afternoon reading old newsgroup posts and BOL but am
> still a bit confused about the best way to approach a new backup
> scheme.
> My organization would like to establish a single repository for backups
> from our database servers, by either backing up databases on each
> server and then moving them to the new, central server in some
> automated fashion, or by simply pointing to the remote server as the
> backup device.
>
> then copying the resulting files to a remote destination may be the
> better option, as we have several servers and at least one of the
> databases residing on them results in an almost 2GB backup file (with
> most of the remainder smaller than that). I'm also unsure of exactly
> how to go about this.
> I believe SQL Server has been installed by default under the local
> system account, so I'm wondering if this will limit my options with
> regard to authentication across servers.
> I've read about the BACKUP command, "log shipping" and other options,
> but am not sure if any match our requirements.
> If anyone could shine a light down the right path for me, my blood
> pressure would be grateful. ;)
>

Backup/copy to remote server

Hello,
I've spent the afternoon reading old newsgroup posts and BOL but am
still a bit confused about the best way to approach a new backup
scheme.
My organization would like to establish a single repository for backups
from our database servers, by either backing up databases on each
server and then moving them to the new, central server in some
automated fashion, or by simply pointing to the remote server as the
backup device.
>From a network performance standpoint I think backing up locally and
then copying the resulting files to a remote destination may be the
better option, as we have several servers and at least one of the
databases residing on them results in an almost 2GB backup file (with
most of the remainder smaller than that). I'm also unsure of exactly
how to go about this.
I believe SQL Server has been installed by default under the local
system account, so I'm wondering if this will limit my options with
regard to authentication across servers.
I've read about the BACKUP command, "log shipping" and other options,
but am not sure if any match our requirements.
If anyone could shine a light down the right path for me, my blood
pressure would be grateful. ;)vast55555@.yahoo.com wrote:
> Hello,
> I've spent the afternoon reading old newsgroup posts and BOL but am
> still a bit confused about the best way to approach a new backup
> scheme.
> My organization would like to establish a single repository for backups
> from our database servers, by either backing up databases on each
> server and then moving them to the new, central server in some
> automated fashion, or by simply pointing to the remote server as the
> backup device.
>>From a network performance standpoint I think backing up locally and
> then copying the resulting files to a remote destination may be the
> better option, as we have several servers and at least one of the
> databases residing on them results in an almost 2GB backup file (with
> most of the remainder smaller than that). I'm also unsure of exactly
> how to go about this.
> I believe SQL Server has been installed by default under the local
> system account, so I'm wondering if this will limit my options with
> regard to authentication across servers.
> I've read about the BACKUP command, "log shipping" and other options,
> but am not sure if any match our requirements.
> If anyone could shine a light down the right path for me, my blood
> pressure would be grateful. ;)
>
Create a share on your central server, configure SQL to run as a domain
user, grant that domain user permissions to the share, then use the
BACKUP command to backup directly to the UNC for that share. We move a
dozen backups around on our network each night, some of which are
approaching 200GB, there is no noticeable difference between backing up
locally and then copying vs. backing up over the network.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
Thanks for your quick response. That sounds like the way to go. One
potential problem is that this is a hosted situation--not in-house--and
I think there may be no domain, but rather isolated machines (I'm not a
network engineer by trade so I'm a bit ignorant here).
Tracy McKibben wrote:
> Create a share on your central server, configure SQL to run as a domain
> user, grant that domain user permissions to the share, then use the
> BACKUP command to backup directly to the UNC for that share. We move a
> dozen backups around on our network each night, some of which are
> approaching 200GB, there is no noticeable difference between backing up
> locally and then copying vs. backing up over the network.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Performance wise, backing up straight to a remote file share is often faster
than backing up locally and then copying the backup file to the same file
share. But there are other factors to consider. For instance, with backing up
straight to the remote file share, if it fails towards to the end due to some
network issue, the retry may take longer than just retrying the copy
operation.
Linchi
"vast55555@.yahoo.com" wrote:
> Hello,
> I've spent the afternoon reading old newsgroup posts and BOL but am
> still a bit confused about the best way to approach a new backup
> scheme.
> My organization would like to establish a single repository for backups
> from our database servers, by either backing up databases on each
> server and then moving them to the new, central server in some
> automated fashion, or by simply pointing to the remote server as the
> backup device.
> >From a network performance standpoint I think backing up locally and
> then copying the resulting files to a remote destination may be the
> better option, as we have several servers and at least one of the
> databases residing on them results in an almost 2GB backup file (with
> most of the remainder smaller than that). I'm also unsure of exactly
> how to go about this.
> I believe SQL Server has been installed by default under the local
> system account, so I'm wondering if this will limit my options with
> regard to authentication across servers.
> I've read about the BACKUP command, "log shipping" and other options,
> but am not sure if any match our requirements.
> If anyone could shine a light down the right path for me, my blood
> pressure would be grateful. ;)
>

Backup/copy to remote server

Hello,
I've spent the afternoon reading old newsgroup posts and BOL but am
still a bit confused about the best way to approach a new backup
scheme.
My organization would like to establish a single repository for backups
from our database servers, by either backing up databases on each
server and then moving them to the new, central server in some
automated fashion, or by simply pointing to the remote server as the
backup device.

>From a network performance standpoint I think backing up locally and
then copying the resulting files to a remote destination may be the
better option, as we have several servers and at least one of the
databases residing on them results in an almost 2GB backup file (with
most of the remainder smaller than that). I'm also unsure of exactly
how to go about this.
I believe SQL Server has been installed by default under the local
system account, so I'm wondering if this will limit my options with
regard to authentication across servers.
I've read about the BACKUP command, "log shipping" and other options,
but am not sure if any match our requirements.
If anyone could shine a light down the right path for me, my blood
pressure would be grateful. ;)
vast55555@.yahoo.com wrote:
> Hello,
> I've spent the afternoon reading old newsgroup posts and BOL but am
> still a bit confused about the best way to approach a new backup
> scheme.
> My organization would like to establish a single repository for backups
> from our database servers, by either backing up databases on each
> server and then moving them to the new, central server in some
> automated fashion, or by simply pointing to the remote server as the
> backup device.
> then copying the resulting files to a remote destination may be the
> better option, as we have several servers and at least one of the
> databases residing on them results in an almost 2GB backup file (with
> most of the remainder smaller than that). I'm also unsure of exactly
> how to go about this.
> I believe SQL Server has been installed by default under the local
> system account, so I'm wondering if this will limit my options with
> regard to authentication across servers.
> I've read about the BACKUP command, "log shipping" and other options,
> but am not sure if any match our requirements.
> If anyone could shine a light down the right path for me, my blood
> pressure would be grateful. ;)
>
Create a share on your central server, configure SQL to run as a domain
user, grant that domain user permissions to the share, then use the
BACKUP command to backup directly to the UNC for that share. We move a
dozen backups around on our network each night, some of which are
approaching 200GB, there is no noticeable difference between backing up
locally and then copying vs. backing up over the network.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi Tracy,
Thanks for your quick response. That sounds like the way to go. One
potential problem is that this is a hosted situation--not in-house--and
I think there may be no domain, but rather isolated machines (I'm not a
network engineer by trade so I'm a bit ignorant here).
Tracy McKibben wrote:
> Create a share on your central server, configure SQL to run as a domain
> user, grant that domain user permissions to the share, then use the
> BACKUP command to backup directly to the UNC for that share. We move a
> dozen backups around on our network each night, some of which are
> approaching 200GB, there is no noticeable difference between backing up
> locally and then copying vs. backing up over the network.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Performance wise, backing up straight to a remote file share is often faster
than backing up locally and then copying the backup file to the same file
share. But there are other factors to consider. For instance, with backing up
straight to the remote file share, if it fails towards to the end due to some
network issue, the retry may take longer than just retrying the copy
operation.
Linchi
"vast55555@.yahoo.com" wrote:

> Hello,
> I've spent the afternoon reading old newsgroup posts and BOL but am
> still a bit confused about the best way to approach a new backup
> scheme.
> My organization would like to establish a single repository for backups
> from our database servers, by either backing up databases on each
> server and then moving them to the new, central server in some
> automated fashion, or by simply pointing to the remote server as the
> backup device.
> then copying the resulting files to a remote destination may be the
> better option, as we have several servers and at least one of the
> databases residing on them results in an almost 2GB backup file (with
> most of the remainder smaller than that). I'm also unsure of exactly
> how to go about this.
> I believe SQL Server has been installed by default under the local
> system account, so I'm wondering if this will limit my options with
> regard to authentication across servers.
> I've read about the BACKUP command, "log shipping" and other options,
> but am not sure if any match our requirements.
> If anyone could shine a light down the right path for me, my blood
> pressure would be grateful. ;)
>

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?
>
>