I know this is an old question. The way I solved it – after failing by increasing the length or even changing to data type text – was creating an XLSX file and importing. It accurately detected the data type instead of setting all columns as varchar(50). Turns out nvarchar(255) for that column would have … Read more
There are issues with leap year/days and the following method, see the update below: try this: OUTPUT: UPDATE here are some more accurate methods: BEST METHOD FOR YEARS IN INT you can change the above 10000 to 10000.0 and get decimals, but it will not be as accurate as the method below. BEST METHOD FOR … Read more
I got it. It worked fine Thank you for your help:
should work
Add a WHERE clause
You are dropping it, then creating it, then trying to create it again by using SELECT INTO. Change to: In MS SQL Server you can create a table without a CREATE TABLE statement by using SELECT INTO
OK. I finally created a view that works: Thanks to AdaTheDev and CodeByMoonlight. I used your two answers to get to this. (Thanks to the other repliers too of course) Now when I do joins with other bigint cols or do something like ‘SELECT * FROM MyView where mycol=1’ it returns the correct result with … Read more
You seem to want to use a CURSOR. Though most of the times it’s best to use a set based solution, there are some times where a CURSOR is the best solution. Without knowing more about your real problem, we can’t help you more than that:
Dynamic SQL PIVOT: Results: