Viewing 15 posts - 1 through 15 (of 117 total)
Yes, I agree SQL 2008 R2 is the stupidest version name ever. Has been nothing but problems with database servers running SQL 2008 (not r2). Vendors installing their products get...
May 31, 2017 at 11:55 am
Thank You, that was the problem the PUBLIC permission was missing. I Granted execute permission on the Extended Stored Procedure in the Master database to the application id and it...
April 4, 2017 at 8:16 am
I liked your tracking on how old the password. I was never sure if PWDCOMPARE takes into account the case of letters. In current releases of SQL Server the password...
April 4, 2017 at 7:34 am
No denies
Just db_datareader, db_datawriter, and execute permission on the user database.
March 31, 2017 at 1:06 pm
It was not harden, unless that is the new default for SQL 2012
USER_DEFINED_AUDIT_GROUP was enabled on the server audit and then I went back and added to the...
March 31, 2017 at 12:52 pm
Hi I release SQL Overview VII - SSRS Reports and Subscriptions in November 2014. It also contains a change History. The history section article was not published I...
October 24, 2016 at 12:22 pm
Having been part of several data center moves, using location in the server name never seemed practical but they continue to do it. Naming servers after characters while fun can...
May 21, 2015 at 6:55 am
Sorry for the missing article attachment. I added it to this reply
January 12, 2015 at 9:18 pm
Something went wrong with my install because the DTEXEC is located on different drives on each node.
June 10, 2014 at 1:46 pm
To fix the value of @@SERVERNAME for renamed server use
sp_dropserver <old_name>
GO
sp_addserver <new_name>, local
GO
I have used these comamnds to fix @@SERVERNAME. It requires a restart of the instance.
Source http://msdn.microsoft.com/en-us/library/ms143799.aspx
September 29, 2011 at 7:44 am
I have upgraded the package to SQL 2008 and plan to publish it someday. We are skipping the SQL Server 2008 R2 in our shop because of Microsoft's requirement for...
September 29, 2011 at 7:39 am
The SQL Overview package has been updated in SQL Overview V - Monitoring Long Running Jobs[/url]. You will find a full download of the package in this article.
I am sorry...
September 13, 2011 at 6:40 am
Make sure the SQL Overview database is on the localhost using the default instance. Create the temp tables on the local host before opening the package.
Make sure the variale Srvconn...
July 26, 2011 at 11:25 am
Try the last link to file listed under Resources: with a colon.
July 11, 2011 at 9:30 am
Viewing 15 posts - 1 through 15 (of 117 total)