To locate the troublesome row use the errorfile specifier. myRubbishData.log will have the offending rows and a companion file myRubbishData.log.txt will give you row numbers and offsets into the file. Companion file example:
I was ultimately able to resolve the solution by setting the column type in the flat file connection to be of type “database date [DT_DBDATE]” Apparently the differences between these date formats are as follow: DT_DATE A date structure that consists of year, month, day, and hour. DT_DBDATE A date structure that consists of year, … Read more
Should do what you need. Test Case Returns
Should do what you need. Test Case Returns
My guess is that you’re trying to squeeze a number greater than 99999.99 into your decimal fields. Changing it to (8,3) isn’t going to do anything if it’s greater than 99999.999 – you need to increase the number of digits before the decimal. You can do this by increasing the precision (which is the total number of … Read more
There are two formats of case expression. You can do CASE with many WHEN as; Or a Simple CASE expression Or CASE within CASE as;
You can obtain this information and much, much more by querying the Information Schema views. This sample query: Can be made over all these DB objects: CHECK_CONSTRAINTS COLUMN_DOMAIN_USAGE COLUMN_PRIVILEGES COLUMNS CONSTRAINT_COLUMN_USAGE CONSTRAINT_TABLE_USAGE DOMAIN_CONSTRAINTS DOMAINS KEY_COLUMN_USAGE PARAMETERS REFERENTIAL_CONSTRAINTS ROUTINES ROUTINE_COLUMNS SCHEMATA TABLE_CONSTRAINTS TABLE_PRIVILEGES TABLES VIEW_COLUMN_USAGE VIEW_TABLE_USAGE VIEWS
I am seeing this in several situations and it is intermittent in our web based application connecting to SQL 2008 R2 serve back end. Users are coming across a point 2 point connection and seeing this on and off. Thought it was bandwidth issues until I started seeing it on terminal servers that are on … Read more
Whenever this happens to me, I press Ctrl+Shift+R which refreshes intellisense, close the query window (save if necessary), then start a new session which usually works quite well.
instead of below Code replace with Updated : (thanks to @Marc Durdin for pointing) Note that under high load, this will still sometimes fail, because a second connection can pass the IF NOT EXISTS test before the first connection executes the INSERT, i.e. a race condition. See stackoverflow.com/a/3791506/1836776 for a good answer on why even wrapping in a … Read more