Skip to main content

XCOPY

Ctrl + C and Ctrl + V is the easiest thing that a person can do in computers ,  but I had the most difficult copy scripts to run. (Well ... I better have an good explanation for wasting so much time in copying stuff over ;P)

I had to copy files from one server to another over different domains  ... phew. Thank God that it is over. Writing a simple copy did not help, I used XCOPY. I thought why not share my experience with all, and what better place to share than this.

To write a copy script one must keep few things in mind...
  • Keep it simple
            xcopy source [destination]
         
            Destination is not mandatory , if you don't give it then it will copy to the current folder from where you are running the script.
  • Keep every thing in Quotes
            xcopy "source" "[destination]"
            
            Make sure that your source and destination are in quotation marks. That will save you from the horror of not knowing what went wrong. Spaces in the file name or file path can cause xcopy to think that the 2nd part is the destination :(
  • echo f
                Ever seen this :  Does <destination> specify a file name or directory name on the target (F = file, D = directory)?
            Microsoft does provide you with the convenient option of using /i . But what if you don't want it to default it to Directory and reply as file instead?  Imagine how annoying it can be when you have to enter 'f' continuously. That's the last thing how you want to start your day doing. Echo f cam to my rescue. Start the xcopy with echo   f   | so that when the command prompt asks you if it is a file or directory it gets the answer f , that is file.
  • Can't find it
            Make sure that the source file path is correct and you have the necessary permission to read and write to the machine.
  • Need a Log??
            I know that annoying . How can you know what failed and what passed. I can tell you how. Use test.bat >> test.log to redirect the output of the bat file to the log file .

Now you can look at the errors.

A simple example :
echo f | xcopy  "A\B\c.txt" "X\y\z.txt"



Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)

While accessing the active directory (AD) and authorization manager (AZMAN) , If you get “   Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)  “ message check the    account that is being used to get the LDAP query from AD .  ERROR DETAILS Exception Details:  System.Runtime.InteropServices.COMException: Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098) Source Error: Line 154:    'Session("FullName") = System.Security.Principal.WindowsIdentity.GetCurrent.Name.ToString() Line 155: Line 156:    If Not User.IsInRole("Role1") Then Line 157:          Response.Redirect("./Login.aspx") Line 158:    End If  Stack Trace : .... SOLVE IT Steps to do check the app pool rights: Click on the website name that you are having problem with in IIS  In the right panel you will se...
Post a Comment
Read more

SQL Server 2008 - Inline Variable Assignment

Microsoft SQL Server 2008 brings in a new feature of 'Declaring and Assigning' a variable all in a single line. Earlier, while using SQL 2005 and earlier versions, we had to declare a variable before assigning it. This feature is explained in detail below. In SQL 2005 and earlier versions we had to write: Declare @age int Declare @name nvarchar(25) Declare @date date Set @age = 25 Set @name = "Garry" Set @date = GETDATE() With SQL 2008 we can combine both these statements to write Declare @age int = 25 Declare @name nvarchar(25) Declare @date @date = GETDATE() Advantage : This helps us to write less code, yet get the same functionality. Even though this feature has been available it is not being used in many projects because of backward compatibility issue. If the same code is being used on both 2005 and 2008 server we would prefer writing in a format compatible to both. Do share with us :  Would you like to use this new method? If not, why?
Post a Comment
Read more

Do's and Don't SQL

Do's: Writing comments whenever something is not very obvious, as it won’t impact the performance.  (--) for single line  (/*…*/) to mark a section Use proper indentation Use Upper Case for all SQL keywords. SELECT, UPDATE, INSERT, WHERE, INNER JOIN, AND, OR, LIKE. Use BEGIN... END block for multiple statements in conditional code  Use Declare and Set in beginning of Stored procedure Create objects in same database where its relevant table exists otherwise it will reduce network performance. Use PRIMARY key in WHERE condition of UPDATE or DELETE statements as this will avoid error possibilities. If User table references Employee table than the column name used in reference should be UserID where User is table name and ID primary column of User table and UserID is reference column of Employee table. Use select column name instead of select * Use CTE (Common Table Expression); its scope is limited to the next statement in SQL query, instead of...
Post a Comment
Read more