Tags: transactional replication distribution Transactional replicationHow to handle large transaction operations in SQL Server transactional replicationWorking mechanism of transactional replicationTransactional replication is implemented by the SQL Server Snapshot Agent, th
backups, because I have backed up the ZP database two times, and the data files for the two backups are the same. Here we select the most recent time backup
The default settings in the database are as follows: Append to the backup set, so there will be two backups, as shown below:
Also, set the "Do not rollback" transaction in "Options".
Note: Restore the database through the transaction
"Guide" This article focuses on SQL Server 2000, which describes how to use SQL Server log transfer to implement high availability of a database.
Clustering is an effective solution for achieving high availability, sometimes counterproductive. And it's very expensive. As a
log on the production database unless you have sufficient reason and sufficient certainty, or ...
It's not you who take responsibility.
Now that this method is unsafe, I'll introduce a secure approach.
As you know, SQL Server automatically truncates the inactive portions of the transaction
Use masterdrop TABLE CustomerCREATE TABLE Customer (ID int PRIMARY KEY,Account decimal Check (account>0),Name varchar (20))--use MasterALTER TABLE Dbo.customerAdd Check (customer.account>0)SELECT * FROM CustomerINSERT into customer values (2012090101,2000, ' Zhang San ');INSERT into customer values (2012090102,1000, ' John Doe ');INSERT into customer values (2012090103,1000, ' Harry ');BEGIN TRANSACTIONDECLARE @sum intSet @sum =0Update customer set account-=200 where customer.id=2012090101Set @s
This article is the fifth of the SQL Server Agent series, please refer to the original text for more information.
As mentioned in the previous series, SQL Server Agent jobs are composed of a series of job steps, each of which is executed by a separate type. In the fourth chapter we see that
A few days ago "read" "Sqlserver2005 Advanced Program Design" and "The introduction of SQL Server 2008 Programming Classic (3rd edition)," The two translations of the Chinese version of the book. found that the directory structure is roughly the same, the content of the explanation is almost the same. There is suspicion of plagiarism. See the "Transaction and loc
Label:1 , phenomenon, problem description Customer reflects that a client can not login, the client program log display "Connection database timeout"; Check the corresponding database server, the log shows "autogrow of file" a database log file ' in the database ' a DB ' is cancelled by user or T Imed out after 2391 mi
default first is 0%, the other two is unchecked, Dot OK-If your previous database log file is greater than 1M then look now, is not only 1 m. 3, after the operation--"in the first step, the" failure to restore ", selected" complete ", the legendary SQL Server 2000 has the automatic restore function, That is, if the illegal shutdown factors such as data loss c
Server
Role changes, role swaps, and monitoring server location
When an online database is shut down (either planned maintenance or unplanned), you might be more comfortable if the database on the standby server is available for access. A well-designed log shipping system that delivers the database
then replace the data file of the new library with the attached failed data file, and then set the database as the Emergency Recovery mode, so that the data can be read in generalALTER DATABASE db_name SET EMERGENCYAfter the database can be read, you can try to set it to ONLINE mode, if successful, then DBCC CHECKDB once, confirm no problemIf you can't online, you probably have to create a new library and then take the data from the contingency mode library to the new library.Special Note: The
Cause Analysis and Solution for SQL Server failure to contract log files, SQL Cause Analysis
An error is reported when the server executes a job that compresses the log file size recently.
One of my batch
Settings dialog box, select the time of retention, more than the retention time, the full backup record will be deleted. 19, double-click the "Clear Maintenance" box, pop Up the Settings dialog box, choose the time of retention, more than the retention time, the full backup file will be deleted, note the path to set the backup file, and the extension bak, not. bak. 20, after the setup is complete, this is the case. 21, the following two sub-plans,
to standard mode, with the 1th, because the log is often an important basis for restoring the database in some unusual cases.
However, the server can use the following statement to execute in Query Analyzer
Copy Code code as follows:
DUMP TRANSACTION [Jc8] with no_log
BACKUP LOG [Jc8] with no_log
D
the amount of VLF in the transaction log. If you feel VLF too much, you can reduce it in the following ways:
1. Clear the log (such as through log backups, etc. truncate log)
2. Manually shrink the
SQL Server is a relational database management system, the application is very extensive, in the process of SQL Server database operations will inevitably occur mistakenly deleted or other reasons caused by log damage, and because of the importance of data in
SQL2008 Empty Delete log:
Method One:
Use [master]
to
ALTER DATABASE AFMS set RECOVERY simple and no_wait
go
alter DATABASE AFMS SET RECOVERY S Imple
go
to Afms
go
DBCC shrinkfile (N ' Afms_log ', one, truncateonly) go use
[master]
Go
ALTER DATABASE AFMS set RECOVERY full and no_wait
go
alter DATABASE AFMS SET RECOVERY full
Go
' Clearing the log in SQL2008 must be done in simple mode, until th
disk space may be full, affecting access. Therefore, it is more practical to set Automatic cleanup of database log files.
Manual cleaning method: Right-click the database to be cleaned up, select "properties", set the fault recovery model to simple on the "options" card, click OK, and close. Then, right-click the database, "All tasks"-"shrink Database". After confirmation, you can clear the
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.