sql server replication monitor script

In general, we will use the database maintenance plan provided by SQL Server to define the backup.However, sometimes the maintenance plan of some machine databases cannot be successfully backed up.The error cause may be different. In this case, we can use a simple SQL Server backup

I encountered a requirement in my work. I had to query the table structure, index, and primary key, but it was suddenly difficult because the script I wrote for the first time was only compatible with SQL Server 2005, in SQL Server 2000, an error is reported. If it is depres

As the database accumulates over time and experienced developers are different in different styles, the objects in the database are messy. In order to comply with the IT integration trend, improve the maintainability and scalability of the system and database, and decide to integrate the system, database and server It's just the beginning. The following is a newly written script that captures and summarizes

server| Script Set conn = Server.CreateObject ("ADODB. Connection ") Conn.Open "ODBC name", "username", "password" Sql1= "SELECT * from dbo.sysobjects where type is not in (' S ', ' D ', ' K ')" Sql1= "SELECT * from dbo.sysobjects where type = ' U '" Set RSCC = Server.CreateObject ("Adodb.recordset") Set rs = Server.CreateObject ("Adodb.recordset") Rscc.open sql1,conn,1,2 Do as not rscc.eof

$query = "SELECT @ @servername" $csvFilePath = "c:\Scripts\queryresults.csv" $instanceNameList = get-content c:\Scripts\ Serverlist.txt[email protected] () foreach ($instanceName in $instanceNameList) {write-host "executing query against Server: "$instanceName $results + = Invoke-sqlcmd-query $query-serverinstance $instanceName} # Output to CsvwritE-host "Saving Query Results in CSV format ..." $results | Export-csv $csvFilePath-notypeinformationPower

I like to think of the tools bundled with SQL servers as inverted pyramid. tools for diagnosing and checking general problems are at the top, and tools for finding and diagnosing specific areas of problems are at the bottom. In addition to providing a convenient way to write SQL scripts, the QueryAnalyzer still needs to be used when you need to solve specific SQL

SQL Script for read information from a csv file in FTP Server, scriptcsv DECLARE w_file_path VARCHAR2(4000) := 'XXIF_INPUT'; --all_directories.directory_name w_file_name VARCHAR2(4000) := 'lcytest001.csv'; --The file name w_file_exists BOOLEAN; w_file_length NUMBER(10) DEFAULT 0; w_file_type utl_file.file_type; w_line VARCHAR2(4000) DEFAULT NUL

Label:--视图、存储过程、函数名称DECLARE @NAME NVARCHAR(255);--局部游标DECLARE @CUR CURSOR--自动修改未上状态为旷课SET @CUR=CURSOR SCROLL DYNAMIC FORSELECT NAME FROM DBO.SYSOBJECTS WHERE NAME NOT IN (‘SYSCONSTRAINTS‘,‘SYSSEGMENTS‘)AND(OBJECTPROPERTY(ID, N‘IsView‘) = 1 --视图OR OBJECTPROPERTY(ID,N‘IsProcedure‘) = 1 --存储过程OR OBJECTPROPERTY(ID,N‘IsScalarFunction‘) = 1 --标量函数OR OBJECTPROPERTY(ID,N‘IsTableFunction‘) = 1 --标题函数OR OBJECTPROPERTY(ID,N‘IsInlineFunction‘) = 1 --内联函数);OPEN @CUR;FETCH NEXT FROM @CUR INTO @NAMEWHILE (@@FE

Use [Master]GOALTER DATABASEF360dwSETRECOVERY Simple withno_waitGOALTER DATABASEF360dwSETRECOVERY Simple--Simple ModeGO UseF360DWGODBCCShrinkfile (N'F360dw_log', One, Truncateonly)/*--Dnname_log here if you do not know what the name is in Sys.database_files, you can use the following comments to query the statement using the F360dwgoselect file_id, name from sys.database_files; GO*/GO Use [Master]GOALTER DATABASEF360dwSETRECOVERY Full withno_waitGOALTER DATABASEF360dwSETRECOVERY Full --revert t

Problem Description: You want to copy the tables and fields from one database to another database;Method One: A. Generate script file Select Database right button-"task-" Generate script;B. Select a specific database object-"next step;"C. Advanced-"Scripting data type selection architecture and data-" Select the generated script file location-"next;D. Next-"Next"

I like to think of the tools bundled with SQL servers as inverted pyramid. Tools for diagnosing and checking general problems are at the top, and tools for finding and diagnosing specific areas of problems are at the bottom. In addition to providing a convenient way to write SQL scripts, the Query Analyzer still needs to use resources when you need to solve specific SQL