this procedure is an interface to bcp it gets database name,table name , file and path,,mode E/I for export/import and seperator character user and password and exports/imports text files from / to SQLSERVER
2002-07-10
1,426 reads
There are various utilities for scripting MS SQL Server objects : Tables , Procedures , Functions .... etc ...Small piece of code that will allow you to script all jobs from your SQL Server using SQL DMO object.
2002-06-17
1,312 reads
This script will create a procedure to list all databases on the server (except tempdb), the last time the database was backed up (database backup, not log backups), and a comment which could be customized. For my purposes, I flag any database which hasn't been backed up in the last week. This provides a quick […]
2002-06-14
3,147 reads
Set the Autoclose database option to True and perform a cold backup of your data files without even shutting down the SQL Server Services.
2002-04-25
947 reads
There are times you want to kill all the connections in a database. This would do that trick. This can be very useful when you replace a database regularly and some connections still exist so your automated restore fails. You can issue this command to kill all the connections before issuing a restore command.
2002-04-17
2,516 reads
This procedure when executed with the correct parameters, backs up a database in the specified directory pathUsage :exec USP_BACKUPDATABASE databasename, directory_path
2002-03-12
590 reads
When rebuilding a server or setting up a backup or DR server the logins need to be added into master and synchronised with the user databases.Inevitably there are orphaned users is sysusers or the sid's do not match with syslogins.I use this stored procedure to check for a particular user when the user experiences a […]
2002-03-07
821 reads
This Stored Procedure will display object level permissionsfor stated User or Role.Procedure output is ready to execute batch.Usage: Exec ScriptPermissions 'public'
2002-02-27
1,410 reads
Script to check whether a file exists with todays date and performs an action based on whether the file exisits or not. We use this to check whether backups have completed from another SQL Srver and if they have completed we restoe on a server used for management information
2002-01-09
2,056 reads
When the transaction log is full, sometimes the SQLServer 6.5 and 6.0 does not clear the transactions after dump command. This situation occours because not enough more page to record a end-point for transaction.
2002-01-06
267 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers