Do the logs and data files of a database have to be on the same server as the
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this?
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this?
>
|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this?
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/default...b;en-us;304261
Regards
Steen
Showing posts with label logs. Show all posts
Showing posts with label logs. Show all posts
Wednesday, March 21, 2012
Location of Logs and data files
Do the logs and data files of a database have to be on the same server as th
e
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this'> Do the logs and data files of a database have to be on the same server as theen">
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as
the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However
I
> am expecting a new one to grow quite fast, and would like to place the dat
a
> and log files on a separate server. However, when I create a new DB and tr
y
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as
the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However
I
> am expecting a new one to grow quite fast, and would like to place the dat
a
> and log files on a separate server. However, when I create a new DB and tr
y
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/defaul...kb;en-us;304261
Regards
Steen
e
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this'> Do the logs and data files of a database have to be on the same server as theen">
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as
the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However
I
> am expecting a new one to grow quite fast, and would like to place the dat
a
> and log files on a separate server. However, when I create a new DB and tr
y
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as
the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However
I
> am expecting a new one to grow quite fast, and would like to place the dat
a
> and log files on a separate server. However, when I create a new DB and tr
y
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/defaul...kb;en-us;304261
Regards
Steen
Location of Logs and data files
Do the logs and data files of a database have to be on the same server as the
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this'> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
Regards
Steen
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this'> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
Regards
Steen
Monday, March 19, 2012
Location for audit logs?
Hi,
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
Bing
Hi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended to
> store auditing logs on an unused disk drive because auditing logs could grow
> wildly. But based on this article
> http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
> SQL Server doesn't let you log auditable events to an alternative location.
>
> <QUOTE>After you enable C2 auditing for the default database or for an
> instance, the database server will log all activity to the data directory
> that you specified during the installation process. (SQL Server doesn't let
> you log auditable events to an alternative location.) This directory holds
> the databases that SQL Server initially created. This directory is also the
> default location for all new databases and their transaction log
> files.</QUOTE>
> Now I'm confused. I have data/transaction logs on one drive, I'm planning
> to add additional disk drive specifically for auditing. Is it possible to
> direct auditing logs to the new drive?
> Thanks,
> Bing
If you change the default data and log directories in the Database
properties task in Enterprise Manager on the properties page of the instance
(right click) do new audit files get created their (you may need to restart)?
If not you can move the databases away from this location using
sp_detach_db/sp_attach_db or backup/restore see
http://support.microsoft.com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
Bing
Hi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended to
> store auditing logs on an unused disk drive because auditing logs could grow
> wildly. But based on this article
> http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
> SQL Server doesn't let you log auditable events to an alternative location.
>
> <QUOTE>After you enable C2 auditing for the default database or for an
> instance, the database server will log all activity to the data directory
> that you specified during the installation process. (SQL Server doesn't let
> you log auditable events to an alternative location.) This directory holds
> the databases that SQL Server initially created. This directory is also the
> default location for all new databases and their transaction log
> files.</QUOTE>
> Now I'm confused. I have data/transaction logs on one drive, I'm planning
> to add additional disk drive specifically for auditing. Is it possible to
> direct auditing logs to the new drive?
> Thanks,
> Bing
If you change the default data and log directories in the Database
properties task in Enterprise Manager on the properties page of the instance
(right click) do new audit files get created their (you may need to restart)?
If not you can move the databases away from this location using
sp_detach_db/sp_attach_db or backup/restore see
http://support.microsoft.com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
Location for audit logs?
Hi,
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
BingHi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended to
> store auditing logs on an unused disk drive because auditing logs could grow
> wildly. But based on this article
> http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
> SQL Server doesn't let you log auditable events to an alternative location.
>
> <QUOTE>After you enable C2 auditing for the default database or for an
> instance, the database server will log all activity to the data directory
> that you specified during the installation process. (SQL Server doesn't let
> you log auditable events to an alternative location.) This directory holds
> the databases that SQL Server initially created. This directory is also the
> default location for all new databases and their transaction log
> files.</QUOTE>
> Now I'm confused. I have data/transaction logs on one drive, I'm planning
> to add additional disk drive specifically for auditing. Is it possible to
> direct auditing logs to the new drive?
> Thanks,
> Bing
If you change the default data and log directories in the Database
properties task in Enterprise Manager on the properties page of the instance
(right click) do new audit files get created their (you may need to restart)?
If not you can move the databases away from this location using
sp_detach_db/sp_attach_db or backup/restore see
http://support.microsoft.com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
BingHi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended to
> store auditing logs on an unused disk drive because auditing logs could grow
> wildly. But based on this article
> http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
> SQL Server doesn't let you log auditable events to an alternative location.
>
> <QUOTE>After you enable C2 auditing for the default database or for an
> instance, the database server will log all activity to the data directory
> that you specified during the installation process. (SQL Server doesn't let
> you log auditable events to an alternative location.) This directory holds
> the databases that SQL Server initially created. This directory is also the
> default location for all new databases and their transaction log
> files.</QUOTE>
> Now I'm confused. I have data/transaction logs on one drive, I'm planning
> to add additional disk drive specifically for auditing. Is it possible to
> direct auditing logs to the new drive?
> Thanks,
> Bing
If you change the default data and log directories in the Database
properties task in Enterprise Manager on the properties page of the instance
(right click) do new audit files get created their (you may need to restart)?
If not you can move the databases away from this location using
sp_detach_db/sp_attach_db or backup/restore see
http://support.microsoft.com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
Location for audit logs?
Hi,
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/se.../sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
BingHi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended
to
> store auditing logs on an unused disk drive because auditing logs could gr
ow
> wildly. But based on this article
> If you change the default data and log directories in the Databaseproperties task in Enterprise Manager on the properties page of the instance(right click) do new audit files get created their (you may need to restart)?If not you can move the databases away from this location usingsp_detach_db/sp_attach_db or backup/restore see[url]http://support.microsoft.com/kb/314546." target="_blank">http://www.microsoft.com/technet/se...com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
[url]http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx[/u
rl]
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/se.../sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
BingHi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended
to
> store auditing logs on an unused disk drive because auditing logs could gr
ow
> wildly. But based on this article
> If you change the default data and log directories in the Databaseproperties task in Enterprise Manager on the properties page of the instance(right click) do new audit files get created their (you may need to restart)?If not you can move the databases away from this location usingsp_detach_db/sp_attach_db or backup/restore see[url]http://support.microsoft.com/kb/314546." target="_blank">http://www.microsoft.com/technet/se...com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
[url]http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx[/u
rl]
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
Monday, February 20, 2012
local access to replication logs (was "Does anyone have a clever solution")
We have a SQL Server database that runs a website on our server, however the company that we are running the website for requested that they have a replicated local version at their business. Everything is working fine.
However they have requested that they have access to the replication logs. They want to have the details of the recent replication details so they can see if changes they have made on their side has been transferre across successfully they also want a table with all the details in of the changes that have ever happened. Can anyone suggest a good way of doing this?
Thanks EdStructure changes or data cheanges.
If they're changing the structure I think it's a much bigger deal...|||I've had to do the same thing at my company, what I did was put triggers on the replicated tables (on the subscriber side). The triggers wrote all insert/updates into a "Log" table which our customer could access throgh Crystal reports.|||Thanks I thik I'll go with the trigger solution, Thanks Ed
However they have requested that they have access to the replication logs. They want to have the details of the recent replication details so they can see if changes they have made on their side has been transferre across successfully they also want a table with all the details in of the changes that have ever happened. Can anyone suggest a good way of doing this?
Thanks EdStructure changes or data cheanges.
If they're changing the structure I think it's a much bigger deal...|||I've had to do the same thing at my company, what I did was put triggers on the replicated tables (on the subscriber side). The triggers wrote all insert/updates into a "Log" table which our customer could access throgh Crystal reports.|||Thanks I thik I'll go with the trigger solution, Thanks Ed
Subscribe to:
Posts (Atom)