Showing posts with label names. Show all posts
Showing posts with label names. Show all posts

Friday, March 30, 2012

Log of database changes

Hi All,
I would like to know if it is possible to figure out what user change the field names of one of my tables
on my SQL Server.
It seems that somebody change and after all nobody it guilty.
Do you know?
Thanks in advance
Roberto
You should be able to find the log entry for ALTER TABLE or sp_rename if it
was recent enough.
http://www.lumigent.com/products/le_sql/le_sql.htm
http://www.lockwoodtech.com/index_lognavigator.htm
http://www.logpi.com/
http://www.apexsql.com/
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
(Reverse e-mail to reply.)
"Roberto C3" <anonymous@.discussions.microsoft.com> wrote in message
news:A4CEF9C9-5F8E-464C-BA3C-29DD271D1386@.microsoft.com...
> Hi All,
> I would like to know if it is possible to figure out what user change the
> field names of one of my tables
> on my SQL Server.
> It seems that somebody change and after all nobody it guilty.
> Do you know?
> Thanks in advance
> Roberto

Log of database changes

Hi All
I would like to know if it is possible to figure out what user change the field names of one of my table
on my SQL Server
It seems that somebody change and after all nobody it guilty
Do you know
Thanks in advanc
RobertoYou should be able to find the log entry for ALTER TABLE or sp_rename if it
was recent enough.
http://www.lumigent.com/products/le_sql/le_sql.htm
http://www.lockwoodtech.com/index_lognavigator.htm
http://www.logpi.com/
http://www.apexsql.com/
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
(Reverse e-mail to reply.)
"Roberto C3" <anonymous@.discussions.microsoft.com> wrote in message
news:A4CEF9C9-5F8E-464C-BA3C-29DD271D1386@.microsoft.com...
> Hi All,
> I would like to know if it is possible to figure out what user change the
> field names of one of my tables
> on my SQL Server.
> It seems that somebody change and after all nobody it guilty.
> Do you know?
> Thanks in advance
> Roberto

Log of database changes

Hi All,
I would like to know if it is possible to figure out what user change the fi
eld names of one of my tables
on my SQL Server.
It seems that somebody change and after all nobody it guilty.
Do you know?
Thanks in advance
RobertoYou should be able to find the log entry for ALTER TABLE or sp_rename if it
was recent enough.
http://www.lumigent.com/products/le_sql/le_sql.htm
http://www.lockwoodtech.com/index_lognavigator.htm
http://www.logpi.com/
http://www.apexsql.com/
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
(Reverse e-mail to reply.)
"Roberto C3" <anonymous@.discussions.microsoft.com> wrote in message
news:A4CEF9C9-5F8E-464C-BA3C-29DD271D1386@.microsoft.com...
> Hi All,
> I would like to know if it is possible to figure out what user change the
> field names of one of my tables
> on my SQL Server.
> It seems that somebody change and after all nobody it guilty.
> Do you know?
> Thanks in advance
> Roberto

Friday, March 9, 2012

Log file

How can I get the names of Log Files for a particular database?And how can I truncate or shrink the log files in SQL SERVER?Right click on DB & look @. Properties 2 get LogFile Name
& Run
Backup Log 'DBName' WITH Truncate_Only

GW|||To see the log file name do as GWilliy wrote.
To truncate teh log you can force a maximum value for the log file but that it's not the best way to keep it small. It better to implement some mantainence plans that backup and shrink the database log file.

Originally posted by subhasishray
How can I get the names of Log Files for a particular database?And how can I truncate or shrink the log files in SQL SERVER?|||To see the files (including MDF and LDF) you can run

sp_helpfile

If you do not require transactional recovery you can run

backup log dbname with truncate_only

And you can set the recovery mode to simple to keep the log small.

If you do require transactional recovery, schedule regular T-log backups. If you want transactional recovery, be careful with shrinking the log file as it is a performance hit when SQL has to allocate more space to grow the log when it is too small.

HTH