Friday, February 24, 2012
.BAK files do not show
the directory where my .bak files are nothing shows. However, if I rename
the files in windows without changing the file extension, the files show.
Once this occurs, Enterprise Manager stops responding with the following
error in the event log:
Hanging application mmc.exe, version 5.2.3790.0, hang module ntdll.dll,
version 5.2.3790.0, hang address 0x0000f67d.
Any help would be appreciated tremendously.
Hi Tony,
Try to choose "From Disk"
Regards,
Daniel
"Tony" <Tony@.discussions.microsoft.com> wrote in message
news:484BEC53-8F12-4114-8D09-77913CCCC42A@.microsoft.com...
> When attempting to restore a database, I choose "From Device" and browse
to
> the directory where my .bak files are nothing shows. However, if I rename
> the files in windows without changing the file extension, the files show.
> Once this occurs, Enterprise Manager stops responding with the following
> error in the event log:
> Hanging application mmc.exe, version 5.2.3790.0, hang module ntdll.dll,
> version 5.2.3790.0, hang address 0x0000f67d.
> Any help would be appreciated tremendously.
.BAK files do not show
the directory where my .bak files are nothing shows. However, if I rename
the files in windows without changing the file extension, the files show.
Once this occurs, Enterprise Manager stops responding with the following
error in the event log:
Hanging application mmc.exe, version 5.2.3790.0, hang module ntdll.dll,
version 5.2.3790.0, hang address 0x0000f67d.
Any help would be appreciated tremendously.Hi Tony,
Try to choose "From Disk"
Regards,
Daniel
"Tony" <Tony@.discussions.microsoft.com> wrote in message
news:484BEC53-8F12-4114-8D09-77913CCCC42A@.microsoft.com...
> When attempting to restore a database, I choose "From Device" and browse
to
> the directory where my .bak files are nothing shows. However, if I rename
> the files in windows without changing the file extension, the files show.
> Once this occurs, Enterprise Manager stops responding with the following
> error in the event log:
> Hanging application mmc.exe, version 5.2.3790.0, hang module ntdll.dll,
> version 5.2.3790.0, hang address 0x0000f67d.
> Any help would be appreciated tremendously.
.BAK files do not show
the directory where my .bak files are nothing shows. However, if I rename
the files in windows without changing the file extension, the files show.
Once this occurs, Enterprise Manager stops responding with the following
error in the event log:
Hanging application mmc.exe, version 5.2.3790.0, hang module ntdll.dll,
version 5.2.3790.0, hang address 0x0000f67d.
Any help would be appreciated tremendously.Hi Tony,
Try to choose "From Disk"
Regards,
Daniel
"Tony" <Tony@.discussions.microsoft.com> wrote in message
news:484BEC53-8F12-4114-8D09-77913CCCC42A@.microsoft.com...
> When attempting to restore a database, I choose "From Device" and browse
to
> the directory where my .bak files are nothing shows. However, if I rename
> the files in windows without changing the file extension, the files show.
> Once this occurs, Enterprise Manager stops responding with the following
> error in the event log:
> Hanging application mmc.exe, version 5.2.3790.0, hang module ntdll.dll,
> version 5.2.3790.0, hang address 0x0000f67d.
> Any help would be appreciated tremendously.
Sunday, February 19, 2012
..\MSSQL\Data\ - Directory saturated
..ldb files that are huge, some reach 21GB! while backup files don't
exceed 8MB.
I guess it's a kind of transaction log, but I'm not sure.
Can I erase them all and lose no information?
Where I configure it to avoid it to happen in the future?
Thanks in advance.Try to shrink the database. Run the SQL Server Enterprise manager.
Right-click on the database of interest and select "all tasks | shrink
database" from the context menu. Try this witthout and then with the "move
pages" option checked. Free space "holes" can develop in your database as
storage expands and rows are added/deleted/updated. Doing index maintenance
may help, too but at 8MB vs 21GB, I'm thinking it's not just sparse page
fills but wholesale extents. You could set the databases for autoshrink but
this might cause operations in your database to slow down when you weren't
expecting it. Probably better to do it on a schedule.
You might also look at the properties and see how much space is used versus
allocated. Before looking at properties, be sure to right-click on the
database and do a "refresh" to get the figures updated.
Could be your log has never been dumped and truncated. You may have to set
up a maintenance plan. Check the Administrator's guide for advice. The log
is in the .LDF file.
"Pablo" <pablopettis@.yahoo.com> wrote in message
news:47ae7cc6.0407150630.4ad7be1d@.posting.google.c om...
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\" contains .mdb and
> .ldb files that are huge, some reach 21GB! while backup files don't
> exceed 8MB.
> I guess it's a kind of transaction log, but I'm not sure.
> Can I erase them all and lose no information?
> Where I configure it to avoid it to happen in the future?
> Thanks in advance.|||Hi
Check out:
http://msdn.microsoft.com/library/d...ar_da2_1uzr.asp
If this is production machine you should think about moving the log files
onto a different set of spindles (disks/controller card) to the data files,
operating system and page file.
John
"Pablo" <pablopettis@.yahoo.com> wrote in message
news:47ae7cc6.0407150630.4ad7be1d@.posting.google.c om...
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\" contains .mdb and
> .ldb files that are huge, some reach 21GB! while backup files don't
> exceed 8MB.
> I guess it's a kind of transaction log, but I'm not sure.
> Can I erase them all and lose no information?
> Where I configure it to avoid it to happen in the future?
> Thanks in advance.