Hi,
I read somewhere that you can have max 16 files in a filegroup and still be
able to detach/reattach.
Can I have several filegroups with max 16 files each and still be able to
detach/retach?
I am quite new with working with large databases. Currently I have fixed
sized datafile of 4.5GB each, enough to fit on DVD.
However, my database is growing fast and I need to create more datafiles and
still be able to detach/retach database.
Any clear insight on this would be appreciated
Thanks in advance
Christian
> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
I believe you can have up to 256 files per filegroup and up to 256
filegroups per database in SQL 2000. However, if you need to attach a
database with more than 16 files, you need to use CREATE DATABASE ... FOR
ATTACH instead of sp_attach_db. The sp_attach_db proc is basically just a
convenience wrapper for CREATE DATABASE ... FOR ATTACH but is limited to 16
files.
Hope this helps.
Dan Guzman
SQL Server MVP
"Christian Perthen" <enough@.onegrantforeachkilledspammer.com> wrote in
message news:OV%23Hb7DHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
> I am quite new with working with large databases. Currently I have fixed
> sized datafile of 4.5GB each, enough to fit on DVD.
> However, my database is growing fast and I need to create more datafiles
and
> still be able to detach/retach database.
> Any clear insight on this would be appreciated
> Thanks in advance
> Christian
>
Showing posts with label files. Show all posts
Showing posts with label files. Show all posts
Wednesday, March 28, 2012
Max files in filegroup
Hi,
I read somewhere that you can have max 16 files in a filegroup and still be
able to detach/reattach.
Can I have several filegroups with max 16 files each and still be able to
detach/retach?
I am quite new with working with large databases. Currently I have fixed
sized datafile of 4.5GB each, enough to fit on DVD.
However, my database is growing fast and I need to create more datafiles and
still be able to detach/retach database.
Any clear insight on this would be appreciated
Thanks in advance
Christian> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
I believe you can have up to 256 files per filegroup and up to 256
filegroups per database in SQL 2000. However, if you need to attach a
database with more than 16 files, you need to use CREATE DATABASE ... FOR
ATTACH instead of sp_attach_db. The sp_attach_db proc is basically just a
convenience wrapper for CREATE DATABASE ... FOR ATTACH but is limited to 16
files.
Hope this helps.
Dan Guzman
SQL Server MVP
"Christian Perthen" <enough@.onegrantforeachkilledspammer.com> wrote in
message news:OV%23Hb7DHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
> I am quite new with working with large databases. Currently I have fixed
> sized datafile of 4.5GB each, enough to fit on DVD.
> However, my database is growing fast and I need to create more datafiles
and
> still be able to detach/retach database.
> Any clear insight on this would be appreciated
> Thanks in advance
> Christian
>
I read somewhere that you can have max 16 files in a filegroup and still be
able to detach/reattach.
Can I have several filegroups with max 16 files each and still be able to
detach/retach?
I am quite new with working with large databases. Currently I have fixed
sized datafile of 4.5GB each, enough to fit on DVD.
However, my database is growing fast and I need to create more datafiles and
still be able to detach/retach database.
Any clear insight on this would be appreciated
Thanks in advance
Christian> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
I believe you can have up to 256 files per filegroup and up to 256
filegroups per database in SQL 2000. However, if you need to attach a
database with more than 16 files, you need to use CREATE DATABASE ... FOR
ATTACH instead of sp_attach_db. The sp_attach_db proc is basically just a
convenience wrapper for CREATE DATABASE ... FOR ATTACH but is limited to 16
files.
Hope this helps.
Dan Guzman
SQL Server MVP
"Christian Perthen" <enough@.onegrantforeachkilledspammer.com> wrote in
message news:OV%23Hb7DHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
> I am quite new with working with large databases. Currently I have fixed
> sized datafile of 4.5GB each, enough to fit on DVD.
> However, my database is growing fast and I need to create more datafiles
and
> still be able to detach/retach database.
> Any clear insight on this would be appreciated
> Thanks in advance
> Christian
>
Max files in filegroup
Hi,
I read somewhere that you can have max 16 files in a filegroup and still be
able to detach/reattach.
Can I have several filegroups with max 16 files each and still be able to
detach/retach?
I am quite new with working with large databases. Currently I have fixed
sized datafile of 4.5GB each, enough to fit on DVD.
However, my database is growing fast and I need to create more datafiles and
still be able to detach/retach database.
Any clear insight on this would be appreciated
Thanks in advance
Christian> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
I believe you can have up to 256 files per filegroup and up to 256
filegroups per database in SQL 2000. However, if you need to attach a
database with more than 16 files, you need to use CREATE DATABASE ... FOR
ATTACH instead of sp_attach_db. The sp_attach_db proc is basically just a
convenience wrapper for CREATE DATABASE ... FOR ATTACH but is limited to 16
files.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Christian Perthen" <enough@.onegrantforeachkilledspammer.com> wrote in
message news:OV%23Hb7DHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
> I am quite new with working with large databases. Currently I have fixed
> sized datafile of 4.5GB each, enough to fit on DVD.
> However, my database is growing fast and I need to create more datafiles
and
> still be able to detach/retach database.
> Any clear insight on this would be appreciated
> Thanks in advance
> Christian
>
I read somewhere that you can have max 16 files in a filegroup and still be
able to detach/reattach.
Can I have several filegroups with max 16 files each and still be able to
detach/retach?
I am quite new with working with large databases. Currently I have fixed
sized datafile of 4.5GB each, enough to fit on DVD.
However, my database is growing fast and I need to create more datafiles and
still be able to detach/retach database.
Any clear insight on this would be appreciated
Thanks in advance
Christian> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
I believe you can have up to 256 files per filegroup and up to 256
filegroups per database in SQL 2000. However, if you need to attach a
database with more than 16 files, you need to use CREATE DATABASE ... FOR
ATTACH instead of sp_attach_db. The sp_attach_db proc is basically just a
convenience wrapper for CREATE DATABASE ... FOR ATTACH but is limited to 16
files.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Christian Perthen" <enough@.onegrantforeachkilledspammer.com> wrote in
message news:OV%23Hb7DHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I read somewhere that you can have max 16 files in a filegroup and still
be
> able to detach/reattach.
> Can I have several filegroups with max 16 files each and still be able to
> detach/retach?
> I am quite new with working with large databases. Currently I have fixed
> sized datafile of 4.5GB each, enough to fit on DVD.
> However, my database is growing fast and I need to create more datafiles
and
> still be able to detach/retach database.
> Any clear insight on this would be appreciated
> Thanks in advance
> Christian
>
Saturday, February 25, 2012
mastlog.ldf and other locked files
Whenever I back up my laptop, I get a series of messages that the files
in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
folder such as mastlog.ldf are being used by another application. The
backup stalls until I manually tell it to skip these files.
Is there any way to identify what application is using these files?
I am running WIndows XP.
Thanks,
Dani<reachdani@.gmail.com> wrote in message
news:1131309673.446106.52540@.g44g2000cwa.googlegroups.com...
> Whenever I back up my laptop, I get a series of messages that the files
> in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
> folder such as mastlog.ldf are being used by another application. The
> backup stalls until I manually tell it to skip these files.
> Is there any way to identify what application is using these files?
> I am running WIndows XP.
> Thanks,
> Dani
>
Mastlog.ldf is the log file for master. SQL Server will open the Master
database whether or not other applications are in use.
If you want to backup SQL databases then the best way is usually to use the
SQL BACKUP command. That's doubly so for Master. If you want to back them up
via the file system then shutdown the SQL Server service first - I assume
that won't be a problem on your laptop.
--
David Portas
SQL Server MVP
--|||Hi
Looks like BCM = Business Contact Manager, a option for Microsoft Office
2003.
It seems to use MSDE to store data. MSDE is the free version of SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:kLSdnSlrKtLb4fPeRVnyuQ@.giganews.com...
> <reachdani@.gmail.com> wrote in message
> news:1131309673.446106.52540@.g44g2000cwa.googlegroups.com...
>> Whenever I back up my laptop, I get a series of messages that the files
>> in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
>> folder such as mastlog.ldf are being used by another application. The
>> backup stalls until I manually tell it to skip these files.
>> Is there any way to identify what application is using these files?
>> I am running WIndows XP.
>> Thanks,
>> Dani
> Mastlog.ldf is the log file for master. SQL Server will open the Master
> database whether or not other applications are in use.
> If you want to backup SQL databases then the best way is usually to use
> the SQL BACKUP command. That's doubly so for Master. If you want to back
> them up via the file system then shutdown the SQL Server service first - I
> assume that won't be a problem on your laptop.
> --
> David Portas
> SQL Server MVP
> --
>
in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
folder such as mastlog.ldf are being used by another application. The
backup stalls until I manually tell it to skip these files.
Is there any way to identify what application is using these files?
I am running WIndows XP.
Thanks,
Dani<reachdani@.gmail.com> wrote in message
news:1131309673.446106.52540@.g44g2000cwa.googlegroups.com...
> Whenever I back up my laptop, I get a series of messages that the files
> in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
> folder such as mastlog.ldf are being used by another application. The
> backup stalls until I manually tell it to skip these files.
> Is there any way to identify what application is using these files?
> I am running WIndows XP.
> Thanks,
> Dani
>
Mastlog.ldf is the log file for master. SQL Server will open the Master
database whether or not other applications are in use.
If you want to backup SQL databases then the best way is usually to use the
SQL BACKUP command. That's doubly so for Master. If you want to back them up
via the file system then shutdown the SQL Server service first - I assume
that won't be a problem on your laptop.
--
David Portas
SQL Server MVP
--|||Hi
Looks like BCM = Business Contact Manager, a option for Microsoft Office
2003.
It seems to use MSDE to store data. MSDE is the free version of SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:kLSdnSlrKtLb4fPeRVnyuQ@.giganews.com...
> <reachdani@.gmail.com> wrote in message
> news:1131309673.446106.52540@.g44g2000cwa.googlegroups.com...
>> Whenever I back up my laptop, I get a series of messages that the files
>> in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
>> folder such as mastlog.ldf are being used by another application. The
>> backup stalls until I manually tell it to skip these files.
>> Is there any way to identify what application is using these files?
>> I am running WIndows XP.
>> Thanks,
>> Dani
> Mastlog.ldf is the log file for master. SQL Server will open the Master
> database whether or not other applications are in use.
> If you want to backup SQL databases then the best way is usually to use
> the SQL BACKUP command. That's doubly so for Master. If you want to back
> them up via the file system then shutdown the SQL Server service first - I
> assume that won't be a problem on your laptop.
> --
> David Portas
> SQL Server MVP
> --
>
mastlog.ldf and other locked files
Whenever I back up my laptop, I get a series of messages that the files
in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
folder such as mastlog.ldf are being used by another application. The
backup stalls until I manually tell it to skip these files.
Is there any way to identify what application is using these files?
I am running WIndows XP.
Thanks,
Dani
<reachdani@.gmail.com> wrote in message
news:1131309673.446106.52540@.g44g2000cwa.googlegro ups.com...
> Whenever I back up my laptop, I get a series of messages that the files
> in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
> folder such as mastlog.ldf are being used by another application. The
> backup stalls until I manually tell it to skip these files.
> Is there any way to identify what application is using these files?
> I am running WIndows XP.
> Thanks,
> Dani
>
Mastlog.ldf is the log file for master. SQL Server will open the Master
database whether or not other applications are in use.
If you want to backup SQL databases then the best way is usually to use the
SQL BACKUP command. That's doubly so for Master. If you want to back them up
via the file system then shutdown the SQL Server service first - I assume
that won't be a problem on your laptop.
David Portas
SQL Server MVP
|||Hi
Looks like BCM = Business Contact Manager, a option for Microsoft Office
2003.
It seems to use MSDE to store data. MSDE is the free version of SQL Server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:kLSdnSlrKtLb4fPeRVnyuQ@.giganews.com...
> <reachdani@.gmail.com> wrote in message
> news:1131309673.446106.52540@.g44g2000cwa.googlegro ups.com...
> Mastlog.ldf is the log file for master. SQL Server will open the Master
> database whether or not other applications are in use.
> If you want to backup SQL databases then the best way is usually to use
> the SQL BACKUP command. That's doubly so for Master. If you want to back
> them up via the file system then shutdown the SQL Server service first - I
> assume that won't be a problem on your laptop.
> --
> David Portas
> SQL Server MVP
> --
>
in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
folder such as mastlog.ldf are being used by another application. The
backup stalls until I manually tell it to skip these files.
Is there any way to identify what application is using these files?
I am running WIndows XP.
Thanks,
Dani
<reachdani@.gmail.com> wrote in message
news:1131309673.446106.52540@.g44g2000cwa.googlegro ups.com...
> Whenever I back up my laptop, I get a series of messages that the files
> in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
> folder such as mastlog.ldf are being used by another application. The
> backup stalls until I manually tell it to skip these files.
> Is there any way to identify what application is using these files?
> I am running WIndows XP.
> Thanks,
> Dani
>
Mastlog.ldf is the log file for master. SQL Server will open the Master
database whether or not other applications are in use.
If you want to backup SQL databases then the best way is usually to use the
SQL BACKUP command. That's doubly so for Master. If you want to back them up
via the file system then shutdown the SQL Server service first - I assume
that won't be a problem on your laptop.
David Portas
SQL Server MVP
|||Hi
Looks like BCM = Business Contact Manager, a option for Microsoft Office
2003.
It seems to use MSDE to store data. MSDE is the free version of SQL Server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:kLSdnSlrKtLb4fPeRVnyuQ@.giganews.com...
> <reachdani@.gmail.com> wrote in message
> news:1131309673.446106.52540@.g44g2000cwa.googlegro ups.com...
> Mastlog.ldf is the log file for master. SQL Server will open the Master
> database whether or not other applications are in use.
> If you want to backup SQL databases then the best way is usually to use
> the SQL BACKUP command. That's doubly so for Master. If you want to back
> them up via the file system then shutdown the SQL Server service first - I
> assume that won't be a problem on your laptop.
> --
> David Portas
> SQL Server MVP
> --
>
mastlog.ldf and other locked files
Whenever I back up my laptop, I get a series of messages that the files
in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
folder such as mastlog.ldf are being used by another application. The
backup stalls until I manually tell it to skip these files.
Is there any way to identify what application is using these files?
I am running WIndows XP.
Thanks,
Dani<reachdani@.gmail.com> wrote in message
news:1131309673.446106.52540@.g44g2000cwa.googlegroups.com...
> Whenever I back up my laptop, I get a series of messages that the files
> in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
> folder such as mastlog.ldf are being used by another application. The
> backup stalls until I manually tell it to skip these files.
> Is there any way to identify what application is using these files?
> I am running WIndows XP.
> Thanks,
> Dani
>
Mastlog.ldf is the log file for master. SQL Server will open the Master
database whether or not other applications are in use.
If you want to backup SQL databases then the best way is usually to use the
SQL BACKUP command. That's doubly so for Master. If you want to back them up
via the file system then shutdown the SQL Server service first - I assume
that won't be a problem on your laptop.
David Portas
SQL Server MVP
--|||Hi
Looks like BCM = Business Contact Manager, a option for Microsoft Office
2003.
It seems to use MSDE to store data. MSDE is the free version of SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:kLSdnSlrKtLb4fPeRVnyuQ@.giganews.com...
> <reachdani@.gmail.com> wrote in message
> news:1131309673.446106.52540@.g44g2000cwa.googlegroups.com...
> Mastlog.ldf is the log file for master. SQL Server will open the Master
> database whether or not other applications are in use.
> If you want to backup SQL databases then the best way is usually to use
> the SQL BACKUP command. That's doubly so for Master. If you want to back
> them up via the file system then shutdown the SQL Server service first - I
> assume that won't be a problem on your laptop.
> --
> David Portas
> SQL Server MVP
> --
>
in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
folder such as mastlog.ldf are being used by another application. The
backup stalls until I manually tell it to skip these files.
Is there any way to identify what application is using these files?
I am running WIndows XP.
Thanks,
Dani<reachdani@.gmail.com> wrote in message
news:1131309673.446106.52540@.g44g2000cwa.googlegroups.com...
> Whenever I back up my laptop, I get a series of messages that the files
> in the C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Data
> folder such as mastlog.ldf are being used by another application. The
> backup stalls until I manually tell it to skip these files.
> Is there any way to identify what application is using these files?
> I am running WIndows XP.
> Thanks,
> Dani
>
Mastlog.ldf is the log file for master. SQL Server will open the Master
database whether or not other applications are in use.
If you want to backup SQL databases then the best way is usually to use the
SQL BACKUP command. That's doubly so for Master. If you want to back them up
via the file system then shutdown the SQL Server service first - I assume
that won't be a problem on your laptop.
David Portas
SQL Server MVP
--|||Hi
Looks like BCM = Business Contact Manager, a option for Microsoft Office
2003.
It seems to use MSDE to store data. MSDE is the free version of SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:kLSdnSlrKtLb4fPeRVnyuQ@.giganews.com...
> <reachdani@.gmail.com> wrote in message
> news:1131309673.446106.52540@.g44g2000cwa.googlegroups.com...
> Mastlog.ldf is the log file for master. SQL Server will open the Master
> database whether or not other applications are in use.
> If you want to backup SQL databases then the best way is usually to use
> the SQL BACKUP command. That's doubly so for Master. If you want to back
> them up via the file system then shutdown the SQL Server service first - I
> assume that won't be a problem on your laptop.
> --
> David Portas
> SQL Server MVP
> --
>
Monday, February 20, 2012
Master..sysaltfiles contains incorrect info
Dear all,
I had a database which contained 2 log files, one of the log files was
deleted - however, master..sysaltfiles still shows 2 log files in
existance...
The database is open, and working OK, so second log file is definately not
being used ( it no longer exists on disk)...
So how do I update master..sysaltfiles to be correct ?
I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows 2
files) . I'm loathe to do a direct delete on master..sysaltfiles until I can
discover if this kind of 'corruption' is not unknown... but do I have any
other choice ?
Hi
I don't know why you have got the extra entry, was there any message in the
SQL Server log when you re-started?
What happens when you try to remove the file using:
ALTER DATABASE database REMOVE FILE logical_file_name
John
"SteveH" <SteveH@.discussions.microsoft.com> wrote in message
news:7C75A085-7563-4D94-9E50-353ECAFF820B@.microsoft.com...
> Dear all,
> I had a database which contained 2 log files, one of the log files was
> deleted - however, master..sysaltfiles still shows 2 log files in
> existance...
> The database is open, and working OK, so second log file is definately not
> being used ( it no longer exists on disk)...
> So how do I update master..sysaltfiles to be correct ?
> I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows
> 2
> files) . I'm loathe to do a direct delete on master..sysaltfiles until I
> can
> discover if this kind of 'corruption' is not unknown... but do I have any
> other choice ?
I had a database which contained 2 log files, one of the log files was
deleted - however, master..sysaltfiles still shows 2 log files in
existance...
The database is open, and working OK, so second log file is definately not
being used ( it no longer exists on disk)...
So how do I update master..sysaltfiles to be correct ?
I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows 2
files) . I'm loathe to do a direct delete on master..sysaltfiles until I can
discover if this kind of 'corruption' is not unknown... but do I have any
other choice ?
Hi
I don't know why you have got the extra entry, was there any message in the
SQL Server log when you re-started?
What happens when you try to remove the file using:
ALTER DATABASE database REMOVE FILE logical_file_name
John
"SteveH" <SteveH@.discussions.microsoft.com> wrote in message
news:7C75A085-7563-4D94-9E50-353ECAFF820B@.microsoft.com...
> Dear all,
> I had a database which contained 2 log files, one of the log files was
> deleted - however, master..sysaltfiles still shows 2 log files in
> existance...
> The database is open, and working OK, so second log file is definately not
> being used ( it no longer exists on disk)...
> So how do I update master..sysaltfiles to be correct ?
> I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows
> 2
> files) . I'm loathe to do a direct delete on master..sysaltfiles until I
> can
> discover if this kind of 'corruption' is not unknown... but do I have any
> other choice ?
Master..sysaltfiles contains incorrect info
Dear all,
I had a database which contained 2 log files, one of the log files was
deleted - however, master..sysaltfiles still shows 2 log files in
existance...
The database is open, and working OK, so second log file is definately not
being used ( it no longer exists on disk)...
So how do I update master..sysaltfiles to be correct ?
I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows 2
files) . I'm loathe to do a direct delete on master..sysaltfiles until I can
discover if this kind of 'corruption' is not unknown... but do I have any
other choice ?Hi
I don't know why you have got the extra entry, was there any message in the
SQL Server log when you re-started?
What happens when you try to remove the file using:
ALTER DATABASE database REMOVE FILE logical_file_name
John
"SteveH" <SteveH@.discussions.microsoft.com> wrote in message
news:7C75A085-7563-4D94-9E50-353ECAFF820B@.microsoft.com...
> Dear all,
> I had a database which contained 2 log files, one of the log files was
> deleted - however, master..sysaltfiles still shows 2 log files in
> existance...
> The database is open, and working OK, so second log file is definately not
> being used ( it no longer exists on disk)...
> So how do I update master..sysaltfiles to be correct ?
> I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows
> 2
> files) . I'm loathe to do a direct delete on master..sysaltfiles until I
> can
> discover if this kind of 'corruption' is not unknown... but do I have any
> other choice ?
I had a database which contained 2 log files, one of the log files was
deleted - however, master..sysaltfiles still shows 2 log files in
existance...
The database is open, and working OK, so second log file is definately not
being used ( it no longer exists on disk)...
So how do I update master..sysaltfiles to be correct ?
I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows 2
files) . I'm loathe to do a direct delete on master..sysaltfiles until I can
discover if this kind of 'corruption' is not unknown... but do I have any
other choice ?Hi
I don't know why you have got the extra entry, was there any message in the
SQL Server log when you re-started?
What happens when you try to remove the file using:
ALTER DATABASE database REMOVE FILE logical_file_name
John
"SteveH" <SteveH@.discussions.microsoft.com> wrote in message
news:7C75A085-7563-4D94-9E50-353ECAFF820B@.microsoft.com...
> Dear all,
> I had a database which contained 2 log files, one of the log files was
> deleted - however, master..sysaltfiles still shows 2 log files in
> existance...
> The database is open, and working OK, so second log file is definately not
> being used ( it no longer exists on disk)...
> So how do I update master..sysaltfiles to be correct ?
> I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows
> 2
> files) . I'm loathe to do a direct delete on master..sysaltfiles until I
> can
> discover if this kind of 'corruption' is not unknown... but do I have any
> other choice ?
Master..sysaltfiles contains incorrect info
Dear all,
I had a database which contained 2 log files, one of the log files was
deleted - however, master..sysaltfiles still shows 2 log files in
existance...
The database is open, and working OK, so second log file is definately not
being used ( it no longer exists on disk)...
So how do I update master..sysaltfiles to be correct ?
I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows 2
files) . I'm loathe to do a direct delete on master..sysaltfiles until I can
discover if this kind of 'corruption' is not unknown... but do I have any
other choice ?Hi
I don't know why you have got the extra entry, was there any message in the
SQL Server log when you re-started?
What happens when you try to remove the file using:
ALTER DATABASE database REMOVE FILE logical_file_name
John
"SteveH" <SteveH@.discussions.microsoft.com> wrote in message
news:7C75A085-7563-4D94-9E50-353ECAFF820B@.microsoft.com...
> Dear all,
> I had a database which contained 2 log files, one of the log files was
> deleted - however, master..sysaltfiles still shows 2 log files in
> existance...
> The database is open, and working OK, so second log file is definately not
> being used ( it no longer exists on disk)...
> So how do I update master..sysaltfiles to be correct ?
> I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows
> 2
> files) . I'm loathe to do a direct delete on master..sysaltfiles until I
> can
> discover if this kind of 'corruption' is not unknown... but do I have any
> other choice ?
I had a database which contained 2 log files, one of the log files was
deleted - however, master..sysaltfiles still shows 2 log files in
existance...
The database is open, and working OK, so second log file is definately not
being used ( it no longer exists on disk)...
So how do I update master..sysaltfiles to be correct ?
I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows 2
files) . I'm loathe to do a direct delete on master..sysaltfiles until I can
discover if this kind of 'corruption' is not unknown... but do I have any
other choice ?Hi
I don't know why you have got the extra entry, was there any message in the
SQL Server log when you re-started?
What happens when you try to remove the file using:
ALTER DATABASE database REMOVE FILE logical_file_name
John
"SteveH" <SteveH@.discussions.microsoft.com> wrote in message
news:7C75A085-7563-4D94-9E50-353ECAFF820B@.microsoft.com...
> Dear all,
> I had a database which contained 2 log files, one of the log files was
> deleted - however, master..sysaltfiles still shows 2 log files in
> existance...
> The database is open, and working OK, so second log file is definately not
> being used ( it no longer exists on disk)...
> So how do I update master..sysaltfiles to be correct ?
> I restarted SQL Server, did not resolve issue ( ie sysaltfiles still shows
> 2
> files) . I'm loathe to do a direct delete on master..sysaltfiles until I
> can
> discover if this kind of 'corruption' is not unknown... but do I have any
> other choice ?
Master, Tempdb, Msdb, Model?
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||I use to have data and log on same drive for system databases. The possible exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as for other databases.
Also, moving database files for system databases is a bit special, so read KB 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||I use to have data and log on same drive for system databases. The possible exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as for other databases.
Also, moving database files for system databases is a bit special, so read KB 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
Master, Tempdb, Msdb, Model?
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||I use to have data and log on same drive for system databases. The possible
exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as f
or other databases.
Also, moving database files for system databases is a bit special, so read K
B 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system da
tabases.
Any opinions are appreciated!|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||I use to have data and log on same drive for system databases. The possible
exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as f
or other databases.
Also, moving database files for system databases is a bit special, so read K
B 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system da
tabases.
Any opinions are appreciated!|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!
Subscribe to:
Comments (Atom)