Post reply

Bug in SQL MultiScript of RedGate

  • November 28, 2011 at 5:26 am

    #248562

    Hi guys!

    Why MultiScipt of SQL Missed DBs while running scritps?

    Moreoevr ; When i copy/Paste text of SP in Multiscript Console and Parse , It throws syntex error. While I do the same on SQL Server's own Console , It work fine.

    WHY?

    It means SQL Multiscript is not reliable to work with?

    Pls share :((

    Thanks

  • November 28, 2011 at 5:33 am

    #1413368

    is the specific syntax error possible version related? something that would be fine in, say Version 90 or above(2005+) but not in SQL 2000? could it be somethign as simple as the compatibility version?

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • November 28, 2011 at 5:41 am

    #1413373

    MultiScript Version is 1.1.0.34

    I have integrated SQL 2008 at BE.

    Means>> When i Copy Paste text from My SP file to MScript of RG , It through error when executing.

    Moreover , We are still Unable to Understand why MScript missed DBs while executing Scripts?

  • November 28, 2011 at 7:03 am

    #1413407

    You'll probably want to show us the specific proc you get the error with.

    you also want to show the specific error you get.

    anyway, since it is an error in a proc definition, here's my guess.

    you have a command in a parameter like this:

    DECLARE @MyVal int = 42

    that command is valid in a SQL2008+database. in SLQ 2005, you will get an error.

    Msg 139, Level 15, State 1, Line 0

    Cannot assign a default value to a local variable.

    I doubt it's a bug in multiscript, but more likely a syntax/parsing issue based on what database compatibility is being applied.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • November 28, 2011 at 7:16 am

    #1413420

    I'd need to see the TSQL script and any error messages.

    The most likely reason for Multi-Script to skip a server is because it can't connect to that server.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • November 28, 2011 at 7:36 am

    #1413443

    The most likely reason for Multi-Script to skip a server is because it can't connect to that server

    not server... A DB on Same server.

  • November 28, 2011 at 7:43 am

    #1413448

    waseem.shahzad 45937 (11/28/2011)

    The most likely reason for Multi-Script to skip a server is because it can't connect to that server

    not server... A DB on Same server.

    yep...seems to go back to compatibility level of specific databases (or security, assuming the user is non sysadmin so it doesnt have access)

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • November 28, 2011 at 8:01 am

    #1413457

    waseem.shahzad 45937 (11/28/2011)

    The most likely reason for Multi-Script to skip a server is because it can't connect to that server

    not server... A DB on Same server.

    Sorry, misunderstood. It could still be security. But, it could be the script. Expand the output. You should see information for why it missed certain databases. They're definitely listed in the distribution on the right?

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

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

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