I have two servers (let's call them SQL01 and SQL02), and SQL01 is our main SQL-server.
I have been doing som replication to SQL02, and I want to remove ALL replications. I have an publication on a database called DB1.
The distributor is set to be SQL02.
I used the wizard 'disable....', and stupid as I was I removed the distributor before removing the publications.
Something went wrong, and now the distributor is removed, but the publications are still there (not working, but they are there).
When I try to remove them I get the error:
'Error 2812: Could not find stored procedure ''
I am in deep trouble, and I hope that someone can help me with the problem.
Best regards...
SrenGo to the menu Tools -> Replication -> Generate SQL Script (select disable/drop components). You can use this to run to drop replication. Follow the stored procedures as listed in the order they are provided.|||Hi,
Thanks for the answer, but when I try to do that, I get the same error...
I have really messed things up, and I you have other suggestions, I would really thankful.
Sren|||Were you able to generate the script ? If so, run the script line by line - let me know where it fails - that will give us an indication as to what is broken.|||Hi,
Sorry for not writing back earlier. I have been on a businesstrip to Finland.
I unfortunately still have the problem, and if I uncheck "Distributor attributes", then I can generate the following script:
<B> use [MarliDK]
GO
-- Dropping the merge subscription
exec sp_dropmergesubscription @.publication = N'MarliDK_NEW', @.subscriber = N'ODSSQL02', @.subscriber_db = N'MarliDK', @.subscription_type = N'push'
GO
-- Dropping the merge publication
exec sp_dropmergepublication @.publication = N'MarliDK_NEW'
GO
-- Disabling the replication database
use master
GO
exec sp_replicationdboption @.dbname = N'MarliDK', @.optname = N'merge publish', @.value = N'false'
GO
</B>
When i Run the first statement I get the following:
<B> Server: Msg 2812, Level 16, State 62, Procedure sp_dropmergesubscription, Line 401
Could not find stored procedure ''.
Server: Msg 14056, Level 16, State 1, Procedure sp_dropmergesubscription, Line 444
The subscription could not be dropped at this time.</B>
I would like to thank you many times for trying to help me. I really appreciate that.
Best regards and greetings from Denmark
Sren
Showing posts with label call. Show all posts
Showing posts with label call. Show all posts
Monday, March 12, 2012
Removing replications
Labels:
call,
database,
microsoft,
mysql,
oracle,
removing,
replication,
replications,
server,
servers,
som,
sql,
sql-server,
sql01,
sql02
Friday, March 9, 2012
Removing Log File
I have a database call Runz in SQL Server 2000. When I checked the file
sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
the following:
Runz_Data.MDF 558,400 KB
Runz_Log.LDF 517,184 KB
When I checked the properties of the database in Enterprise Manager, I noted
on the General tab Size: 1050.37 MB Space Available: 718.79 MB
Data Files tab Space Allocated: 546 MB
Transaction Log tab Space Allocated: 506 MB
I am trying to save disk space on my computer. Can I delete file
Runz_Log.LDF or remove all of its data, or does it actually hold data which
exists in the tables. Is there anything else I can do to decrease the amount
of space in the files, similar to a Compact and Repair in Access?
Yes, backup the transaction log and then manually shrink it.
You may need to schedule at least daily transaction log backups.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data which
> exists in the tables. Is there anything else I can do to decrease the amount
> of space in the files, similar to a Compact and Repair in Access?
>
>
|||LDF file is an essential file of a database. It should not be deleted
otherwise you might get into bad trouble.
Every database has at least an MDF and LDF files. MDF files contain data and
LDF files contain transactions.
It can be truncated and shrinked to keep its file size under control.
If you do not take transaction log backups then that means you can tolerate
data loss so you can change your database' s recovery model to SIMPLE so the
transactions will be truncated automatically and your log file will not grow
that large.
You can find more info about recovery models from Books Online.
Ekrem ?nsoy
"rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I
> noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data
> which
> exists in the tables. Is there anything else I can do to decrease the
> amount
> of space in the files, similar to a Compact and Repair in Access?
>
>
|||Thank you
"Ekrem ?nsoy" wrote:
> LDF file is an essential file of a database. It should not be deleted
> otherwise you might get into bad trouble.
> Every database has at least an MDF and LDF files. MDF files contain data and
> LDF files contain transactions.
> It can be truncated and shrinked to keep its file size under control.
> If you do not take transaction log backups then that means you can tolerate
> data loss so you can change your database' s recovery model to SIMPLE so the
> transactions will be truncated automatically and your log file will not grow
> that large.
> You can find more info about recovery models from Books Online.
> --
> Ekrem ?nsoy
>
> "rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
> news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>
|||Thank you
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data which
> exists in the tables. Is there anything else I can do to decrease the amount
> of space in the files, similar to a Compact and Repair in Access?
>
>
sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
the following:
Runz_Data.MDF 558,400 KB
Runz_Log.LDF 517,184 KB
When I checked the properties of the database in Enterprise Manager, I noted
on the General tab Size: 1050.37 MB Space Available: 718.79 MB
Data Files tab Space Allocated: 546 MB
Transaction Log tab Space Allocated: 506 MB
I am trying to save disk space on my computer. Can I delete file
Runz_Log.LDF or remove all of its data, or does it actually hold data which
exists in the tables. Is there anything else I can do to decrease the amount
of space in the files, similar to a Compact and Repair in Access?
Yes, backup the transaction log and then manually shrink it.
You may need to schedule at least daily transaction log backups.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data which
> exists in the tables. Is there anything else I can do to decrease the amount
> of space in the files, similar to a Compact and Repair in Access?
>
>
|||LDF file is an essential file of a database. It should not be deleted
otherwise you might get into bad trouble.
Every database has at least an MDF and LDF files. MDF files contain data and
LDF files contain transactions.
It can be truncated and shrinked to keep its file size under control.
If you do not take transaction log backups then that means you can tolerate
data loss so you can change your database' s recovery model to SIMPLE so the
transactions will be truncated automatically and your log file will not grow
that large.
You can find more info about recovery models from Books Online.
Ekrem ?nsoy
"rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I
> noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data
> which
> exists in the tables. Is there anything else I can do to decrease the
> amount
> of space in the files, similar to a Compact and Repair in Access?
>
>
|||Thank you
"Ekrem ?nsoy" wrote:
> LDF file is an essential file of a database. It should not be deleted
> otherwise you might get into bad trouble.
> Every database has at least an MDF and LDF files. MDF files contain data and
> LDF files contain transactions.
> It can be truncated and shrinked to keep its file size under control.
> If you do not take transaction log backups then that means you can tolerate
> data loss so you can change your database' s recovery model to SIMPLE so the
> transactions will be truncated automatically and your log file will not grow
> that large.
> You can find more info about recovery models from Books Online.
> --
> Ekrem ?nsoy
>
> "rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
> news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>
|||Thank you
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data which
> exists in the tables. Is there anything else I can do to decrease the amount
> of space in the files, similar to a Compact and Repair in Access?
>
>
Removing Log File
I have a database call Runz in SQL Server 2000. When I checked the file
sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
the following:
Runz_Data.MDF 558,400 KB
Runz_Log.LDF 517,184 KB
When I checked the properties of the database in Enterprise Manager, I noted
on the General tab Size: 1050.37 MB Space Available: 718.79 MB
Data Files tab Space Allocated: 546 MB
Transaction Log tab Space Allocated: 506 MB
I am trying to save disk space on my computer. Can I delete file
Runz_Log.LDF or remove all of its data, or does it actually hold data which
exists in the tables. Is there anything else I can do to decrease the amoun
t
of space in the files, similar to a Compact and Repair in Access?Yes, backup the transaction log and then manually shrink it.
You may need to schedule at least daily transaction log backups.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I not
ed
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data whic
h
> exists in the tables. Is there anything else I can do to decrease the amo
unt
> of space in the files, similar to a Compact and Repair in Access?
>
>|||LDF file is an essential file of a database. It should not be deleted
otherwise you might get into bad trouble.
Every database has at least an MDF and LDF files. MDF files contain data and
LDF files contain transactions.
It can be truncated and shrinked to keep its file size under control.
If you do not take transaction log backups then that means you can tolerate
data loss so you can change your database' s recovery model to SIMPLE so the
transactions will be truncated automatically and your log file will not grow
that large.
You can find more info about recovery models from Books Online.
Ekrem ?nsoy
"rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I
> noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data
> which
> exists in the tables. Is there anything else I can do to decrease the
> amount
> of space in the files, similar to a Compact and Repair in Access?
>
>|||Thank you
"Ekrem ?nsoy" wrote:
> LDF file is an essential file of a database. It should not be deleted
> otherwise you might get into bad trouble.
> Every database has at least an MDF and LDF files. MDF files contain data a
nd
> LDF files contain transactions.
> It can be truncated and shrinked to keep its file size under control.
> If you do not take transaction log backups then that means you can tolerat
e
> data loss so you can change your database' s recovery model to SIMPLE so t
he
> transactions will be truncated automatically and your log file will not gr
ow
> that large.
> You can find more info about recovery models from Books Online.
> --
> Ekrem ?nsoy
>
> "rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
> news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>|||Thank you
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I not
ed
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data whic
h
> exists in the tables. Is there anything else I can do to decrease the amo
unt
> of space in the files, similar to a Compact and Repair in Access?
>
>
sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
the following:
Runz_Data.MDF 558,400 KB
Runz_Log.LDF 517,184 KB
When I checked the properties of the database in Enterprise Manager, I noted
on the General tab Size: 1050.37 MB Space Available: 718.79 MB
Data Files tab Space Allocated: 546 MB
Transaction Log tab Space Allocated: 506 MB
I am trying to save disk space on my computer. Can I delete file
Runz_Log.LDF or remove all of its data, or does it actually hold data which
exists in the tables. Is there anything else I can do to decrease the amoun
t
of space in the files, similar to a Compact and Repair in Access?Yes, backup the transaction log and then manually shrink it.
You may need to schedule at least daily transaction log backups.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I not
ed
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data whic
h
> exists in the tables. Is there anything else I can do to decrease the amo
unt
> of space in the files, similar to a Compact and Repair in Access?
>
>|||LDF file is an essential file of a database. It should not be deleted
otherwise you might get into bad trouble.
Every database has at least an MDF and LDF files. MDF files contain data and
LDF files contain transactions.
It can be truncated and shrinked to keep its file size under control.
If you do not take transaction log backups then that means you can tolerate
data loss so you can change your database' s recovery model to SIMPLE so the
transactions will be truncated automatically and your log file will not grow
that large.
You can find more info about recovery models from Books Online.
Ekrem ?nsoy
"rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I
> noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data
> which
> exists in the tables. Is there anything else I can do to decrease the
> amount
> of space in the files, similar to a Compact and Repair in Access?
>
>|||Thank you
"Ekrem ?nsoy" wrote:
> LDF file is an essential file of a database. It should not be deleted
> otherwise you might get into bad trouble.
> Every database has at least an MDF and LDF files. MDF files contain data a
nd
> LDF files contain transactions.
> It can be truncated and shrinked to keep its file size under control.
> If you do not take transaction log backups then that means you can tolerat
e
> data loss so you can change your database' s recovery model to SIMPLE so t
he
> transactions will be truncated automatically and your log file will not gr
ow
> that large.
> You can find more info about recovery models from Books Online.
> --
> Ekrem ?nsoy
>
> "rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
> news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>|||Thank you
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I not
ed
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data whic
h
> exists in the tables. Is there anything else I can do to decrease the amo
unt
> of space in the files, similar to a Compact and Repair in Access?
>
>
Removing Log File
I have a database call Runz in SQL Server 2000. When I checked the file
sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
the following:
Runz_Data.MDF 558,400 KB
Runz_Log.LDF 517,184 KB
When I checked the properties of the database in Enterprise Manager, I noted
on the General tab Size: 1050.37 MB Space Available: 718.79 MB
Data Files tab Space Allocated: 546 MB
Transaction Log tab Space Allocated: 506 MB
I am trying to save disk space on my computer. Can I delete file
Runz_Log.LDF or remove all of its data, or does it actually hold data which
exists in the tables. Is there anything else I can do to decrease the amount
of space in the files, similar to a Compact and Repair in Access?Yes, backup the transaction log and then manually shrink it.
You may need to schedule at least daily transaction log backups.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data which
> exists in the tables. Is there anything else I can do to decrease the amount
> of space in the files, similar to a Compact and Repair in Access?
>
>|||LDF file is an essential file of a database. It should not be deleted
otherwise you might get into bad trouble.
Every database has at least an MDF and LDF files. MDF files contain data and
LDF files contain transactions.
It can be truncated and shrinked to keep its file size under control.
If you do not take transaction log backups then that means you can tolerate
data loss so you can change your database' s recovery model to SIMPLE so the
transactions will be truncated automatically and your log file will not grow
that large.
You can find more info about recovery models from Books Online.
--
Ekrem Ã?nsoy
"rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I
> noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data
> which
> exists in the tables. Is there anything else I can do to decrease the
> amount
> of space in the files, similar to a Compact and Repair in Access?
>
>|||Thank you
"Ekrem Ã?nsoy" wrote:
> LDF file is an essential file of a database. It should not be deleted
> otherwise you might get into bad trouble.
> Every database has at least an MDF and LDF files. MDF files contain data and
> LDF files contain transactions.
> It can be truncated and shrinked to keep its file size under control.
> If you do not take transaction log backups then that means you can tolerate
> data loss so you can change your database' s recovery model to SIMPLE so the
> transactions will be truncated automatically and your log file will not grow
> that large.
> You can find more info about recovery models from Books Online.
> --
> Ekrem Ã?nsoy
>
> "rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
> news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
> >I have a database call Runz in SQL Server 2000. When I checked the file
> > sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> > the following:
> >
> > Runz_Data.MDF 558,400 KB
> > Runz_Log.LDF 517,184 KB
> >
> > When I checked the properties of the database in Enterprise Manager, I
> > noted
> > on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> > Data Files tab Space Allocated: 546 MB
> > Transaction Log tab Space Allocated: 506 MB
> >
> > I am trying to save disk space on my computer. Can I delete file
> > Runz_Log.LDF or remove all of its data, or does it actually hold data
> > which
> > exists in the tables. Is there anything else I can do to decrease the
> > amount
> > of space in the files, similar to a Compact and Repair in Access?
> >
> >
> >
> >
>|||Thank you
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data which
> exists in the tables. Is there anything else I can do to decrease the amount
> of space in the files, similar to a Compact and Repair in Access?
>
>
sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
the following:
Runz_Data.MDF 558,400 KB
Runz_Log.LDF 517,184 KB
When I checked the properties of the database in Enterprise Manager, I noted
on the General tab Size: 1050.37 MB Space Available: 718.79 MB
Data Files tab Space Allocated: 546 MB
Transaction Log tab Space Allocated: 506 MB
I am trying to save disk space on my computer. Can I delete file
Runz_Log.LDF or remove all of its data, or does it actually hold data which
exists in the tables. Is there anything else I can do to decrease the amount
of space in the files, similar to a Compact and Repair in Access?Yes, backup the transaction log and then manually shrink it.
You may need to schedule at least daily transaction log backups.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data which
> exists in the tables. Is there anything else I can do to decrease the amount
> of space in the files, similar to a Compact and Repair in Access?
>
>|||LDF file is an essential file of a database. It should not be deleted
otherwise you might get into bad trouble.
Every database has at least an MDF and LDF files. MDF files contain data and
LDF files contain transactions.
It can be truncated and shrinked to keep its file size under control.
If you do not take transaction log backups then that means you can tolerate
data loss so you can change your database' s recovery model to SIMPLE so the
transactions will be truncated automatically and your log file will not grow
that large.
You can find more info about recovery models from Books Online.
--
Ekrem Ã?nsoy
"rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
>I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I
> noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data
> which
> exists in the tables. Is there anything else I can do to decrease the
> amount
> of space in the files, similar to a Compact and Repair in Access?
>
>|||Thank you
"Ekrem Ã?nsoy" wrote:
> LDF file is an essential file of a database. It should not be deleted
> otherwise you might get into bad trouble.
> Every database has at least an MDF and LDF files. MDF files contain data and
> LDF files contain transactions.
> It can be truncated and shrinked to keep its file size under control.
> If you do not take transaction log backups then that means you can tolerate
> data loss so you can change your database' s recovery model to SIMPLE so the
> transactions will be truncated automatically and your log file will not grow
> that large.
> You can find more info about recovery models from Books Online.
> --
> Ekrem Ã?nsoy
>
> "rmcompute" <rmcompute@.discussions.microsoft.com> wrote in message
> news:4D485673-1D54-4ECA-8F7E-4203DD4CA06B@.microsoft.com...
> >I have a database call Runz in SQL Server 2000. When I checked the file
> > sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> > the following:
> >
> > Runz_Data.MDF 558,400 KB
> > Runz_Log.LDF 517,184 KB
> >
> > When I checked the properties of the database in Enterprise Manager, I
> > noted
> > on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> > Data Files tab Space Allocated: 546 MB
> > Transaction Log tab Space Allocated: 506 MB
> >
> > I am trying to save disk space on my computer. Can I delete file
> > Runz_Log.LDF or remove all of its data, or does it actually hold data
> > which
> > exists in the tables. Is there anything else I can do to decrease the
> > amount
> > of space in the files, similar to a Compact and Repair in Access?
> >
> >
> >
> >
>|||Thank you
"rmcompute" wrote:
> I have a database call Runz in SQL Server 2000. When I checked the file
> sizes in directory D:\program files\Microsoft SQL Server\MSSQL\Data, I got
> the following:
> Runz_Data.MDF 558,400 KB
> Runz_Log.LDF 517,184 KB
> When I checked the properties of the database in Enterprise Manager, I noted
> on the General tab Size: 1050.37 MB Space Available: 718.79 MB
> Data Files tab Space Allocated: 546 MB
> Transaction Log tab Space Allocated: 506 MB
> I am trying to save disk space on my computer. Can I delete file
> Runz_Log.LDF or remove all of its data, or does it actually hold data which
> exists in the tables. Is there anything else I can do to decrease the amount
> of space in the files, similar to a Compact and Repair in Access?
>
>
Subscribe to:
Posts (Atom)