"A special resource task in the Windows service uses the MinFreeConnections and MaxFreeConnections registry settings to preallocate connection objects. Windows Server 2003 automatically calculates these values. The algorithm that is used by Windows Server 2003 to determine these values now considers the amount of physical RAM in Windows Server 2003. The algorithm also considers the Server service optimization settings. "
References: http://support.microsoft.com/kb/909262
Tuesday, January 18, 2011
Thursday, January 13, 2011
WBCOOP is coming!
I have registered to play in the PokerStars World Blogger Championship of Online Poker! The WBCOOP is a free online Poker tournament open to all Bloggers, so register on WBCOOP to play.
Registration code: XXXXXX 781754
Wednesday, January 12, 2011
SQL 2008 Jobs, Proxy, and Credentials
This is some what confusing...
SQL 2008 seems to be allow you to specify a proxy account to each STEP of a SQL Agent job as well as different proxies for different KINDS of job tasks, ie. SSIS, EXE, ActiveX, etc...
For example, the "owner" of a job has a step that runs a SSIS package. In order to do this, you will need to use or setup a SQL local account or domain account that has permissions to execute SSIS, then create a CREDENTIAL associated with that account on SQL server.
Next, you create a SSIS Proxy account and assign the credential to it. You also associate the "owner" to that Proxy.
Finally, in Properties of the job STEP, you assign the Proxy as the "Run as:" for the step that involves SSIS, in this example.
References:
http://support.microsoft.com/kb/918760
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/10/13/who-owns-my-job-and-who-runs-it.aspx
SQL 2008 seems to be allow you to specify a proxy account to each STEP of a SQL Agent job as well as different proxies for different KINDS of job tasks, ie. SSIS, EXE, ActiveX, etc...
For example, the "owner" of a job has a step that runs a SSIS package. In order to do this, you will need to use or setup a SQL local account or domain account that has permissions to execute SSIS, then create a CREDENTIAL associated with that account on SQL server.
Next, you create a SSIS Proxy account and assign the credential to it. You also associate the "owner" to that Proxy.
Finally, in Properties of the job STEP, you assign the Proxy as the "Run as:" for the step that involves SSIS, in this example.
References:
http://support.microsoft.com/kb/918760
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/10/13/who-owns-my-job-and-who-runs-it.aspx
Monday, January 10, 2011
Access denied to remote DCOM on Win 2003
If you're trying to remotely connect to SSIS on SQL server 2005/2008 and get "access is denied", check the Event Viewer (should be in the System log) on the server, and you should see DCOM errors showing the user trying to do "Remote Activation" and an ANONYMOUS LOGON trying to do a "Remote Access".
http://msdn.microsoft.com/en-us/library/aa337083.aspx
http://support.microsoft.com/?kbid=892500
- If you do, you'll need to go into Component Services and edit properties on the computer node.
- On the COM Security tab,
- Click the Edit Limits buttons to make the updates.
http://msdn.microsoft.com/en-us/library/aa337083.aspx
http://support.microsoft.com/?kbid=892500
Wednesday, January 5, 2011
NetApp Filer At-A-Glance
What do the colors mean?
The color-coded bar graph for 'Usage by Volume%' has three colors: green, yellow, and red.
- Green: 85% to 100% available disk space on volume
- Yellow: 10% to 15% available disk space on volume
- Red: less than 10% available disk space on volume
The color-coded bar graph for 'Network file Ops/sec' might show up:
- Blue: represents NFS ops
- Red: represents CIFS and/or HTTP ops
- Green: represents HTTP ops/sec
- Yellow: represents iSCSI ops/sec
- Magenta: represents FCP ops/sec
Reference: https://kb.netapp.com/support/index?page=content&id=3010503&pmv=print&impressions=false
Subscribe to:
Posts (Atom)