| Q: What SQL Server
security permissions are necessary to backup with SQL Backup
Manager? |
| A: The user specified in the SQL Server's
registration properties must belong to members of the
sysadmin fixed server role and the db_owner and
db_backupoperator fixed database roles. |
|
| Q: I can not find the
tempdb database , Why? |
| A: The tempdb database doesn't and shouldn't ever
be backed up. It is actually recreated every time when SQL
Server is started. |
|
| Q: When should I
backup the master database? |
|
A: If information in master has been
changed , you should backup the master database . If master
is not backed up after it changes, any changes since the
last backup will be lost if the backup is restored. For
example, if a user database is created after master is
backed up, tables and data added to the database, and then
master is restored because of a hard disk failure, the user
database will not be known to SQL Server because there are
no entries in the restored master database for this new user
database.
The types of operations that cause master to be updated, and
that require a backup to take place include:
- Creating or deleting a user database.
- If a user database grows automatically, by virtue of
the autogrow feature, to accommodate new data, this does
not affect master. Adding and deleting files and
filegroups does not affect master.
- Adding logins or other login security-related
operations.
- Database security operations, such as adding a user
to a database, do not affect master.
- Changing any server-wide or database configuration
options.
- Creating or removing backup devices.
- Using SQL Server Enterprise Manager to perform any
of these operations.
- Configuring the server for distributed queries and
remote procedure calls, such as adding linked servers,
or remote logins.
|
|
|
Q: How to rebuild the
master database? |
| A: In SQL Server installation directory , there is
a program named rebuildm.exe ,you just run this program and
follow it's instructions to rebuild the master database. |
|
| Q: After I restore the
master database , a database is missing , Why? |
A: Maybe the database will be created after master
is backed up. Because master backup set has no informaton
about the new database , after master is restored , the user
database will not be known to SQL Server . In this case , if
all database files comprising the user database still exist
on the disk(s), the user database can be created by
attaching the database files .
Just open the Query Analyzer ,and then execute the following
sql statements:(we attach pubs database as sample)
EXEC sp_attach_db @dbname = N'pubs',
@filename1 = N'C:\Program Files\Microsoft SQL
Server\MSSQL\Data\pubs.mdf',
@filename2 = N'C:\Program Files\Microsoft SQL
Server\MSSQL\Data\pubs_log.ldf' |
|
| Q: How to start SQL
Server in single-user mode? |
A: Restoring master database require SQL Server
start in single-user mode .You can execute the following
command in Start->Run :
sqlservr.exe -m
or
{SQL Server installation directory}\bin\sqlservr.exe -m |
|
| Q: Do you charge per server or per processor? |
A: At DMT we believe in keeping things
simple for our customers. We understand that per processor
licensing is more complicated for you, and means we spend
more time administering the licenses and less time
developing software. We therefore have a simple, per server
pricing and licensing model. You only need one license per
server even if you have more than one instance of SQL Server
running and even if you have a multiprocessor server.
By visiting the relevant licensing page on this website, you
can read full license details. |
|
| Q: Does SQL Backup Manager support all versions
of Microsoft SQL Server? |
| A: SQL Backup Manager works with SQL
Server 2000, MSDE, SQL Server 2005 and SQL Server 2005
Express databases. |
|
| Q: Does SQL Backup Manager need to be installed
on the same machine as SQL Server? |
| A: No. You can register servers and
run a backup or a restore remotely. |
|
| Q: Is SQL Backup Manager safe to use? |
A: Yes. Microsoft SQL Server provides
standard interfaces to third-party software vendors to
perform backups and restores. Most storage software uses
this interface to perform database backups and restores
(e.g. your tape storage software). SQL Backup Manager uses
exactly the same interfaces. It does not use any unpublished
features or APIs.
We have thoroughly tested SQL Backup Manager, running over 1
million test backups across many databases, varying in size
and complexity, and across over 30 platforms. We have also
tested on multi-processor machines writing over multiple
disks. In addition, SQL Backup Manager has undergone an
independent security assessment to ensure that it is safe to
use. |
|
| Q: What is the compression ratio like? |
| A: The achievable compression ratio is
largely dependent upon the type of data in the database. Our
testing indicates compression ratios between 50 and 95%. SQL
Backup Manager supports three compression levels. A
Compression Analyzer in the Back Up wizard is also
available; it samples data so that you can determine the
best compression for your requirements. |
|
| Q: Will my backups take less time? |
| A: Yes, you should see an increase on
performance of 10–90%, depending on your machine. This
increase in performance is related to compression and our
highly optimized I/O algorithms. |
|
| If you cannot find solution there, please, submit
request to our
support
pages. |
