You can also:

1. Create a user defined role (for example "MyRoleJobExec")in msdb

2. Add the users which you want to have permissions to execute the job to that...

The owner of the package really doesn't matter. In this case the DTS package will run under the security context of the owner of the job (provided you are...

I've found TCPView from sysinternals (freeware) to be a very useful tool in troubleshooting TCP port conflicts. It lists the process and port number being used by each running...

One other note about the ComCheck utility, it includes a ini file ComCheck.ini which lists the build name and build number mappings. This comes in handy when you don't...

For a description on how to obtain a list of MAC to IP addresses see the following Windows 2000 FAQ:

http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14462

This posting brings back some not-so-fond memories of Y2K testing!!! At the time I was working with COBOL on MVS and AS/400 platforms which of course we couldn't...

Since your just changing table owners, SQLDMO will work also. The nice thing about using SQLDMO, is that you can create it as a SQL Agent job (ActiveX/VBScript), which...

I've had a smiliar experience after configuring a linked server to use Windows authentication (see "Security Account Delegation" in BOL). If I log into the local SQL Server and...

Create a role in msdb and add the users or groups to that role which need to execute the job. Then add 2 lines to sysjobs_view:

OR ((ISNULL(IS_MEMBER(N'MyJobExecRole'), 0) =...

I've used Log Explorer from Lumigent (www.lumigent.com) for several years the price is reasonable and it accomplishes just this type of thing very easily by reading the SQL Server...

I've used PKZip 6.0 for Windows to zip a 15 GB file. According to their documentation there is no limit to size since version 4.5.

Try running unlodctr and lodctr, then restarting SQL or rebooting server.

unlodctr.exe MSSQLServer <$instance name>

lodctr.exe <sql>\BINN\sqlctr.ini

It took me several months and many calls to Microsoft's PSS to finally resolve our SQL Server SSPI errors. Although I still see some occasional but rare SSPI...

The debugger behavior has changed in SP3, so that owners of objects can only debug objects they own. This is true even with SP3 on server and workstation. ...

My favorite 3rd party tools, they are not cheap, but well worth $$:

Data modeling -- Erwin

Data Recovery -- Lumigent Log Explorer

Performance Monitoring -- Netiq AppManager and Precise Indepth for SQL...