Full Screen in Report Manager?

Hi all...
I'm curious if there is a way to default to "full screen" mode when a
user first views a report through report manager. The users here can
click the arrows on the right side and thus make the "header" of the
page collapse, but is there a way to default to that so that the users
don't have to click the arrows?
I had read something about the option to collapse the parameter portion
of the report coming with SP1, which we just installed, but haven't
been able pinpoint how to do it.
We've also given users to ability to access reports via our intranet by
physically typing in the address to our intranet. That address
redirects to the report server - wondering if this may make a
difference in the ability to default to full screen.
Any help is appreciated.
Thanks,
MattIn the link you use to call the report add in &rc:Toolbar=false and
possibly &rc:Parameters=false to remove everything.
ie
src="http://myreportserver/ReportServer?%2fReportfolder%2fParameter&rc%3aParameters=false&rc:LinkTarget=_self&rc:ToolBar=false"|||Thanks for the info! I know that the answer to my problem is in there
somewhere, but when I copy what you have after
"myreportserver/ReportServer" in the link above and add it to the URL
that my project points to, I'm being asked for login/password, and that
shouldn't be happening?
Am I able to take parts of what you wrote above to make the parameters
not be viewable? Sorry to wollow in the details of this as I'm guessing
it's not all that complicated, but it's the first time I've given this
a shot, so thanks for your patience.
Matt|||Yes!
take your regular link and add the pieces you want afterward.
&rc:Parameters=false
&rc:ToolBar=false
&rc:LinkTarget=_blank (or _top or _self...)
You should be able to just tack them on after what you already have.
Ches|||Yes!
take your regular link and add the pieces you want afterward.
&rc:Parameters=false
&rc:ToolBar=false
&rc:LinkTarget=_blank (or _top or _self...)
You should be able to just tack them on after what you already have.
Ches|||Thanks once again for the help.
When I add the piece to suppress parameters and/or the toolbar, I end
up with this link as what is entered for the TargetURL for the
solution:
http://servername/ReportServer&rc:ToolBar=false
When I hit F5 to push the changes to the server, I end up getting the
following:
"A connection could not be made to the report server
http://servername/ReportServer&rc:ToolBar=false"
Any idea what I'm missing or doing wrong here? Do I need a "?" directly
after "reportserver"....this is one of those things that is a small
problem, but the annoyance that it is causing is growing!!
Again, thanks for the help...
Matt

Full Screen in Report Manager

Hi all....

I'm curious if there is a way to default to "full screen" mode when a user first views a report through report manager. The users here can click the arrows on the right side and thus make the "header" of the page collapse, but is there a way to default to that so that the users don't have to click the arrows?

We've also given users to ability to access reports via our intranet by physically typing in the address to our intranet. That address redirects to the report server - wondering if this may make a difference in the ability to default to full screen.

Any help is appreciated.
Thanks,
MattHi Matt,
We too are trying to achieve a "full screen" view when a user clicks a hyper-link from our intranet.
I have browsed the forums expecting the answer to be somewhere in the Report properites but have had no joy. Can anyone please help ?
Cheers
Smeganb|||Hi Matt,

I have been investigating this further and can offer the following:

Using the url

http://<<localhost>>/Reports/Pages/Report.aspx?ItemPath=<<ReportName>>

produces a report with all the paraphernalia assocaited with the Report manager (good though it is i do not want users to be overloaded with superfluous information.

If you point the user to the url

http://<<localhost>>/ReportServer/Pages/Report.aspx?<<ReportName>>&rs:Command=Render

you get a report displayed in a new IE window without the paraphernalia. But that's not all because you can aso use a myriad of other switches to determine what is or is not displayed.E.g.

&rc:Toolbar=false removes the Report Viewer toolbar
&rc:Toolbar=true displays it

I hope this helps

Cheers

Rich

Full Screen in Report Manager

Hi all....

I'm curious if there is a way to default to "full screen" mode when a user first views a report through report manager. The users here can click the arrows on the right side and thus make the "header" of the page collapse, but is there a way to default to that so that the users don't have to click the arrows?

We've also given users to ability to access reports via our intranet by physically typing in the address to our intranet. That address redirects to the report server - wondering if this may make a difference in the ability to default to full screen.

Any help is appreciated.
Thanks,
MattHi Matt,
We too are trying to achieve a "full screen" view when a user clicks a hyper-link from our intranet.
I have browsed the forums expecting the answer to be somewhere in the Report properites but have had no joy. Can anyone please help ?
Cheers
Smeganb|||Hi Matt,

I have been investigating this further and can offer the following:

Using the url

http://<<localhost>>/Reports/Pages/Report.aspx?ItemPath=<<ReportName>>

produces a report with all the paraphernalia assocaited with the Report manager (good though it is i do not want users to be overloaded with superfluous information.

If you point the user to the url

http://<<localhost>>/ReportServer/Pages/Report.aspx?<<ReportName>>&rs:Command=Render

you get a report displayed in a new IE window without the paraphernalia. But that's not all because you can aso use a myriad of other switches to determine what is or is not displayed.E.g.

&rc:Toolbar=false removes the Report Viewer toolbar
&rc:Toolbar=true displays it

I hope this helps

Cheers

Rich

Full Screen in Report Manager

Hi all....

I'm curious if there is a way to default to "full screen" mode when a user first views a report through report manager. The users here can click the arrows on the right side and thus make the "header" of the page collapse, but is there a way to default to that so that the users don't have to click the arrows?

We've also given users to ability to access reports via our intranet by physically typing in the address to our intranet. That address redirects to the report server - wondering if this may make a difference in the ability to default to full screen.

Any help is appreciated.
Thanks,
MattHi Matt,
We too are trying to achieve a "full screen" view when a user clicks a hyper-link from our intranet.
I have browsed the forums expecting the answer to be somewhere in the Report properites but have had no joy. Can anyone please help ?
Cheers
Smeganb|||Hi Matt,

I have been investigating this further and can offer the following:

Using the url

http://<<localhost>>/Reports/Pages/Report.aspx?ItemPath=<<ReportName>>

produces a report with all the paraphernalia assocaited with the Report manager (good though it is i do not want users to be overloaded with superfluous information.

If you point the user to the url

http://<<localhost>>/ReportServer/Pages/Report.aspx?<<ReportName>>&rs:Command=Render

you get a report displayed in a new IE window without the paraphernalia. But that's not all because you can aso use a myriad of other switches to determine what is or is not displayed.E.g.

&rc:Toolbar=false removes the Report Viewer toolbar
&rc:Toolbar=true displays it

I hope this helps

Cheers

Rich

Full screen

Hi all,

I have a simple question about RS.

I need to show all my reports in full screen mode but I don't find any properties in report.

I read in some threads to use ToolBar options but toolbar show or hide print, refresh, etc. but I want to hide the top bar because I don't want show search box or navigation bar!!!

Thanks for all your help.

Did you try pointing to the /reportserver/ url instead of /reports? You can see the URL by right-clicking inside the report and selecting properties.

Also look at URL parameters for the web service.

cheers,

Andrew

|||

Great!

Thank you so much for the tips!!!

cheers,

Mattia

Full recovery mode and large log

Hi,
I have several databases using full recovery mode.
Once an hour I backup the log by
USE master
GO
BACKUP LOG [Prozess_Daten] TO [sich_Prozess_Daten] WITH NOINIT , NOUNLOAD
, NAME = N'Prozess_Daten Sicherung LOG', NOSKIP , STATS = 10, NOFORMAT
and once a day I backup the full db by
USE Prozess_Daten
GO
DBCC CHECKDB ('Prozess_Daten') WITH NO_INFOMSGS
GO
USE master
GO
BACKUP DATABASE [Prozess_Daten] TO [sich_Prozess_Daten] WITH INIT ,
NOUNLOAD , NAME = N'Prozess_Daten Sicherung', NOSKIP , STATS = 10,
NOFORMAT
Nevertheless the log file increases up to several GB (as large as the
datafile!). Only a tiny part of that space is used.
DBCC SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY)
does not help. I must switch to simple recovery mode first, then DBCC
SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY) and switch back to full
recovery mode.
I don't understand why, cause most of the Logfile is unused and could be
truncated(?)
Should I change the way I perform my backups? Maybe:
DBCC CHECKDB ...
BACKUP DATABASE ...
ALTER DATABASE ... (simple)
DBCC SHRINKFILE ... (log)
ALTER DATABASE ... (full)
What's best practice?
Thanks for your help!
--
Regards, InspektorDerrickMost probably you are doing work in between two log backup occasions, and the work you do requires
this amount of log space. My guess is index rebuilds. If you do require this amount of log space, do
not shrink the file regularly, as this comes with a penalty, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"InspektorDerrick" <inspektor.derrick@.kstp.at> wrote in message
news:2F653064-7990-40B1-82C9-0BF53CE40D53@.microsoft.com...
> Hi,
> I have several databases using full recovery mode.
> Once an hour I backup the log by
> USE master
> GO
> BACKUP LOG [Prozess_Daten] TO [sich_Prozess_Daten] WITH NOINIT , NOUNLOAD
> , NAME = N'Prozess_Daten Sicherung LOG', NOSKIP , STATS = 10, NOFORMAT
> and once a day I backup the full db by
> USE Prozess_Daten
> GO
> DBCC CHECKDB ('Prozess_Daten') WITH NO_INFOMSGS
> GO
> USE master
> GO
> BACKUP DATABASE [Prozess_Daten] TO [sich_Prozess_Daten] WITH INIT ,
> NOUNLOAD , NAME = N'Prozess_Daten Sicherung', NOSKIP , STATS = 10,
> NOFORMAT
> Nevertheless the log file increases up to several GB (as large as the
> datafile!). Only a tiny part of that space is used.
> DBCC SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY)
> does not help. I must switch to simple recovery mode first, then DBCC
> SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY) and switch back to full
> recovery mode.
> I don't understand why, cause most of the Logfile is unused and could be
> truncated(?)
> Should I change the way I perform my backups? Maybe:
> DBCC CHECKDB ...
> BACKUP DATABASE ...
> ALTER DATABASE ... (simple)
> DBCC SHRINKFILE ... (log)
> ALTER DATABASE ... (full)
> What's best practice?
> Thanks for your help!
> --
> Regards, InspektorDerrick

Full recovery mode and large log

Hi,
I have several databases using full recovery mode.
Once an hour I backup the log by
USE master
GO
BACKUP LOG [Prozess_Daten] TO [sich_Prozess_Daten] WITH NOINIT , N
OUNLOAD
, NAME = N'Prozess_Daten Sicherung LOG', NOSKIP , STATS = 10, NOFORMAT
and once a day I backup the full db by
USE Prozess_Daten
GO
DBCC CHECKDB ('Prozess_Daten') WITH NO_INFOMSGS
GO
USE master
GO
BACKUP DATABASE [Prozess_Daten] TO [sich_Prozess_Daten] WITH INIT ,
NOUNLOAD , NAME = N'Prozess_Daten Sicherung', NOSKIP , STATS = 10,
NOFORMAT
Nevertheless the log file increases up to several GB (as large as the
datafile!). Only a tiny part of that space is used.
DBCC SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY)
does not help. I must switch to simple recovery mode first, then DBCC
SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY) and switch back to full
recovery mode.
I don't understand why, cause most of the Logfile is unused and could be
truncated(?)
Should I change the way I perform my backups? Maybe:
DBCC CHECKDB ...
BACKUP DATABASE ...
ALTER DATABASE ... (simple)
DBCC SHRINKFILE ... (log)
ALTER DATABASE ... (full)
What's best practice?
Thanks for your help!
--
Regards, InspektorDerrickMost probably you are doing work in between two log backup occasions, and th
e work you do requires
this amount of log space. My guess is index rebuilds. If you do require this
amount of log space, do
not shrink the file regularly, as this comes with a penalty, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"InspektorDerrick" <inspektor.derrick@.kstp.at> wrote in message
news:2F653064-7990-40B1-82C9-0BF53CE40D53@.microsoft.com...
> Hi,
> I have several databases using full recovery mode.
> Once an hour I backup the log by
> USE master
> GO
> BACKUP LOG [Prozess_Daten] TO [sich_Prozess_Daten] WITH NOINIT ,
NOUNLOAD
> , NAME = N'Prozess_Daten Sicherung LOG', NOSKIP , STATS = 10, NOFORMAT
> and once a day I backup the full db by
> USE Prozess_Daten
> GO
> DBCC CHECKDB ('Prozess_Daten') WITH NO_INFOMSGS
> GO
> USE master
> GO
> BACKUP DATABASE [Prozess_Daten] TO [sich_Prozess_Daten] WITH INIT
,
> NOUNLOAD , NAME = N'Prozess_Daten Sicherung', NOSKIP , STATS = 10,
> NOFORMAT
> Nevertheless the log file increases up to several GB (as large as the
> datafile!). Only a tiny part of that space is used.
> DBCC SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY)
> does not help. I must switch to simple recovery mode first, then DBCC
> SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY) and switch back to full
> recovery mode.
> I don't understand why, cause most of the Logfile is unused and could be
> truncated(?)
> Should I change the way I perform my backups? Maybe:
> DBCC CHECKDB ...
> BACKUP DATABASE ...
> ALTER DATABASE ... (simple)
> DBCC SHRINKFILE ... (log)
> ALTER DATABASE ... (full)
> What's best practice?
> Thanks for your help!
> --
> Regards, InspektorDerrick

Full recovery mode and large log

Hi,
I have several databases using full recovery mode.
Once an hour I backup the log by
USE master
GO
BACKUP LOG [Prozess_Daten] TO [sich_Prozess_Daten] WITH NOINIT , NOUNLOAD
, NAME = N'Prozess_Daten Sicherung LOG', NOSKIP , STATS = 10, NOFORMAT
and once a day I backup the full db by
USE Prozess_Daten
GO
DBCC CHECKDB ('Prozess_Daten') WITH NO_INFOMSGS
GO
USE master
GO
BACKUP DATABASE [Prozess_Daten] TO [sich_Prozess_Daten] WITH INIT ,
NOUNLOAD , NAME = N'Prozess_Daten Sicherung', NOSKIP , STATS = 10,
NOFORMAT
Nevertheless the log file increases up to several GB (as large as the
datafile!). Only a tiny part of that space is used.
DBCC SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY)
does not help. I must switch to simple recovery mode first, then DBCC
SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY) and switch back to full
recovery mode.
I don't understand why, cause most of the Logfile is unused and could be
truncated(?)
Should I change the way I perform my backups? Maybe:
DBCC CHECKDB ...
BACKUP DATABASE ...
ALTER DATABASE ... (simple)
DBCC SHRINKFILE ... (log)
ALTER DATABASE ... (full)
What's best practice?
Thanks for your help!
Regards, InspektorDerrick
Most probably you are doing work in between two log backup occasions, and the work you do requires
this amount of log space. My guess is index rebuilds. If you do require this amount of log space, do
not shrink the file regularly, as this comes with a penalty, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"InspektorDerrick" <inspektor.derrick@.kstp.at> wrote in message
news:2F653064-7990-40B1-82C9-0BF53CE40D53@.microsoft.com...
> Hi,
> I have several databases using full recovery mode.
> Once an hour I backup the log by
> USE master
> GO
> BACKUP LOG [Prozess_Daten] TO [sich_Prozess_Daten] WITH NOINIT , NOUNLOAD
> , NAME = N'Prozess_Daten Sicherung LOG', NOSKIP , STATS = 10, NOFORMAT
> and once a day I backup the full db by
> USE Prozess_Daten
> GO
> DBCC CHECKDB ('Prozess_Daten') WITH NO_INFOMSGS
> GO
> USE master
> GO
> BACKUP DATABASE [Prozess_Daten] TO [sich_Prozess_Daten] WITH INIT ,
> NOUNLOAD , NAME = N'Prozess_Daten Sicherung', NOSKIP , STATS = 10,
> NOFORMAT
> Nevertheless the log file increases up to several GB (as large as the
> datafile!). Only a tiny part of that space is used.
> DBCC SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY)
> does not help. I must switch to simple recovery mode first, then DBCC
> SHRINKFILE (N'Prozess_Daten_Log', TRUNCATEONLY) and switch back to full
> recovery mode.
> I don't understand why, cause most of the Logfile is unused and could be
> truncated(?)
> Should I change the way I perform my backups? Maybe:
> DBCC CHECKDB ...
> BACKUP DATABASE ...
> ALTER DATABASE ... (simple)
> DBCC SHRINKFILE ... (log)
> ALTER DATABASE ... (full)
> What's best practice?
> Thanks for your help!
> --
> Regards, InspektorDerrick

Full Recovery

I have a production DB that is in Simple recovery mode. I want to change it
to Full Recovery mode. Are there any settings that i should change before
switching such as from MULTI to SINGLE_USER mode. Will this affect the
current maintenance plans, backup jobs that i have currently running? The
bottomline is that "is it as simple as changing it to Full recovery in
database properties? Thanks...Yes, it is that simple. But you need to make sure you perform regular transaction log backups when
in full mode (this is the reason to have it in full).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mmc" <mmc@.discussions.microsoft.com> wrote in message
news:DCA5CC99-1ECB-49E2-90C3-FB7440A4BE34@.microsoft.com...
>I have a production DB that is in Simple recovery mode. I want to change it
> to Full Recovery mode. Are there any settings that i should change before
> switching such as from MULTI to SINGLE_USER mode. Will this affect the
> current maintenance plans, backup jobs that i have currently running? The
> bottomline is that "is it as simple as changing it to Full recovery in
> database properties? Thanks...|||mmc wrote:
> I have a production DB that is in Simple recovery mode. I want to change it
> to Full Recovery mode. Are there any settings that i should change before
> switching such as from MULTI to SINGLE_USER mode. Will this affect the
> current maintenance plans, backup jobs that i have currently running? The
> bottomline is that "is it as simple as changing it to Full recovery in
> database properties? Thanks...
You'll need to schedule periodic transaction log backups, otherwise the
transaction log will never get flushed out and will continue to grow as
new transactions are created.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" job?
"Tracy McKibben" wrote:
> mmc wrote:
> > I have a production DB that is in Simple recovery mode. I want to change it
> > to Full Recovery mode. Are there any settings that i should change before
> > switching such as from MULTI to SINGLE_USER mode. Will this affect the
> > current maintenance plans, backup jobs that i have currently running? The
> > bottomline is that "is it as simple as changing it to Full recovery in
> > database properties? Thanks...
> You'll need to schedule periodic transaction log backups, otherwise the
> transaction log will never get flushed out and will continue to grow as
> new transactions are created.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" job?
No. Shrinking a file is not the same as emptying it. You can try to shrink the file all you want,
but that will not reduce the number of log records in the file...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mmc" <mmc@.discussions.microsoft.com> wrote in message
news:029D7C74-7478-4CA4-A4C4-01529B9B71C0@.microsoft.com...
> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" job?
> "Tracy McKibben" wrote:
>> mmc wrote:
>> > I have a production DB that is in Simple recovery mode. I want to change it
>> > to Full Recovery mode. Are there any settings that i should change before
>> > switching such as from MULTI to SINGLE_USER mode. Will this affect the
>> > current maintenance plans, backup jobs that i have currently running? The
>> > bottomline is that "is it as simple as changing it to Full recovery in
>> > database properties? Thanks...
>> You'll need to schedule periodic transaction log backups, otherwise the
>> transaction log will never get flushed out and will continue to grow as
>> new transactions are created.
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com|||mmc wrote:
> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" job?
>
Nope. Shrinking removes free space from the files, it doesn't remove
committed transactions. Backing up the log file will remove the
committed transactions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||And before you can start making transaction log backups, you'll have to make
a full backup.
You should do that as soon as you make the switch to full mode.
--
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OlQotFyEHHA.2356@.TK2MSFTNGP03.phx.gbl...
> Yes, it is that simple. But you need to make sure you perform regular
> transaction log backups when in full mode (this is the reason to have it
> in full).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "mmc" <mmc@.discussions.microsoft.com> wrote in message
> news:DCA5CC99-1ECB-49E2-90C3-FB7440A4BE34@.microsoft.com...
>>I have a production DB that is in Simple recovery mode. I want to change
>>it
>> to Full Recovery mode. Are there any settings that i should change before
>> switching such as from MULTI to SINGLE_USER mode. Will this affect the
>> current maintenance plans, backup jobs that i have currently running? The
>> bottomline is that "is it as simple as changing it to Full recovery in
>> database properties? Thanks...
>

Full Recovery

I have a production DB that is in Simple recovery mode. I want to change it
to Full Recovery mode. Are there any settings that i should change before
switching such as from MULTI to SINGLE_USER mode. Will this affect the
current maintenance plans, backup jobs that i have currently running? The
bottomline is that "is it as simple as changing it to Full recovery in
database properties? Thanks...Yes, it is that simple. But you need to make sure you perform regular transa
ction log backups when
in full mode (this is the reason to have it in full).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mmc" <mmc@.discussions.microsoft.com> wrote in message
news:DCA5CC99-1ECB-49E2-90C3-FB7440A4BE34@.microsoft.com...
>I have a production DB that is in Simple recovery mode. I want to change it
> to Full Recovery mode. Are there any settings that i should change before
> switching such as from MULTI to SINGLE_USER mode. Will this affect the
> current maintenance plans, backup jobs that i have currently running? The
> bottomline is that "is it as simple as changing it to Full recovery in
> database properties? Thanks...|||mmc wrote:
> I have a production DB that is in Simple recovery mode. I want to change i
t
> to Full Recovery mode. Are there any settings that i should change before
> switching such as from MULTI to SINGLE_USER mode. Will this affect the
> current maintenance plans, backup jobs that i have currently running? The
> bottomline is that "is it as simple as changing it to Full recovery in
> database properties? Thanks...
You'll need to schedule periodic transaction log backups, otherwise the
transaction log will never get flushed out and will continue to grow as
new transactions are created.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" job
?
"Tracy McKibben" wrote:

> mmc wrote:
> You'll need to schedule periodic transaction log backups, otherwise the
> transaction log will never get flushed out and will continue to grow as
> new transactions are created.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" j
ob?
No. Shrinking a file is not the same as emptying it. You can try to shrink t
he file all you want,
but that will not reduce the number of log records in the file...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mmc" <mmc@.discussions.microsoft.com> wrote in message
news:029D7C74-7478-4CA4-A4C4-01529B9B71C0@.microsoft.com...[vbcol=seagreen]
> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" j
ob?
> "Tracy McKibben" wrote:
>|||mmc wrote:
> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" j
ob?
>
Nope. Shrinking removes free space from the files, it doesn't remove
committed transactions. Backing up the log file will remove the
committed transactions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||And before you can start making transaction log backups, you'll have to make
a full backup.
You should do that as soon as you make the switch to full mode.
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OlQotFyEHHA.2356@.TK2MSFTNGP03.phx.gbl...
> Yes, it is that simple. But you need to make sure you perform regular
> transaction log backups when in full mode (this is the reason to have it
> in full).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "mmc" <mmc@.discussions.microsoft.com> wrote in message
> news:DCA5CC99-1ECB-49E2-90C3-FB7440A4BE34@.microsoft.com...
>

