Search
Subscribe
Categories
- Backup and Restore
- Capacity Planning
- Compression
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- DBCC
- Deadlocks
- Default Trace
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Execution Plan
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Isolation levels
- Jobs
- Latches
- Links
- Locking
- Memory
- Monitor Performance
- MS DTC
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Blocking
- SQL Cachestore
- SQL DAC
- SQL Default Trace
- SQL DTS
- SQL Error Logs
- SQL Execution Plan
- SQL Optimizer
- SQL problems
- SQL Query Tuning
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL Trigger
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- Stored Procedure
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- View
- Virtualization
- Wait Stats
SQLServer-DBA.com Links
Recent Posts
- Shredding XML with Powershell and SQL Server
- Task Manager not showing correct SQL Server memory usage
- The value of training and How to convince your boss
- SQL Error 1204 - cannot obtain a LOCK resource at this time
- Multi-statement table valued function and inefficient Excecution Plan
- SQL Server Export to Excel with Powershell
- Who dropped the table in SQL Server
- List sql database roles
- SQL Execution Plan - Comparing Estimated Rows and Actual Rows
- DCOM got error "Logon failure: unknown user name or bad password” Event 1004
29 September,2012 by Jack Vamvas
A developer asked me to develop a template for executing SQLCMD with the output to the screen and output file. Normally it’s one or the other , but there is a workaround that allows SQLCMD to screen output and redirect output to file
Redirecting SQLCMD output to file is done with the –o switch. When using the –o switch , the output that normally would go to the screen , is redirected to the output file. On this occasion the developer wanted to both redirect the output to screen and the log file.
The purpose was to build in some interactivity with PAUSE , and make decisions on whether to continue based on the screen output.
The workaround to use the –o switch AND view the output on the screen is to use the the DOS TYPE command. The TYPE command displays the contents of a text file.
SQLCMD -E -S MyServer\MyInstance -i "mysqlscript.sql" -o output.log :: The next step outputs output.log to the screen echo The query output was: TYPE output.log
Related Posts
Powershell : SQLCMD and invoke-expression
SQL Server – Open SSMS without the splash screen graphic
Author: Jack Vamvas (http://www.sqlserver-dba.com)
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |