Viewing 15 posts - 1,321 through 1,335 (of 2,636 total)
I can't take credit for figuring it out, but I pass it on every chance I get!
Greg
November 7, 2007 at 3:40 pm
To decrypt a DTSRUN command as used in a job step, copy the command to a cmd prompt, append /!X /!C to the end, and run it.
The !X argument blocks...
November 6, 2007 at 4:53 pm
Hi Artem,
Do you require that it be done in a script? You can do it in SQL Server Management Studio by expanding the database, Security, Users and opening the...
November 6, 2007 at 3:51 pm
Open the package file in DTS Designer, click Package -> Save As and save to the SQL Server instance where you want the package.
Greg
November 6, 2007 at 9:20 am
I suggest you download and run SQL Server Upgrade Advisor http://www.microsoft.com/downloads/details.aspx?FamilyID=1470e86b-7e05-4322-a677-95ab44f12d75&DisplayLang=en. It will list for you all the things in existing stored procedures that either won't work or work...
November 2, 2007 at 9:00 am
Mike,
You'll have to grant the vendor some permissions in msdb. I'd create a role, add the user to it, and grant the following permissions to the role:
sp_add_job ...
October 30, 2007 at 9:43 am
http://WWW.SQLDTS.COM does have an example that I've used in a couple of packages:
http://www.sqldts.com/218.aspx
Greg
October 29, 2007 at 8:59 am
If it didn't happen too long ago, you can see a history of schema changes in a database by using the "Schema Changes History" report on the Summary tab in...
October 24, 2007 at 11:01 am
Hi,
Usually the recommendation to remove BUILTIN\Administrators is made because the group contains everyone with administrative rights on the server, including those who may not be SQL Server administrators. You...
October 22, 2007 at 12:59 pm
The generally recommended practice is to put all the data access code (select, update, insert, delete) in stored procedures in the SQL Server database and grant the database user EXECUTE...
October 22, 2007 at 12:37 pm
Jay,
DTS is replaced in SQL 2005 by SQL Server Integration Services (SSIS) which is not so tightly coupled with SQL Server Management Studio as DTS is with Enterprise Manager. ...
October 19, 2007 at 9:21 am
SQL 2005 maintenance plans are created as SSIS packages. You won't find them in any system tables.
Greg
October 18, 2007 at 12:13 pm
Also consider making a backup of the SQL 2000 database and restoring it in the SQL 2005 instance.
Greg
October 18, 2007 at 10:39 am
Osama's suggestion sounds pretty good, although it would be a DTS package rather than SSIS since this is SQL 2000.
You can also set retries on a job step....
October 18, 2007 at 10:25 am
Garrick,
1) If a connection in the package uses a SQL Server login, it won't affect the job execution at all. Of course, a SQL Server login won't be able...
October 18, 2007 at 10:04 am
Viewing 15 posts - 1,321 through 1,335 (of 2,636 total)