Viewing 15 posts - 1,291 through 1,305 (of 1,518 total)
Jeff Moden (3/31/2008)Proxy account to run reviewed stored procedures is going to be a lot easier on the DBA than trying to review some other source code written in a...
April 1, 2008 at 4:04 am
I would suggest that you:
- Read the sp2-install readme file carefully. Incomplete though it may be, it is still a must.
- Install in the default installation location
- Prior to the...
March 31, 2008 at 3:25 pm
I've run into all sorts of issues when deviating from the default installation location of SQL Server and now splitting the data and log files of a system db into...
March 31, 2008 at 2:58 pm
No problem! 🙂
MS really should add this info to their README file for the SP2 install. Having data and log files in the same location is against their best...
March 31, 2008 at 2:25 pm
I think we have found the problem. The data and log files of the resource db are not in the same location:
You cannot install SQL Server 2005 Service Pack 2...
March 31, 2008 at 2:16 pm
Buxton69 (3/31/2008)
March 31, 2008 at 10:20 am
It's tough.
I have been trying to enforce this new initiative of leaving xp_cmdshell turned off on all our SQL Server 2005 instances and using SQL CLR instead. But there is...
March 31, 2008 at 8:44 am
All great ideas Todd. I need to read up more on these issues, esp. how to code access security into my SQL CLR code. Lots to learn and you've opened...
March 30, 2008 at 8:19 am
Thanks all for your input.
Yes, it's true that by trying to replace xp_cmdshell with SQL CLR code that is just as generic opens the door to even more security-related issues.
I...
March 30, 2008 at 7:58 am
From http://support.microsoft.com/kb/263889:
If an owner-qualified procedure is executed with a different case than what the owner-qualified procedure was created as, the owner-qualified procedure can get a CacheMiss or request a COMPILE...
March 28, 2008 at 8:29 pm
I should add that DBAs - myself included 🙂 - probably tend to overuse cursors in our every day work.
As Jason mentioned, as long as it does not impact server...
March 28, 2008 at 1:47 pm
cjudge (3/28/2008)
So, for the edification...
March 28, 2008 at 1:44 pm
Also, is your parameter an int or string type. If the latter, you will have to take quotes into account, like this:
="SELECT * FROM Employees; EXEC dbo.insert_into_table_Sprocs @parameter='" & Parameters!XXX.Value...
March 28, 2008 at 1:16 pm
lalonacademy (3/28/2008)
March 28, 2008 at 1:12 pm
We followed the recommendations on that link and tried re-applying the SP, but no luck.
March 28, 2008 at 10:22 am
Viewing 15 posts - 1,291 through 1,305 (of 1,518 total)