PROVIDING LOGGING INFORMATION AT COMMAND LINE
For providing logging information at command line utility use the option /l
for example
dtexe /f "some path" /l "logging type; connection...
2014-05-03
443 reads
For providing logging information at command line utility use the option /l
for example
dtexe /f "some path" /l "logging type; connection...
2014-05-03
443 reads
Writing this post only for internet explorer as not aware of the settings of other browsers such as chrome/mozilla.
To be...
2014-04-30
1,242 reads
2014-04-27
Recently I encountered a problem of handling dates while converting a vb6 code to .net code.
Problem - cant predict what the...
2013-05-24
495 reads
Hi Guys,
Anyone interested in online training for MSBI (SSAS, SSRS and SSIS), please contact @ er.lokeshsharma08@gmail.com.
Features - Best material (practical and theoretical) for becoming familiar with...
2013-05-24
434 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Hi everyone I asked this earlier but the desired outcome is a bit different...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Comments posted to this topic are about the item Multiple Deployment Processes
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers