November 20, 2015 at 5:06 am
Do you have the latest posted version of the code?
November 24, 2015 at 4:10 am
No
November 24, 2015 at 7:24 am
Take the latest version from this site and try again. Let me know.
January 11, 2016 at 7:52 am
Your version of SQL Server is probably too old to recognize the MAX keyword. Are you using SQL 2000?
You could try doing a replace in the script, replacing MAX with 8000 to see if that works.
Jeff Bennett
St. Louis, MO
February 17, 2016 at 4:37 pm
Way more info than I though available.
February 17, 2016 at 5:31 pm
Iwas Bornready (2/17/2016)
Way more info than I though available.
Hope you found it useful. 🙂
April 27, 2016 at 6:48 am
Sean, I've seen a lot of posts from you that are from way back. You've provided some good stuff. Thanks.
April 27, 2016 at 6:58 am
Iwas Bornready (4/27/2016)
Sean, I've seen a lot of posts from you that are from way back. You've provided some good stuff. Thanks.
I try to share whatever I can with the community. I get good feedback from people too so it helps me improve my code as well. Win-win. 🙂
August 4, 2017 at 2:29 am
Hi all, Is there any update or more recent improvements to the code? Does this take changes in SQL 2016 into account?
Thanks to the OP (Sean) for the great work.
August 4, 2017 at 8:37 am
jumpin - Friday, August 4, 2017 2:29 AMHi all, Is there any update or more recent improvements to the code? Does this take changes in SQL 2016 into account?Thanks to the OP (Sean) for the great work.
I actually have a bunch of updates which need to be posted (just need to find the time because the article, screenshots, etc. all need to be updated as well). Were there any things in particular you were looking to be added for SQL Server 2016?
Viewing 10 posts - 181 through 189 (of 189 total)
You must be logged in to reply to this topic. Login to reply