Viewing 15 posts - 16 through 30 (of 326 total)
Thanks as it worked like a charm
September 21, 2016 at 11:17 am
PHXHoward (2/24/2016)
February 24, 2016 at 11:01 am
Hello,
Cool script! I would just make one change and add the following
PRINT @dbname
EXEC ('EXEC [' + @dbname + '].dbo.sp_change_users_login @Action=Report')
This would show the database name where the orphan...
February 23, 2016 at 7:23 am
You sure can. As in most things, there are many ways to get a job done.
February 19, 2016 at 8:08 am
Ness (2/19/2016)
You could always take a look at MS Baseline Security Analyser. Not fantastic, but useful.
Yes good point. However, by the time you install it, this script would have been...
February 19, 2016 at 7:39 am
patrickpartin (2/5/2016)
If so, line 220...
February 8, 2016 at 6:37 am
terry.home (2/3/2016)
Not sure about turning database mail functionality off, appreciate that if anybody hacks system they can send email to...
February 3, 2016 at 1:44 pm
SQL Guy 1 (2/2/2016)
If not bugs, would put...
February 3, 2016 at 7:27 am
dainolib (2/2/2016)
1. This option is not related to restriction on local administrator but on local connections
2. The recommended value is 0 (only local connections...
February 3, 2016 at 7:25 am
Jefferson Elias (2/2/2016)
This seems interesting but it doesn't work against a 2008 R2 instance.
Reason:
Msg 207, Level 16, State 1, Line 245
Invalid column name 'physical_memory_kb'.
You could use an...
February 3, 2016 at 7:18 am
shadighaith (2/3/2016)
February 3, 2016 at 7:07 am
Hello Mike,
Sorry that the script didn't work in SQL Express. We don't use that edition of SQL so I haven't tested it. Assuming that you could make changes to the...
January 26, 2016 at 6:49 am
quackhandle1975 (11/26/2015)
November 26, 2015 at 11:01 am
Thanks for the comments 🙂
Glad to see that this article is creating conversation as there isn't a lot on this topic in the wild. My goal here was to provide...
October 16, 2015 at 11:21 am
Kris Gruttemeyer (10/16/2015)
One thing which is not mentioned: You can only restore 2008+ in SQL 2014, if you have a SQL2005 (or SQL2000 :w00t: database), you'll have to restore it...
October 16, 2015 at 11:16 am
Viewing 15 posts - 16 through 30 (of 326 total)