Full Recovery

I have a production DB that is in Simple recovery mode. I want to change it
to Full Recovery mode. Are there any settings that i should change before
switching such as from MULTI to SINGLE_USER mode. Will this affect the
current maintenance plans, backup jobs that i have currently running? The
bottomline is that "is it as simple as changing it to Full recovery in
database properties? Thanks...
mmc wrote:
> I have a production DB that is in Simple recovery mode. I want to change it
> to Full Recovery mode. Are there any settings that i should change before
> switching such as from MULTI to SINGLE_USER mode. Will this affect the
> current maintenance plans, backup jobs that i have currently running? The
> bottomline is that "is it as simple as changing it to Full recovery in
> database properties? Thanks...
You'll need to schedule periodic transaction log backups, otherwise the
transaction log will never get flushed out and will continue to grow as
new transactions are created.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" job?
"Tracy McKibben" wrote:

> mmc wrote:
> You'll need to schedule periodic transaction log backups, otherwise the
> transaction log will never get flushed out and will continue to grow as
> new transactions are created.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
|||mmc wrote:
> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" job?
>
Nope. Shrinking removes free space from the files, it doesn't remove
committed transactions. Backing up the log file will remove the
committed transactions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Full mode to Simple mode in SQL2000?

Hi all,
I have two DBs that set as Full mode which has a t-log and
it seems like contains some data.
These DBs are updated by clients 24/7
If I set it to Simple mode, does data from Log will be
updated to DB and truncate it automatically? And not
affect any transaction from clients?
Also, how can I see if there is any data in Transaction
log? Any Stored procedure in query analyzer?
Thanks in advance.
Lintadsl"Lintadsl" <anonymous@.discussions.microsoft.com> wrote in message
news:000f01c3a551$cd775630$a401280a@.phx.gbl...
> Hi all,
> I have two DBs that set as Full mode which has a t-log and
> it seems like contains some data.
> These DBs are updated by clients 24/7
> If I set it to Simple mode, does data from Log will be
> updated to DB and truncate it automatically?
Yes it will.
>And not affect any transaction from clients?
It will not effect any active transaction.
> Also, how can I see if there is any data in Transaction
> log? Any Stored procedure in query analyzer?
You would need a 3rd party product like lumnigent to view any data in the
transaction log. You can use DBCC OPENTRAN to see if there are any open
transactions.
You also need to be aware that if you switch the database from Full to
Simple recovery you loose the ability to recover any transactions, since the
last full database backup.
Steve|||>--Original Message--
>"Lintadsl" <anonymous@.discussions.microsoft.com> wrote in
message
>news:000f01c3a551$cd775630$a401280a@.phx.gbl...
>> Hi all,
>> I have two DBs that set as Full mode which has a t-log
and
>> it seems like contains some data.
>> These DBs are updated by clients 24/7
>> If I set it to Simple mode, does data from Log will be
>> updated to DB and truncate it automatically?
>Yes it will.
>>And not affect any transaction from clients?
>It will not effect any active transaction.
>> Also, how can I see if there is any data in Transaction
>> log? Any Stored procedure in query analyzer?
>You would need a 3rd party product like lumnigent to view
any data in the
>transaction log. You can use DBCC OPENTRAN to see if
there are any open
>transactions.
>You also need to be aware that if you switch the database
from Full to
>Simple recovery you loose the ability to recover any
transactions, since the
>last full database backup.
>Steve
>
>.
>