Viewing 8 posts - 1 through 8 (of 8 total)
I'm confused. It appears you now advocate not upgrading if the SQL version is less than eight years old -- SQL2008R2? Forgive me, but I didn't read that...
June 21, 2016 at 1:24 am
The latest series of posts you enjoy so much from Microsoft says:
I can’t emphasize this patch enough. There is a MSVC, runtime library patch needed by SQL Server...
June 17, 2016 at 12:24 pm
There are additional considerations for .net developers. See
http://stackoverflow.com/questions/1334143/sql-server-datetime2-vs-datetime
Specifically, .net assumes datetime when adding a sqlParameter, and known legacy issues due to odbc style drivers and anything prior to .net...
January 5, 2016 at 10:27 am
100% physical, on SQL 2005. This is a manufacturing plant, where the devices that integrate w/ the database are legacy and are not going to upgrade.
May 8, 2015 at 11:39 am
Thanks Steve. I agree, stack ranking is idiotic for high-performing teams and only serves to drive away talent.
December 4, 2013 at 5:41 pm
The article failed in that it set up the conflict, but didn't resolve: so, Steve, how did you rank your employees? Did you unfairly assign a 2?
December 4, 2013 at 11:39 am
I just had this exact problem, where the SQL Agent account was a domain account. Problem turned out to be somehow permissions got yanked for that account. The...
January 13, 2012 at 9:38 am
I've done this myself, but within a vb.net program that also generates vb code to treat it as a model. I believe later versions of Visual Studio provide this...
February 10, 2011 at 9:21 am
Viewing 8 posts - 1 through 8 (of 8 total)
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy