Post reply

Having problem openning SQL scripts

  • October 20, 2013 at 1:13 am

    #300294

    I have some TSQL scripts which ran successfully a week before and now suddenly when I open these files in SSMS its asking me to choose encoding, I am not sure what to select and If I choose 'Auto- detect' from the dropdown its opening the file but the file is empty ( no code).

    When I look at these file sizes it is 256 KB for all the files, not sure what is happening , so cananyone please help me on this as these scripts are very essential for me for a deployment early next week :crying:

  • October 20, 2013 at 2:16 am

    #1659953

    shashi_1409 (10/20/2013)

    I have some TSQL scripts which ran successfully a week before and now suddenly when I open these files in SSMS its asking me to choose encoding, I am not sure what to select and If I choose 'Auto- detect' from the dropdown its opening the file but the file is empty ( no code).

    When I look at these file sizes it is 256 KB for all the files, not sure what is happening , so cananyone please help me on this as these scripts are very essential for me for a deployment early next week :crying:

    Have you tried opening your TSQL Scripts in notepad to see if it is view able?

    --------------------------------------------------
    ...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀

  • October 20, 2013 at 4:35 am

    #1659961

    If those files are on a network share, ask your admin responsibe for that share if a backup from last week is available and if they're able to restore the files in question. If tose files are gone then I think you'll need to rewrite the code.


    Lutz
    A pessimist is an optimist with experience.

    How to get fast answers to your question[/url]
    How to post performance related questions[/url]
    Links for Tally Table [/url] , Cross Tabs [/url] and Dynamic Cross Tabs [/url], Delimited Split Function[/url]

  • October 20, 2013 at 6:37 am

    #1659966

    I have tried openning the file in notepad and it didnt work...any help how to address this issue is greatly appreciated.

  • October 21, 2013 at 5:31 am

    #1660097

    Pls open ur scripts file and see what is showing ur encoding "dropdown".Please make sure it is "ANSI".If not then save the fille with "ANSI" encoding type and they try to open from SSMS.

  • October 21, 2013 at 6:18 am

    #1660102

    do that files contain INSERT statements ? with N' characters

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

  • October 21, 2013 at 9:11 am

    #1660162

    Ramesh, when you said open the files and check encoding , do you mean opening it in notepad and check the encoding( I checked and it is ANSI).

    Thanks

    Shashi

  • October 21, 2013 at 9:13 am

    #1660164

    Bhuvnesh, It has inserts and update statements in it.

    Thanks

    Shashi

  • October 22, 2013 at 3:27 am

    #1660422

    shashi_1409 (10/21/2013)

    Bhuvnesh, It has inserts and update statements in it.

    Thanks

    Shashi

    so my guess is .. there might be some uni code sitting (international languages..)

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply