March 11, 2010 at 2:38 pm
In SQL 2008 SSMS query window frequently I save my query results to file. In SQL 2000 QA I would get the message: The following file has been saved successfully: xxxxx.rpt.
But, I dont get that message in SQL 08 even though the file did successfully save? Does anyone know why? I've gone throught the Query Options but I do not see anytthing that pertains to this issue.
thanks
Dale
March 15, 2010 at 5:23 pm
I coming to the conclusion that SQL '05 and '08 does not provide this message anymore. Please correct me if I'm wrong. :
The following file has been saved successfully:
March 15, 2010 at 8:29 pm
When I select "Results to File" in 2008, I receive the following message, just as if I had selected "Results to Text" or "Results to Grid". I couldn't find any options regarding the error message you are looking for either.
(1 row(s) affected)
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
March 15, 2010 at 8:53 pm
I am required to run at least 30 scripts a day on our production environment on behalf of our dozen or so developers. I save the query results back to their respective folders on a shared drive so that they can verify the results. As I'm getting old and frail of mind its just nice to see a confirmation that I saved the results file into the correct directory. (1 row(s) affected) does not give me this.
In the scheme of things its not a biggie... its just that I am surprised this is a feature that has been lost in SQL 08 (and probably 05). I have looked through all the relevant options (I think) but it aint there.:crying:
March 15, 2010 at 9:24 pm
I see your difficulty. Maybe a simple SSIS package?
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
March 16, 2010 at 8:42 am
Use SQLCMD mode straight from SSMS...easy!
See http://msdn.microsoft.com/en-us/library/ms174187.aspx for details, and an example 🙂
Example preview:
:out C:\testoutput.txt
SELECT @@VERSION As 'Server Version'
!!DIR
!!:GO
SELECT @@SERVERNAME AS 'Server Name'
GO
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
March 16, 2010 at 10:14 pm
Use SQLCMD mode straight from SSMS...easy!
Thanks for the suggestion but for a myriad of reasons its just not practical to use SQLCMD for running these type of scripts on our production environment. I'll soon get use to not receiving the confirmation message... its 'progress'.
March 16, 2010 at 10:22 pm
krakatoa66 (3/16/2010)
Thanks for the suggestion but for a myriad of reasons its just not practical to use SQLCMD for running these type of scripts on our production environment.
You know I am referring to SQLCMD mode inside SSMS, right? Not the command-line tool of the same name.
In 2005 SSMS there is a toolbar icon to turn it on. In 2005 and 2008 it is an option, like Results To File.
Tools/Options/Query Execution - the tick box 'by default, open new queries in SQLCMD mode'.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
March 16, 2010 at 10:58 pm
You know I am referring to SQLCMD mode inside SSMS, right?
Initially i thought you were referring to the command line tool because using SQLCMD mode within SSMS still doesnt provide the ' such and such file saved message' in the Messages tab... unless I am missing some option?
March 16, 2010 at 11:15 pm
krakatoa66 (3/16/2010)
You know I am referring to SQLCMD mode inside SSMS, right?
Initially i thought you were referring to the command line tool because using SQLCMD mode within SSMS still doesnt provide the ' such and such file saved message' in the Messages tab... unless I am missing some option?
No, the output is directed to the output file.
Any error messages (path not found etc.) will go to the Messages pane by default.
All this is configurable using :out and :error
See http://msdn.microsoft.com/en-us/library/ms162773.aspx for the command reference. You have to scroll down a fair way to get to the in-SSMS command reference.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply