sql server login auditing log

One, what is log shipping? The principle is simple, three actions six words: Backup-> replication-> recovery. If a person completes this three action, it can only be called a log porter, and the SQL Server job completes automatically, called Log shipping. The same thing, n

In the past, SQL Server databases were cleared using statements. Of course, the database can be detached and files can be cleared. Currently, there are many users using SQL Server express databases, and the Express version is equivalent to the database being separated. The database file and

Log files read from the installation directory: Mssql\log\errorlog--this'll hold the rowscreate TABLE #ErrorLog (logdate datetime, ProcessInfo VarChar ( ErrorMessage VarChar (Max))--Dump the errorlog into the Tableinsert into #ErrorLogEXEC master.dbo.xp_readerrorlog--D Elete everything older than 5 minutes--ideally you'll store the max date when it ran Lastdelete #ErrorLogWHERE logdate Exec xp_readerrorlog

1. OverviewLOG Shipping The database backup process provided for SQL Server. It can replicate the entire database to another server. In this case, the transaction log is also periodically sent to the backup server for data recovery purposes, which keeps the

Note: Stored Procedures can prevent the threat of SQL Injection Vulnerabilities and are very secure. The Stored Procedure contains input and output parameters. The input parameters include the user ID and password. The returned values indicate different results. Alter procedure [DBO]. [logining] (@ in_id varchar (10), @ in_password varchar (10), @ out_parameter varchar (10) Output) /** @ in_id input parameter ID @ in_password input parameter passwor

production database unless you have sufficient reason and enough certainty, or ... It's not you who takes responsibility. Now that this method is unsafe, I'll introduce a safe approach. As you know, SQL Server automatically truncates the inactive part of the transaction log when it completes the transaction log backup

server| Solution | data | database The first is to provide a complex method for compressing logs and database files as follows: 1. Empty logDUMP TRANSACTION Library name with NO_LOG2. Truncate the transaction log:BACKUP LOG database name with NO_LOG3. Shrink the database file (if not compressed, the database file will not be reducedEnterprise Manager--right--the database you want to compress--all tasks--shr

SQL 2008 log Files account for 23G of hard disk space, and the transaction log has been truncated (Truncate), the actual log content is small, 1G is not, want to release the extra space occupied by the log files. However, no matter how you shrink (Shrink)

AccessThe operation is very simple. The specific steps are as follows: Open your mdb database, tools> Database Utilities> compress and restore the database (c )...SQL SERVER In general, the contraction of the SQL database does not greatly reduce the size of the database. Its main function is to shrink the log size. Thi

We all know that from winforms applications ProgramTo access the database server, use the connection string. If you are using a user name/password for connection, we usually encrypt the connection string to enhance security. This is far from enough. Through the network packet capture tool, we can intercept data packets of the TDS protocol adopted by SQL Server