Hello:
A couple of times on this board, I posed the question as to why expired
backup files may not get deleted from a server folder automatically despite
the fact that the maintenance plan in SQL 2000 tells the server to delete
files older than x number of days.
I want to thank everyone for pointing me to that really good article by Bill
Hollinshead. The part of the article about reading the maintenance plan's
history report solved the problem for me.
You see, by reading the report at my client site, I found a third reason as
to why backup files do not get deleted. (The first two reasons are
Permissions and Sharing Violation.)
The client did not have enough space on his server's hard drive. Therefore,
the last few databases in the list of databases were not getting deleted.
So, here is what a SQL maintenance plan does in this case where there is not
enough space and the backups of those last few databases terminate abnormally
therefore.
The maintenace plan quits and does not bother deleting the expired backups.
basically, if the server has run out of space, the maintenance plan does not
try to delete expired backups!
In a way, this should be added as a third reason as to why backup files do
not get deleted!
Thanks, again!
childofthe1980s
On Feb 8, 10:15 pm, childofthe1980s
<childofthe19...@.discussions.microsoft.com> wrote:
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despite
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bill
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason as
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefore,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is not
> enough space and the backups of those last few databases terminate abnormally
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups.
> basically, if the server has run out of space, the maintenance plan does not
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s
This is one argument I have for NOT using the maintenance plans - you
have no control over the inner workings. I'd encourage everyone to
build their OWN maintenance routines. Write your own backup scripts,
your own reindex scripts, your own cleanup scripts. I have examples
of all three here:
http://realsqlguy.blogspot.com/2007/02/automating-database-backups.html
http://realsqlguy.blogspot.com/2007/02/cleaning-up-old-files.html
http://realsqlguy.blogspot.com/2007/02/smart-index-defragmentation.html
Showing posts with label automatically. Show all posts
Showing posts with label automatically. Show all posts
Monday, March 19, 2012
another reason why backup files do not get deleted
Hello:
A couple of times on this board, I posed the question as to why expired
backup files may not get deleted from a server folder automatically despite
the fact that the maintenance plan in SQL 2000 tells the server to delete
files older than x number of days.
I want to thank everyone for pointing me to that really good article by Bill
Hollinshead. The part of the article about reading the maintenance plan's
history report solved the problem for me.
You see, by reading the report at my client site, I found a third reason as
to why backup files do not get deleted. (The first two reasons are
Permissions and Sharing Violation.)
The client did not have enough space on his server's hard drive. Therefore,
the last few databases in the list of databases were not getting deleted.
So, here is what a SQL maintenance plan does in this case where there is not
enough space and the backups of those last few databases terminate abnormall
y
therefore.
The maintenace plan quits and does not bother deleting the expired backups.
basically, if the server has run out of space, the maintenance plan does not
try to delete expired backups!
In a way, this should be added as a third reason as to why backup files do
not get deleted!
Thanks, again!
childofthe1980sThanks for reporting back to us. This is essentially why I would like a "con
tinue on error" option.
Basically, this is the same as connect issue 125025. Re-reading this report,
I now see that they are
considering it for sp2, so it might be worth checking if they implemented su
ch an option...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in messa
ge
news:B8454FDE-F33B-4BAD-BF70-7C18261A4677@.microsoft.com...
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despit
e
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bi
ll
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason a
s
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefor
e,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is n
ot
> enough space and the backups of those last few databases terminate abnorma
lly
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups
.
> basically, if the server has run out of space, the maintenance plan does n
ot
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s|||On Feb 8, 10:15 pm, childofthe1980s
<childofthe19...@.discussions.microsoft.com> wrote:
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despit
e
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bi
ll
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason a
s
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefor
e,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is n
ot
> enough space and the backups of those last few databases terminate abnorma
lly
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups
.
> basically, if the server has run out of space, the maintenance plan does n
ot
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s
This is one argument I have for NOT using the maintenance plans - you
have no control over the inner workings. I'd encourage everyone to
build their OWN maintenance routines. Write your own backup scripts,
your own reindex scripts, your own cleanup scripts. I have examples
of all three here:
http://realsqlguy.blogspot.com/2007...se-backups.html
http://realsqlguy.blogspot.com/2007...-old-files.html
http://realsqlguy.blogspot.com/2007...gmentation.html
A couple of times on this board, I posed the question as to why expired
backup files may not get deleted from a server folder automatically despite
the fact that the maintenance plan in SQL 2000 tells the server to delete
files older than x number of days.
I want to thank everyone for pointing me to that really good article by Bill
Hollinshead. The part of the article about reading the maintenance plan's
history report solved the problem for me.
You see, by reading the report at my client site, I found a third reason as
to why backup files do not get deleted. (The first two reasons are
Permissions and Sharing Violation.)
The client did not have enough space on his server's hard drive. Therefore,
the last few databases in the list of databases were not getting deleted.
So, here is what a SQL maintenance plan does in this case where there is not
enough space and the backups of those last few databases terminate abnormall
y
therefore.
The maintenace plan quits and does not bother deleting the expired backups.
basically, if the server has run out of space, the maintenance plan does not
try to delete expired backups!
In a way, this should be added as a third reason as to why backup files do
not get deleted!
Thanks, again!
childofthe1980sThanks for reporting back to us. This is essentially why I would like a "con
tinue on error" option.
Basically, this is the same as connect issue 125025. Re-reading this report,
I now see that they are
considering it for sp2, so it might be worth checking if they implemented su
ch an option...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in messa
ge
news:B8454FDE-F33B-4BAD-BF70-7C18261A4677@.microsoft.com...
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despit
e
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bi
ll
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason a
s
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefor
e,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is n
ot
> enough space and the backups of those last few databases terminate abnorma
lly
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups
.
> basically, if the server has run out of space, the maintenance plan does n
ot
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s|||On Feb 8, 10:15 pm, childofthe1980s
<childofthe19...@.discussions.microsoft.com> wrote:
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despit
e
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bi
ll
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason a
s
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefor
e,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is n
ot
> enough space and the backups of those last few databases terminate abnorma
lly
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups
.
> basically, if the server has run out of space, the maintenance plan does n
ot
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s
This is one argument I have for NOT using the maintenance plans - you
have no control over the inner workings. I'd encourage everyone to
build their OWN maintenance routines. Write your own backup scripts,
your own reindex scripts, your own cleanup scripts. I have examples
of all three here:
http://realsqlguy.blogspot.com/2007...se-backups.html
http://realsqlguy.blogspot.com/2007...-old-files.html
http://realsqlguy.blogspot.com/2007...gmentation.html
another reason why backup files do not get deleted
Hello:
A couple of times on this board, I posed the question as to why expired
backup files may not get deleted from a server folder automatically despite
the fact that the maintenance plan in SQL 2000 tells the server to delete
files older than x number of days.
I want to thank everyone for pointing me to that really good article by Bill
Hollinshead. The part of the article about reading the maintenance plan's
history report solved the problem for me.
You see, by reading the report at my client site, I found a third reason as
to why backup files do not get deleted. (The first two reasons are
Permissions and Sharing Violation.)
The client did not have enough space on his server's hard drive. Therefore,
the last few databases in the list of databases were not getting deleted.
So, here is what a SQL maintenance plan does in this case where there is not
enough space and the backups of those last few databases terminate abnormally
therefore.
The maintenace plan quits and does not bother deleting the expired backups.
basically, if the server has run out of space, the maintenance plan does not
try to delete expired backups!
In a way, this should be added as a third reason as to why backup files do
not get deleted!
Thanks, again!
childofthe1980sThanks for reporting back to us. This is essentially why I would like a "continue on error" option.
Basically, this is the same as connect issue 125025. Re-reading this report, I now see that they are
considering it for sp2, so it might be worth checking if they implemented such an option...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in message
news:B8454FDE-F33B-4BAD-BF70-7C18261A4677@.microsoft.com...
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despite
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bill
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason as
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefore,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is not
> enough space and the backups of those last few databases terminate abnormally
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups.
> basically, if the server has run out of space, the maintenance plan does not
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s|||On Feb 8, 10:15 pm, childofthe1980s
<childofthe19...@.discussions.microsoft.com> wrote:
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despite
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bill
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason as
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefore,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is not
> enough space and the backups of those last few databases terminate abnormally
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups.
> basically, if the server has run out of space, the maintenance plan does not
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s
This is one argument I have for NOT using the maintenance plans - you
have no control over the inner workings. I'd encourage everyone to
build their OWN maintenance routines. Write your own backup scripts,
your own reindex scripts, your own cleanup scripts. I have examples
of all three here:
http://realsqlguy.blogspot.com/2007/02/automating-database-backups.html
http://realsqlguy.blogspot.com/2007/02/cleaning-up-old-files.html
http://realsqlguy.blogspot.com/2007/02/smart-index-defragmentation.html
A couple of times on this board, I posed the question as to why expired
backup files may not get deleted from a server folder automatically despite
the fact that the maintenance plan in SQL 2000 tells the server to delete
files older than x number of days.
I want to thank everyone for pointing me to that really good article by Bill
Hollinshead. The part of the article about reading the maintenance plan's
history report solved the problem for me.
You see, by reading the report at my client site, I found a third reason as
to why backup files do not get deleted. (The first two reasons are
Permissions and Sharing Violation.)
The client did not have enough space on his server's hard drive. Therefore,
the last few databases in the list of databases were not getting deleted.
So, here is what a SQL maintenance plan does in this case where there is not
enough space and the backups of those last few databases terminate abnormally
therefore.
The maintenace plan quits and does not bother deleting the expired backups.
basically, if the server has run out of space, the maintenance plan does not
try to delete expired backups!
In a way, this should be added as a third reason as to why backup files do
not get deleted!
Thanks, again!
childofthe1980sThanks for reporting back to us. This is essentially why I would like a "continue on error" option.
Basically, this is the same as connect issue 125025. Re-reading this report, I now see that they are
considering it for sp2, so it might be worth checking if they implemented such an option...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in message
news:B8454FDE-F33B-4BAD-BF70-7C18261A4677@.microsoft.com...
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despite
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bill
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason as
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefore,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is not
> enough space and the backups of those last few databases terminate abnormally
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups.
> basically, if the server has run out of space, the maintenance plan does not
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s|||On Feb 8, 10:15 pm, childofthe1980s
<childofthe19...@.discussions.microsoft.com> wrote:
> Hello:
> A couple of times on this board, I posed the question as to why expired
> backup files may not get deleted from a server folder automatically despite
> the fact that the maintenance plan in SQL 2000 tells the server to delete
> files older than x number of days.
> I want to thank everyone for pointing me to that really good article by Bill
> Hollinshead. The part of the article about reading the maintenance plan's
> history report solved the problem for me.
> You see, by reading the report at my client site, I found a third reason as
> to why backup files do not get deleted. (The first two reasons are
> Permissions and Sharing Violation.)
> The client did not have enough space on his server's hard drive. Therefore,
> the last few databases in the list of databases were not getting deleted.
> So, here is what a SQL maintenance plan does in this case where there is not
> enough space and the backups of those last few databases terminate abnormally
> therefore.
> The maintenace plan quits and does not bother deleting the expired backups.
> basically, if the server has run out of space, the maintenance plan does not
> try to delete expired backups!
> In a way, this should be added as a third reason as to why backup files do
> not get deleted!
> Thanks, again!
> childofthe1980s
This is one argument I have for NOT using the maintenance plans - you
have no control over the inner workings. I'd encourage everyone to
build their OWN maintenance routines. Write your own backup scripts,
your own reindex scripts, your own cleanup scripts. I have examples
of all three here:
http://realsqlguy.blogspot.com/2007/02/automating-database-backups.html
http://realsqlguy.blogspot.com/2007/02/cleaning-up-old-files.html
http://realsqlguy.blogspot.com/2007/02/smart-index-defragmentation.html
Sunday, March 11, 2012
Another newbie question
What is the role of the SQL agent and what is the difference whether it will
run automatically or manually (I am trying to run the replication wizard)
Thanks,
Shmuel
There are several agents associated with replication and they are
essentially jobs fundamental to replication. Have a look in BOL for
replication,agents for a description of each agent. Running continuously
will help you work with miniumum latency, but you will not then have control
over when the load is placed on your server, and connectivity is mandatory.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||i'm kinda new at this too... but it seems to me that automatic means the same thing as scheduled... you can have it run once a day at a certain time, etc... manual means you want to control if and when it runs.
Andrea Garcia
Yahoo IM: mmmmojobootay
CS degree arriving in: July 2005
www.millionformarriage.com
"S Shulman" <smshulman@.hotmail.com> wrote in message news:uQ8Z4J0IFHA.2648@.TK2MSFTNGP14.phx.gbl...
What is the role of the SQL agent and what is the difference whether it will
run automatically or manually (I am trying to run the replication wizard)
Thanks,
Shmuel
|||sql server agent is the component of sql server which runs all of your
jobs. If you configure it to run automatically it will start whenever
you reboot your machine. If you configure it to run manually you will
have to manually start it.
S Shulman wrote:
> What is the role of the SQL agent and what is the difference whether it will
> run automatically or manually (I am trying to run the replication wizard)
> Thanks,
> Shmuel
>
run automatically or manually (I am trying to run the replication wizard)
Thanks,
Shmuel
There are several agents associated with replication and they are
essentially jobs fundamental to replication. Have a look in BOL for
replication,agents for a description of each agent. Running continuously
will help you work with miniumum latency, but you will not then have control
over when the load is placed on your server, and connectivity is mandatory.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||i'm kinda new at this too... but it seems to me that automatic means the same thing as scheduled... you can have it run once a day at a certain time, etc... manual means you want to control if and when it runs.
Andrea Garcia
Yahoo IM: mmmmojobootay
CS degree arriving in: July 2005
www.millionformarriage.com
"S Shulman" <smshulman@.hotmail.com> wrote in message news:uQ8Z4J0IFHA.2648@.TK2MSFTNGP14.phx.gbl...
What is the role of the SQL agent and what is the difference whether it will
run automatically or manually (I am trying to run the replication wizard)
Thanks,
Shmuel
|||sql server agent is the component of sql server which runs all of your
jobs. If you configure it to run automatically it will start whenever
you reboot your machine. If you configure it to run manually you will
have to manually start it.
S Shulman wrote:
> What is the role of the SQL agent and what is the difference whether it will
> run automatically or manually (I am trying to run the replication wizard)
> Thanks,
> Shmuel
>
Saturday, February 25, 2012
Annoying feature - report service rewrite query automatically.
This feature is very annoying, report service 2k rewrites my query, even the
format of query is changed too. How to disable this feature?
Thanks really a lot.Use the generic query designer (two pane) instead of the graphical query
designer. The button to switch to it is one of the buttons to the right of
the ...
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"qye2020" <qye2020@.yahoo.com> wrote in message
news:uz0EglpJGHA.2088@.TK2MSFTNGP11.phx.gbl...
> This feature is very annoying, report service 2k rewrites my query, even
> the format of query is changed too. How to disable this feature?
> Thanks really a lot.
>|||Wonderful, problem is gone with your kind answer.
Thanks a lot.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ewOcV9pJGHA.3176@.TK2MSFTNGP12.phx.gbl...
> Use the generic query designer (two pane) instead of the graphical query
> designer. The button to switch to it is one of the buttons to the right of
> the ...
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "qye2020" <qye2020@.yahoo.com> wrote in message
> news:uz0EglpJGHA.2088@.TK2MSFTNGP11.phx.gbl...
>> This feature is very annoying, report service 2k rewrites my query, even
>> the format of query is changed too. How to disable this feature?
>> Thanks really a lot.
>
format of query is changed too. How to disable this feature?
Thanks really a lot.Use the generic query designer (two pane) instead of the graphical query
designer. The button to switch to it is one of the buttons to the right of
the ...
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"qye2020" <qye2020@.yahoo.com> wrote in message
news:uz0EglpJGHA.2088@.TK2MSFTNGP11.phx.gbl...
> This feature is very annoying, report service 2k rewrites my query, even
> the format of query is changed too. How to disable this feature?
> Thanks really a lot.
>|||Wonderful, problem is gone with your kind answer.
Thanks a lot.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ewOcV9pJGHA.3176@.TK2MSFTNGP12.phx.gbl...
> Use the generic query designer (two pane) instead of the graphical query
> designer. The button to switch to it is one of the buttons to the right of
> the ...
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "qye2020" <qye2020@.yahoo.com> wrote in message
> news:uz0EglpJGHA.2088@.TK2MSFTNGP11.phx.gbl...
>> This feature is very annoying, report service 2k rewrites my query, even
>> the format of query is changed too. How to disable this feature?
>> Thanks really a lot.
>
Subscribe to:
Posts (Atom)