Basic DB Question

I have inherited a rather huge DB and some of the tables are related and some are not...my question is For a DB in SQL server 2000 to be totally relational isnt it imperative that all the tables are linked together by some sort of key of?For good design then yes but its not essential. Relational does idicate that tables are related. But it is more that they can be, they don't have to be. If the tables contain related data i.e. orders, customers etc then one would suggest that they should contain keys for the related tables.

backups getting huge

Is replication suppose to continually grow the database backups on the
distribution machine? I had to remove replication because the backups grew a
couple gig in about a months time. Am I missing something? I've tried this
twice now with the same results. Thanks.
for merge it may. For transactional it shouldn't if your log reader agent is
running frequently.
Hilary Cotter
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
"s" <s@.discussions.microsoft.com> wrote in message
news:9B0AD4A6-D102-486C-9FAF-9091B954E9A3@.microsoft.com...
> Is replication suppose to continually grow the database backups on the
> distribution machine? I had to remove replication because the backups grew
a
> couple gig in about a months time. Am I missing something? I've tried this
> twice now with the same results. Thanks.
|||Thanks for the reply. I was using snapshot replication. Would this also
create continually growing backups? Is there any way to get around this
effect?
"Hilary Cotter" wrote:

> for merge it may. For transactional it shouldn't if your log reader agent is
> running frequently.
> --
> Hilary Cotter
> 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
> "s" <s@.discussions.microsoft.com> wrote in message
> news:9B0AD4A6-D102-486C-9FAF-9091B954E9A3@.microsoft.com...
> a
>
>

Backup to NULL

Hi,
I have a database that was left with recovery set to full and receving a lot
of updates. Log file has become huge but there were no transaction log
backups being done. Until I needed to trim the transaction log file now
being 25 GB (data file is only 1.5GB) because there is no more space in the
drive.
To be able to shrink it I plan to back it up first, then change the recovery
from full to simple and then shrink the log file. My problem is I don't have
any more disk space to hold the transaction log backup. Is there a way to
just backup the 20GB+ transaction log to the great void? Null? or wherever?
Please share me your insights, comments and suggestion are welcome.
TIA.
CarloVino
...
You can specify WITH TRUNCATE_ONLY on the BACKUP LOG command so that
committed data are removed from the log without creating a backup file.
Then shrink the log file to the desired size.
Afterwards, backup the database and schedule regular transaction log backups
to keep your log size reasonable.
Hope this helps.
Dan Guzman
SQL Server MVP
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:06741C7C-D44A-4D7E-B65B-8F2E8C23B7B1@.microsoft.com...
> Hi,
> I have a database that was left with recovery set to full and receving a
> lot
> of updates. Log file has become huge but there were no transaction log
> backups being done. Until I needed to trim the transaction log file now
> being 25 GB (data file is only 1.5GB) because there is no more space in
> the
> drive.
> To be able to shrink it I plan to back it up first, then change the
> recovery
> from full to simple and then shrink the log file. My problem is I don't
> have
> any more disk space to hold the transaction log backup. Is there a way to
> just backup the 20GB+ transaction log to the great void? Null? or
> wherever?
> Please share me your insights, comments and suggestion are welcome.
> TIA.
> CarloVino
> --
> ...
|||BACKUP LOG MyDatabase with TRUNCATE_ONLY. Look it up in BOL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:06741C7C-D44A-4D7E-B65B-8F2E8C23B7B1@.microsoft.com...
> Hi,
> I have a database that was left with recovery set to full and receving a
> lot
> of updates. Log file has become huge but there were no transaction log
> backups being done. Until I needed to trim the transaction log file now
> being 25 GB (data file is only 1.5GB) because there is no more space in
> the
> drive.
> To be able to shrink it I plan to back it up first, then change the
> recovery
> from full to simple and then shrink the log file. My problem is I don't
> have
> any more disk space to hold the transaction log backup. Is there a way to
> just backup the 20GB+ transaction log to the great void? Null? or
> wherever?
> Please share me your insights, comments and suggestion are welcome.
> TIA.
> CarloVino
> --
> ...

Backup to NULL

Hi,
I have a database that was left with recovery set to full and receving a lot
of updates. Log file has become huge but there were no transaction log
backups being done. Until I needed to trim the transaction log file now
being 25 GB (data file is only 1.5GB) because there is no more space in the
drive.
To be able to shrink it I plan to back it up first, then change the recovery
from full to simple and then shrink the log file. My problem is I don't have
any more disk space to hold the transaction log backup. Is there a way to
just backup the 20GB+ transaction log to the great void? Null? or wherever?
Please share me your insights, comments and suggestion are welcome.
TIA.
CarloVino
--
...You can specify WITH TRUNCATE_ONLY on the BACKUP LOG command so that
committed data are removed from the log without creating a backup file.
Then shrink the log file to the desired size.
Afterwards, backup the database and schedule regular transaction log backups
to keep your log size reasonable.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:06741C7C-D44A-4D7E-B65B-8F2E8C23B7B1@.microsoft.com...
> Hi,
> I have a database that was left with recovery set to full and receving a
> lot
> of updates. Log file has become huge but there were no transaction log
> backups being done. Until I needed to trim the transaction log file now
> being 25 GB (data file is only 1.5GB) because there is no more space in
> the
> drive.
> To be able to shrink it I plan to back it up first, then change the
> recovery
> from full to simple and then shrink the log file. My problem is I don't
> have
> any more disk space to hold the transaction log backup. Is there a way to
> just backup the 20GB+ transaction log to the great void? Null? or
> wherever?
> Please share me your insights, comments and suggestion are welcome.
> TIA.
> CarloVino
> --
> ...|||BACKUP LOG MyDatabase with TRUNCATE_ONLY. Look it up in BOL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:06741C7C-D44A-4D7E-B65B-8F2E8C23B7B1@.microsoft.com...
> Hi,
> I have a database that was left with recovery set to full and receving a
> lot
> of updates. Log file has become huge but there were no transaction log
> backups being done. Until I needed to trim the transaction log file now
> being 25 GB (data file is only 1.5GB) because there is no more space in
> the
> drive.
> To be able to shrink it I plan to back it up first, then change the
> recovery
> from full to simple and then shrink the log file. My problem is I don't
> have
> any more disk space to hold the transaction log backup. Is there a way to
> just backup the 20GB+ transaction log to the great void? Null? or
> wherever?
> Please share me your insights, comments and suggestion are welcome.
> TIA.
> CarloVino
> --
> ...

Backup to NULL

Hi,
I have a database that was left with recovery set to full and receving a lot
of updates. Log file has become huge but there were no transaction log
backups being done. Until I needed to trim the transaction log file now
being 25 GB (data file is only 1.5GB) because there is no more space in the
drive.
To be able to shrink it I plan to back it up first, then change the recovery
from full to simple and then shrink the log file. My problem is I don't hav
e
any more disk space to hold the transaction log backup. Is there a way to
just backup the 20GB+ transaction log to the great void? Null? or wherever?
Please share me your insights, comments and suggestion are welcome.
TIA.
CarloVino
--
...You can specify WITH TRUNCATE_ONLY on the BACKUP LOG command so that
committed data are removed from the log without creating a backup file.
Then shrink the log file to the desired size.
Afterwards, backup the database and schedule regular transaction log backups
to keep your log size reasonable.
Hope this helps.
Dan Guzman
SQL Server MVP
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:06741C7C-D44A-4D7E-B65B-8F2E8C23B7B1@.microsoft.com...
> Hi,
> I have a database that was left with recovery set to full and receving a
> lot
> of updates. Log file has become huge but there were no transaction log
> backups being done. Until I needed to trim the transaction log file now
> being 25 GB (data file is only 1.5GB) because there is no more space in
> the
> drive.
> To be able to shrink it I plan to back it up first, then change the
> recovery
> from full to simple and then shrink the log file. My problem is I don't
> have
> any more disk space to hold the transaction log backup. Is there a way to
> just backup the 20GB+ transaction log to the great void? Null? or
> wherever?
> Please share me your insights, comments and suggestion are welcome.
> TIA.
> CarloVino
> --
> ...|||BACKUP LOG MyDatabase with TRUNCATE_ONLY. Look it up in BOL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:06741C7C-D44A-4D7E-B65B-8F2E8C23B7B1@.microsoft.com...
> Hi,
> I have a database that was left with recovery set to full and receving a
> lot
> of updates. Log file has become huge but there were no transaction log
> backups being done. Until I needed to trim the transaction log file now
> being 25 GB (data file is only 1.5GB) because there is no more space in
> the
> drive.
> To be able to shrink it I plan to back it up first, then change the
> recovery
> from full to simple and then shrink the log file. My problem is I don't
> have
> any more disk space to hold the transaction log backup. Is there a way to
> just backup the 20GB+ transaction log to the great void? Null? or
> wherever?
> Please share me your insights, comments and suggestion are welcome.
> TIA.
> CarloVino
> --
> ...