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
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
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
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
Quite the title, so let me set the stage first. You have an Azure...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers