I am new to SQL Server, but I cannot seem to find any way that SQL Server
will automatically move a log file (when it isn't needed anymore) off to
archive. Is the only way I can do this by setting up a batch process and
doing it myself?
Help?I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
>I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||Transaction logs are circular files, the same space is reused over and over
again, so there is never a need to "remove the files"... As Dan says, the
way to remove transactions and make space available for re-use is to back up
the log , or use SQL Simple recovery mode.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
>
Just to add to what others have said, it sounds like you're coming from an
Oracle background?
In that case, basically it comes down to, SQL Server reuses the same file
and can do on-line backups of it which will "clear it out".
> Help?sql
Showing posts with label automatically. Show all posts
Showing posts with label automatically. Show all posts
Sunday, March 25, 2012
archive logging the log file
I am new to SQL Server, but I cannot seem to find any way that SQL Server
will automatically move a log file (when it isn't needed anymore) off to
archive. Is the only way I can do this by setting up a batch process and
doing it myself?
Help?
I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
>I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?
|||Transaction logs are circular files, the same space is reused over and over
again, so there is never a need to "remove the files"... As Dan says, the
way to remove transactions and make space available for re-use is to back up
the log , or use SQL Simple recovery mode.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?
|||"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
>
Just to add to what others have said, it sounds like you're coming from an
Oracle background?
In that case, basically it comes down to, SQL Server reuses the same file
and can do on-line backups of it which will "clear it out".
> Help?
will automatically move a log file (when it isn't needed anymore) off to
archive. Is the only way I can do this by setting up a batch process and
doing it myself?
Help?
I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
>I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?
|||Transaction logs are circular files, the same space is reused over and over
again, so there is never a need to "remove the files"... As Dan says, the
way to remove transactions and make space available for re-use is to back up
the log , or use SQL Simple recovery mode.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?
|||"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
>
Just to add to what others have said, it sounds like you're coming from an
Oracle background?
In that case, basically it comes down to, SQL Server reuses the same file
and can do on-line backups of it which will "clear it out".
> Help?
archive logging the log file
I am new to SQL Server, but I cannot seem to find any way that SQL Server
will automatically move a log file (when it isn't needed anymore) off to
archive. Is the only way I can do this by setting up a batch process and
doing it myself?
Help?I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
>I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||Transaction logs are circular files, the same space is reused over and over
again, so there is never a need to "remove the files"... As Dan says, the
way to remove transactions and make space available for re-use is to back up
the log , or use SQL Simple recovery mode.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
>
Just to add to what others have said, it sounds like you're coming from an
Oracle background?
In that case, basically it comes down to, SQL Server reuses the same file
and can do on-line backups of it which will "clear it out".
> Help?
will automatically move a log file (when it isn't needed anymore) off to
archive. Is the only way I can do this by setting up a batch process and
doing it myself?
Help?I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
>I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||Transaction logs are circular files, the same space is reused over and over
again, so there is never a need to "remove the files"... As Dan says, the
way to remove transactions and make space available for re-use is to back up
the log , or use SQL Simple recovery mode.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
>
Just to add to what others have said, it sounds like you're coming from an
Oracle background?
In that case, basically it comes down to, SQL Server reuses the same file
and can do on-line backups of it which will "clear it out".
> Help?
Thursday, March 8, 2012
Application starts before SQL is running.
Very basic question.
OS Windows XP pro
On bootup, an application that starts automatically in the start-up folder,
starts before SQL server is running
This only happens on slower hardware, It must be a common problem, what's
the usual solution?
Graham.
%Profound_observation%I just have a loop in my app where I have exception handling on logon and re
try...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Graham." <me@.privacy.com> wrote in message news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com.
.
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up folder
,
> starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||Another option is to have a vbscript with a timer to wait 5 mins or so on
boot, THEN fire off the executable for the app.
TheSQLGuru
President
Indicium Resources, Inc.
"Graham." <me@.privacy.com> wrote in message
news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com...
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up
> folder, starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||you can also check on whether the SQL server service is running
before your application starts trying to connect to the SQL server.
Change the Application to wait and try for 4-5 times(or based on the
customer experience) to connect to the MSSQL service.
OS Windows XP pro
On bootup, an application that starts automatically in the start-up folder,
starts before SQL server is running
This only happens on slower hardware, It must be a common problem, what's
the usual solution?
Graham.
%Profound_observation%I just have a loop in my app where I have exception handling on logon and re
try...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Graham." <me@.privacy.com> wrote in message news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com.
.
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up folder
,
> starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||Another option is to have a vbscript with a timer to wait 5 mins or so on
boot, THEN fire off the executable for the app.
TheSQLGuru
President
Indicium Resources, Inc.
"Graham." <me@.privacy.com> wrote in message
news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com...
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up
> folder, starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||you can also check on whether the SQL server service is running
before your application starts trying to connect to the SQL server.
Change the Application to wait and try for 4-5 times(or based on the
customer experience) to connect to the MSSQL service.
Application starts before SQL is running.
Very basic question.
OS Windows XP pro
On bootup, an application that starts automatically in the start-up folder,
starts before SQL server is running
This only happens on slower hardware, It must be a common problem, what's
the usual solution?
--
Graham.
%Profound_observation%I just have a loop in my app where I have exception handling on logon and retry...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Graham." <me@.privacy.com> wrote in message news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com...
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up folder,
> starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||Another option is to have a vbscript with a timer to wait 5 mins or so on
boot, THEN fire off the executable for the app.
--
TheSQLGuru
President
Indicium Resources, Inc.
"Graham." <me@.privacy.com> wrote in message
news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com...
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up
> folder, starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||you can also check on whether the SQL server service is running
before your application starts trying to connect to the SQL server.
Change the Application to wait and try for 4-5 times(or based on the
customer experience) to connect to the MSSQL service.
OS Windows XP pro
On bootup, an application that starts automatically in the start-up folder,
starts before SQL server is running
This only happens on slower hardware, It must be a common problem, what's
the usual solution?
--
Graham.
%Profound_observation%I just have a loop in my app where I have exception handling on logon and retry...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Graham." <me@.privacy.com> wrote in message news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com...
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up folder,
> starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||Another option is to have a vbscript with a timer to wait 5 mins or so on
boot, THEN fire off the executable for the app.
--
TheSQLGuru
President
Indicium Resources, Inc.
"Graham." <me@.privacy.com> wrote in message
news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com...
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up
> folder, starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||you can also check on whether the SQL server service is running
before your application starts trying to connect to the SQL server.
Change the Application to wait and try for 4-5 times(or based on the
customer experience) to connect to the MSSQL service.
Sunday, February 12, 2012
Anyway to schedule a report to deploy automatically
Can this be done with ssis or executed in a package?
You only deploy a report when the definition changes. Do your modify your reports on a regular basis? If that is the case then I would suggest writing a little program using the SQL Reporting Services WebServices API. You can do just about anything with it!|||Nevermind, it's the table that is getting updated and the report is already there.
Subscribe to:
Posts (Atom)