How to configure Report Server in SQL Server 2005?

Hello, everyone:

I hope my question is clear.

I have SQl Server 2005 installed in local computer. I am planning to create report by Report Service so a report server is needed by which I can deploy report from my local computer to that server. How to intall the report server in another computer/

Thanks

ZYTZYT,
Your question is clear, but it doesn't look like you've done any research on the subject. There are plenty of KB articles and technical support documents regarding Reporting Services on the Microsoft website and numerous books exist on the subject.
If you encounter a specific problem when trying to implement Reporting Services having done the necessary research, people are more likely to help you, but they won't generally do all your work for you!

Lempster :S

how to clear up log file in primary database in log shipping ?

our database system is runninig in log shipping mode.
currently, primary database log file get much more bigger,
but I dare not shrink log file in primary database ,
because do this will affect log shipping.
any way reslove this?
regards!Backup Log has Active and Inactive Portions. To Truncate Inactive
portion user the following command in SQL Query Analyser
USE The following Command
BACKUP LOG { database_name | @.database_name_var }
WITH TRUNCATE_ONLY|||That would break the log shipping!
AFAIK, shrinking of log file should be OK in a log shipping scenario...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rex" <r.ghodasara@.gmail.com> wrote in message
news:1143808657.133001.205870@.u72g2000cwu.googlegroups.com...
> Backup Log has Active and Inactive Portions. To Truncate Inactive
> portion user the following command in SQL Query Analyser
> USE The following Command
> BACKUP LOG { database_name | @.database_name_var }
> WITH TRUNCATE_ONLY
>|||thanks ,
but according to your point
as time goes, the logfile will get bigger and bigger,
shrinking logfile is not the best way?
do you think so ?
I meant how to clear up logfile and don't affect log shipping?|||The log file is emptied each time you do backup of the transaction log. So, it will grow until it
has the size needed to accommodate the modifications you do between two log backups, so just let it
be the size it need to be. If you see it grow beyond that, you can perhaps have had a long running
transaction in the log preventing the file to be emptied to a high degree. See
http://www.karaszi.com/SQLServer/info_dont_shrink.asp for more information.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<lovexueer@.gmail.com> wrote in message news:1143814572.962154.266770@.g10g2000cwb.googlegroups.com...
> thanks ,
> but according to your point
> as time goes, the logfile will get bigger and bigger,
> shrinking logfile is not the best way?
> do you think so ?
> I meant how to clear up logfile and don't affect log shipping?
>

how to clear up log file in primary database in log shipping ?

our database system is runninig in log shipping mode.
currently, primary database log file get much more bigger,
but I dare not shrink log file in primary database ,
because do this will affect log shipping.
any way reslove this?
regards!
Backup Log has Active and Inactive Portions. To Truncate Inactive
portion user the following command in SQL Query Analyser
USE The following Command
BACKUP LOG { database_name | @.database_name_var }
WITH TRUNCATE_ONLY
|||That would break the log shipping!
AFAIK, shrinking of log file should be OK in a log shipping scenario...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rex" <r.ghodasara@.gmail.com> wrote in message
news:1143808657.133001.205870@.u72g2000cwu.googlegr oups.com...
> Backup Log has Active and Inactive Portions. To Truncate Inactive
> portion user the following command in SQL Query Analyser
> USE The following Command
> BACKUP LOG { database_name | @.database_name_var }
> WITH TRUNCATE_ONLY
>
|||thanks ,
but according to your point
as time goes, the logfile will get bigger and bigger,
shrinking logfile is not the best way?
do you think so ?
I meant how to clear up logfile and don't affect log shipping?
|||The log file is emptied each time you do backup of the transaction log. So, it will grow until it
has the size needed to accommodate the modifications you do between two log backups, so just let it
be the size it need to be. If you see it grow beyond that, you can perhaps have had a long running
transaction in the log preventing the file to be emptied to a high degree. See
http://www.karaszi.com/SQLServer/info_dont_shrink.asp for more information.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<lovexueer@.gmail.com> wrote in message news:1143814572.962154.266770@.g10g2000cwb.googlegr oups.com...
> thanks ,
> but according to your point
> as time goes, the logfile will get bigger and bigger,
> shrinking logfile is not the best way?
> do you think so ?
> I meant how to clear up logfile and don't affect log shipping?
>

how to clear up log file in primary database in log shipping ?

our database system is runninig in log shipping mode.
currently, primary database log file get much more bigger,
but I dare not shrink log file in primary database ,
because do this will affect log shipping.
any way reslove this?
regards!Backup Log has Active and Inactive Portions. To Truncate Inactive
portion user the following command in SQL Query Analyser
USE The following Command
BACKUP LOG { database_name | @.database_name_var }
WITH TRUNCATE_ONLY|||That would break the log shipping!
AFAIK, shrinking of log file should be OK in a log shipping scenario...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rex" <r.ghodasara@.gmail.com> wrote in message
news:1143808657.133001.205870@.u72g2000cwu.googlegroups.com...
> Backup Log has Active and Inactive Portions. To Truncate Inactive
> portion user the following command in SQL Query Analyser
> USE The following Command
> BACKUP LOG { database_name | @.database_name_var }
> WITH TRUNCATE_ONLY
>|||thanks ,
but according to your point
as time goes, the logfile will get bigger and bigger,
shrinking logfile is not the best way?
do you think so ?
I meant how to clear up logfile and don't affect log shipping?|||The log file is emptied each time you do backup of the transaction log. So,
it will grow until it
has the size needed to accommodate the modifications you do between two log
backups, so just let it
be the size it need to be. If you see it grow beyond that, you can perhaps h
ave had a long running
transaction in the log preventing the file to be emptied to a high degree. S
ee
http://www.karaszi.com/SQLServer/info_dont_shrink.asp for more information.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<lovexueer@.gmail.com> wrote in message news:1143814572.962154.266770@.g10g2000cwb.googlegroup
s.com...
> thanks ,
> but according to your point
> as time goes, the logfile will get bigger and bigger,
> shrinking logfile is not the best way?
> do you think so ?
> I meant how to clear up logfile and don't affect log shipping?
>

How to clear the log (ldf) file?

Hi all.
I have a database I need no auditor to be able to track changes made to it.
As far as I know, the LDF file keeps a record of all the transactions
performed on it which is exactly what I dont want. I've read that it is
impossible to disable logging in MSSQL. Is this 100% true? Has anyone found a
way to keep the logs file clear?
Att,
RODOLFO
Yes, you are right that we cannot "disable"logging in the SQL Server.
If you want to let to SQL Server to manage its LOG file in terms of size ,
so set the recovery model to SIMPLE
For more info please refer to the BOL
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
found a
> way to keep the logs file clear?
> Att,
> RODOLFO
|||Hi,
We can not totally stop loggin in sql server.
But if you select the RECOVERY model for your database as SIMPLE then
transaction log will be cleared automatically
Has anyone found a way to keep the logs file clear?
If it is SIMPLE recovery log will be cleared automatically, but for other
recovery model you need to perform the transaction log backup.
See Backup Log command in books online.
Thanks
Hari
SQL Server MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
> it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
> found a
> way to keep the logs file clear?
> Att,
> RODOLFO
|||To add to the other responses, the transaction log is required in order to
maintain database consistency. This is used by SQL Server to guarantee
all-or-nothing atomic transactions. Although the log can be used by
third-party tools for auditing purposes, the primary purpose of the log is
to facilitate the backout and roll-forward of transactions.
You can keep transaction log file size reasonable by choosing the
appropriate recovery model and backup strategy for your environment.
Hope this helps.
Dan Guzman
SQL Server MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
> it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
> found a
> way to keep the logs file clear?
> Att,
> RODOLFO
|||Hello and thanks a lot for your answers.
I think I understand better the purpose of the log file now reading your
posts. The problem is that it just confirms my fears. I need NO ONE to be
able to perform an audit on this database. The ideal situation will be to
disable this logging. Now I know it can't be done in MS SQL... what's the
closest to it I can get?
Att,
RODOLFO
"Dan Guzman" wrote:

> To add to the other responses, the transaction log is required in order to
> maintain database consistency. This is used by SQL Server to guarantee
> all-or-nothing atomic transactions. Although the log can be used by
> third-party tools for auditing purposes, the primary purpose of the log is
> to facilitate the backout and roll-forward of transactions.
> You can keep transaction log file size reasonable by choosing the
> appropriate recovery model and backup strategy for your environment.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
> news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
>
>
|||If you don't want anyone to read the log then don't give them permissions to
that folder. The physical security of the data files is up to you at the
Windows level.
Andrew J. Kelly SQL MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:634187D5-A399-4B4A-85D4-3CA9C7FF62B0@.microsoft.com...[vbcol=seagreen]
> Hello and thanks a lot for your answers.
> I think I understand better the purpose of the log file now reading your
> posts. The problem is that it just confirms my fears. I need NO ONE to be
> able to perform an audit on this database. The ideal situation will be to
> disable this logging. Now I know it can't be done in MS SQL... what's the
> closest to it I can get?
> Att,
> RODOLFO
> "Dan Guzman" wrote:

How to clear the log (ldf) file?

Hi all.
I have a database I need no auditor to be able to track changes made to it.
As far as I know, the LDF file keeps a record of all the transactions
performed on it which is exactly what I dont want. I've read that it is
impossible to disable logging in MSSQL. Is this 100% true? Has anyone found
a
way to keep the logs file clear?
Att,
RODOLFOYes, you are right that we cannot "disable"logging in the SQL Server.
If you want to let to SQL Server to manage its LOG file in terms of size ,
so set the recovery model to SIMPLE
For more info please refer to the BOL
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
found a
> way to keep the logs file clear?
> Att,
> RODOLFO|||Hi,
We can not totally stop loggin in sql server.
But if you select the RECOVERY model for your database as SIMPLE then
transaction log will be cleared automatically
Has anyone found a way to keep the logs file clear?
If it is SIMPLE recovery log will be cleared automatically, but for other
recovery model you need to perform the transaction log backup.
See Backup Log command in books online.
Thanks
Hari
SQL Server MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
> it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
> found a
> way to keep the logs file clear?
> Att,
> RODOLFO|||To add to the other responses, the transaction log is required in order to
maintain database consistency. This is used by SQL Server to guarantee
all-or-nothing atomic transactions. Although the log can be used by
third-party tools for auditing purposes, the primary purpose of the log is
to facilitate the backout and roll-forward of transactions.
You can keep transaction log file size reasonable by choosing the
appropriate recovery model and backup strategy for your environment.
Hope this helps.
Dan Guzman
SQL Server MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
> it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
> found a
> way to keep the logs file clear?
> Att,
> RODOLFO|||Hello and thanks a lot for your answers.
I think I understand better the purpose of the log file now reading your
posts. The problem is that it just confirms my fears. I need NO ONE to be
able to perform an audit on this database. The ideal situation will be to
disable this logging. Now I know it can't be done in MS SQL... what's the
closest to it I can get?
Att,
RODOLFO
"Dan Guzman" wrote:

> To add to the other responses, the transaction log is required in order to
> maintain database consistency. This is used by SQL Server to guarantee
> all-or-nothing atomic transactions. Although the log can be used by
> third-party tools for auditing purposes, the primary purpose of the log is
> to facilitate the backout and roll-forward of transactions.
> You can keep transaction log file size reasonable by choosing the
> appropriate recovery model and backup strategy for your environment.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
> news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
>
>|||If you don't want anyone to read the log then don't give them permissions to
that folder. The physical security of the data files is up to you at the
Windows level.
Andrew J. Kelly SQL MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:634187D5-A399-4B4A-85D4-3CA9C7FF62B0@.microsoft.com...[vbcol=seagreen]
> Hello and thanks a lot for your answers.
> I think I understand better the purpose of the log file now reading your
> posts. The problem is that it just confirms my fears. I need NO ONE to be
> able to perform an audit on this database. The ideal situation will be to
> disable this logging. Now I know it can't be done in MS SQL... what's the
> closest to it I can get?
> Att,
> RODOLFO
> "Dan Guzman" wrote:
>

How to clear the log (ldf) file?

Hi all.
I have a database I need no auditor to be able to track changes made to it.
As far as I know, the LDF file keeps a record of all the transactions
performed on it which is exactly what I dont want. I've read that it is
impossible to disable logging in MSSQL. Is this 100% true? Has anyone found a
way to keep the logs file clear?
Att,
RODOLFOYes, you are right that we cannot "disable"logging in the SQL Server.
If you want to let to SQL Server to manage its LOG file in terms of size ,
so set the recovery model to SIMPLE
For more info please refer to the BOL
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
found a
> way to keep the logs file clear?
> Att,
> RODOLFO|||Hi,
We can not totally stop loggin in sql server.
But if you select the RECOVERY model for your database as SIMPLE then
transaction log will be cleared automatically
Has anyone found a way to keep the logs file clear?
If it is SIMPLE recovery log will be cleared automatically, but for other
recovery model you need to perform the transaction log backup.
See Backup Log command in books online.
Thanks
Hari
SQL Server MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
> it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
> found a
> way to keep the logs file clear?
> Att,
> RODOLFO|||To add to the other responses, the transaction log is required in order to
maintain database consistency. This is used by SQL Server to guarantee
all-or-nothing atomic transactions. Although the log can be used by
third-party tools for auditing purposes, the primary purpose of the log is
to facilitate the backout and roll-forward of transactions.
You can keep transaction log file size reasonable by choosing the
appropriate recovery model and backup strategy for your environment.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> Hi all.
> I have a database I need no auditor to be able to track changes made to
> it.
> As far as I know, the LDF file keeps a record of all the transactions
> performed on it which is exactly what I dont want. I've read that it is
> impossible to disable logging in MSSQL. Is this 100% true? Has anyone
> found a
> way to keep the logs file clear?
> Att,
> RODOLFO|||Hello and thanks a lot for your answers.
I think I understand better the purpose of the log file now reading your
posts. The problem is that it just confirms my fears. I need NO ONE to be
able to perform an audit on this database. The ideal situation will be to
disable this logging. Now I know it can't be done in MS SQL... what's the
closest to it I can get?
Att,
RODOLFO
"Dan Guzman" wrote:
> To add to the other responses, the transaction log is required in order to
> maintain database consistency. This is used by SQL Server to guarantee
> all-or-nothing atomic transactions. Although the log can be used by
> third-party tools for auditing purposes, the primary purpose of the log is
> to facilitate the backout and roll-forward of transactions.
> You can keep transaction log file size reasonable by choosing the
> appropriate recovery model and backup strategy for your environment.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
> news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
> > Hi all.
> > I have a database I need no auditor to be able to track changes made to
> > it.
> > As far as I know, the LDF file keeps a record of all the transactions
> > performed on it which is exactly what I dont want. I've read that it is
> > impossible to disable logging in MSSQL. Is this 100% true? Has anyone
> > found a
> > way to keep the logs file clear?
> >
> > Att,
> > RODOLFO
>
>|||If you don't want anyone to read the log then don't give them permissions to
that folder. The physical security of the data files is up to you at the
Windows level.
--
Andrew J. Kelly SQL MVP
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:634187D5-A399-4B4A-85D4-3CA9C7FF62B0@.microsoft.com...
> Hello and thanks a lot for your answers.
> I think I understand better the purpose of the log file now reading your
> posts. The problem is that it just confirms my fears. I need NO ONE to be
> able to perform an audit on this database. The ideal situation will be to
> disable this logging. Now I know it can't be done in MS SQL... what's the
> closest to it I can get?
> Att,
> RODOLFO
> "Dan Guzman" wrote:
>> To add to the other responses, the transaction log is required in order
>> to
>> maintain database consistency. This is used by SQL Server to guarantee
>> all-or-nothing atomic transactions. Although the log can be used by
>> third-party tools for auditing purposes, the primary purpose of the log
>> is
>> to facilitate the backout and roll-forward of transactions.
>> You can keep transaction log file size reasonable by choosing the
>> appropriate recovery model and backup strategy for your environment.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
>> news:99344364-41EF-46BB-A7F2-6621D7944A51@.microsoft.com...
>> > Hi all.
>> > I have a database I need no auditor to be able to track changes made to
>> > it.
>> > As far as I know, the LDF file keeps a record of all the transactions
>> > performed on it which is exactly what I dont want. I've read that it is
>> > impossible to disable logging in MSSQL. Is this 100% true? Has anyone
>> > found a
>> > way to keep the logs file clear?
>> >
>> > Att,
>> > RODOLFO
>>

How to clear the Conflict tables from database

Dear Friends
I have created a Mearge Replication with name TEST for database DBTEST I
have deleted the same Replicaiton but now in my Database DBTEST i see the
tables with name Conflict_TEST_TableName
How i can clean the same.
Your guidance will enable me to solve the problem.
Thanks and best regards
Shailesh.
Shailesh,
you can drop these tables using query analyser.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

How to clear table?

Is there a way to clear all the records in a table in Microsoft SQLServer Management Studio instead of selecting all the rows and delete?

Try the link below and Truncate the table. Hope this helps.

http://msdn2.microsoft.com/en-us/library/ms177570.aspx

|||Thanks for the response, but I'm not looking for a code clear records.I am in Microsof SQL Management Studio. How do I clear the table withinthis tool?|||

Assuming no constraint defined on the table try the link below for a walkthrough. Hope this helps.

http://msdn2.microsoft.com/en-us/library/ms175491.aspx

|||That instruction only show how to delete a column. Are you suggestingthat deleting the column and then recreate that same column?|||

Sorry wrong link.

http://msdn2.microsoft.com/en-us/library/ms190616.aspx

|||That link shows how to delete the whole tabe. I don't want to deletethe whole table. All I want is to clear all the records in the table. Idon't want to recreate the whole table again.|||Truncate is the clean way to do it or you have to do it by column because a database table is columns with your data in rows so if you don't want to truncate you have to do it by column.|||The reason I asked about clearing the table records is because inphpMyAdmin with MySQL, it is very simple to clear the whole records ina table. I would be very surprise if Microsoft does not have thisfeature in their MS SQL Management Studio tool.|||

MySQL is generally free so you can do crude things but SQL Server cost a lot of money companies will not like data delete operations that cannot be traced. So the links below explain Truncate and Delete very clearly and some solutions using temp table. Hope this helps.

http://codebetter.com/blogs/raymond.lewallen/archive/2005/05/09/62960.aspx

http://www.sql-server-performance.com/q&a118.asp

|||Thanks! I will give those two links some reading.

How to clear log ?

Hi,
I am using SQL sever 2000,
My server said, the Log file for MSDB is full, what should I do to clear the
log history?
Thanks
MichaelFairly simple - back up & truncate the log.
You can do this either via the SQL Enterprise Manager or issuing the backup
log command, but before you rush off trying to do that, if you've got DBAs
you're probably best off approaching them as this is something they'd
normally look after.
Regards,
Greg Linwood
SQL Server MVP
"Michael" <vbvfvid@.yahoo.com.sg> wrote in message
news:%238DMrtbyDHA.3220@.tk2msftngp13.phx.gbl...
> Hi,
> I am using SQL sever 2000,
> My server said, the Log file for MSDB is full, what should I do to clear
the
> log history?
> Thanks
> Michael
>|||Is there any Transaction-SQL cmd can clear the logs?
I checked the database, it only sized 14MB, please tell me how to enlarge
the log file history or size? Is there any documents talking about this?
Thanks
Michael
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:Oa0xVzbyDHA.1908@.TK2MSFTNGP10.phx.gbl...
> Fairly simple - back up & truncate the log.
> You can do this either via the SQL Enterprise Manager or issuing the
backup
> log command, but before you rush off trying to do that, if you've got DBAs
> you're probably best off approaching them as this is something they'd
> normally look after.
> Regards,
> Greg Linwood
> SQL Server MVP
> "Michael" <vbvfvid@.yahoo.com.sg> wrote in message
> news:%238DMrtbyDHA.3220@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > I am using SQL sever 2000,
> > My server said, the Log file for MSDB is full, what should I do to clear
> the
> > log history?
> >
> > Thanks
> > Michael
> >
> >
>|||Hi Michael.
The term for "clearing" the transaction log is "truncating" the transaction
log. This will help you research the topic. Truncation of the transaction
log is usually performed whilst backing up the transaction log.
There is an article in the online SQL Server documentation on this here:
http://msdn.microsoft.com/library/en-us/architec/8_ar_da2_7vaf.asp
If you want to enlarge the transaction log via a t-sql command, you do this
via the ALTER DATABASE command, using it's MODIFY FILE argument. Eg:
ALTER DATABASE [database name]
MODIFY FILE (
NAME = [logical file name]
, SIZE = [target size]
)
Managing transaction logs is one of the fundamental aspects of managing SQL
Server databases (as with Oracle, DB2 etc). It's worth reading up more on
this as it will help build your knowledge of SQL Server significantly.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Michael" <vbvfvid@.yahoo.com.sg> wrote in message
news:%23bo1u%23byDHA.3888@.tk2msftngp13.phx.gbl...
> Is there any Transaction-SQL cmd can clear the logs?
> I checked the database, it only sized 14MB, please tell me how to enlarge
> the log file history or size? Is there any documents talking about this?
> Thanks
> Michael
>
>
> "Greg Linwood" <g_linwoodQhotmail.com> wrote in message
> news:Oa0xVzbyDHA.1908@.TK2MSFTNGP10.phx.gbl...
> > Fairly simple - back up & truncate the log.
> >
> > You can do this either via the SQL Enterprise Manager or issuing the
> backup
> > log command, but before you rush off trying to do that, if you've got
DBAs
> > you're probably best off approaching them as this is something they'd
> > normally look after.
> >
> > Regards,
> > Greg Linwood
> > SQL Server MVP
> >
> > "Michael" <vbvfvid@.yahoo.com.sg> wrote in message
> > news:%238DMrtbyDHA.3220@.tk2msftngp13.phx.gbl...
> > > Hi,
> > >
> > > I am using SQL sever 2000,
> > > My server said, the Log file for MSDB is full, what should I do to
clear
> > the
> > > log history?
> > >
> > > Thanks
> > > Michael
> > >
> > >
> >
> >
>|||By default the MSDB database is in simple mode which would truncate the log
upon checkpoint and not allow for the log to grow too big. If the recov mode
for MSDB has been changed to full recov, you should implement regular backup
log commands or jobs to keep this in check, lookup backup log in BOL for
syntax or use a maint plan
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Michael" <vbvfvid@.yahoo.com.sg> wrote in message
news:%23bo1u%23byDHA.3888@.tk2msftngp13.phx.gbl...
> Is there any Transaction-SQL cmd can clear the logs?
> I checked the database, it only sized 14MB, please tell me how to enlarge
> the log file history or size? Is there any documents talking about this?
> Thanks
> Michael
>
>
> "Greg Linwood" <g_linwoodQhotmail.com> wrote in message
> news:Oa0xVzbyDHA.1908@.TK2MSFTNGP10.phx.gbl...
> > Fairly simple - back up & truncate the log.
> >
> > You can do this either via the SQL Enterprise Manager or issuing the
> backup
> > log command, but before you rush off trying to do that, if you've got
DBAs
> > you're probably best off approaching them as this is something they'd
> > normally look after.
> >
> > Regards,
> > Greg Linwood
> > SQL Server MVP
> >
> > "Michael" <vbvfvid@.yahoo.com.sg> wrote in message
> > news:%238DMrtbyDHA.3220@.tk2msftngp13.phx.gbl...
> > > Hi,
> > >
> > > I am using SQL sever 2000,
> > > My server said, the Log file for MSDB is full, what should I do to
clear
> > the
> > > log history?
> > >
> > > Thanks
> > > Michael
> > >
> > >
> >
> >
>|||backup log urdatabase with no_log
dbcc shrinkdatabase (urdatabase)
backup ur database afterwards.

How to clear all database connection using SQLDMO?

Hello guys! I'm using SQLDMO to restore a database backup. The problem is, the program cannot restore the backup if there are active connections using the database. Is there are way to clear all database connections using SQLDMO (or other libraries)? Thanks in advance

You could create a storedproc in master that kills any existing spids per db, then run that proc from DMO as part of the restore job.. something like this

CREATE procedure sp_KillOldspids

@.dbName varchar (30) = NULL
AS

set nocount on

declare @.currentspid int,@.cmdstring varchar(30)

dECLARE OPENSPIDS CURSOR FOR SELECT [SPID] from [MASTER].[DBO].[SYSPROCESSES] WHERE DBID = db_id (@.dbName)
OPEN OPENSPIDS

FETCH NEXT FROM OPENSPIDS INTO @.CURRENTSPID

WHILE @.@.FETCH_STATUS = 0
BEGIN

SELECT @.cmdString = 'kill ' + convert(varchar(10), @.CURRENTspid)
IF @.@.SPID <> @.CURRENTSPID
BEGIN
EXEC (@.cmdString)
END
FETCH NEXT FROM OPENSPIDS INTO @.CURRENTSPID

END

CLOSE CURRENTSPIDS
DEALLOCATE CURRENTSPIDS

hopes this helps.