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
450 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
450 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,255 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
501 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
438 reads
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
I am excited to host T-SQL Tuesday for the first time. I want to...
Hi we're a bit behind on versioning ssrs. I think we have over 1600...
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Comments posted to this topic are about the item Measuring Productivity
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers