Viewing 15 posts - 1,021 through 1,035 (of 1,222 total)
For SQL 2005, goto control panel, Add/Remove Programs and select Change. You should see a link "To install a new component, click here". Click on the link and...
June 22, 2007 at 7:02 am
You can do this using products such as Lumigent's Log Explorer if you stil have the transaction logs for when the sproc was changed. There are other similar products...
June 13, 2007 at 6:50 am
It is up to you (in your master sproc) to do the error handling and decide whether you should abort or not. You can control what happens so I...
June 12, 2007 at 10:57 pm
Why not just change the "On failure action" for the step to be "Goto the next step" instead of "quit the job reporting failure" (this is on the Advanced tab...
June 12, 2007 at 10:07 pm
Have a look at
sp_helparticle @publication = 'publication'
where 'publication' is the name of your publication.
Alternatively, you can use table sysarticles to see all table that...
June 5, 2007 at 10:50 pm
Have a look at
sp_helparticle @publication = 'publication'
where 'publication' is the name of your publication.
Alternatively, you can use table sysarticles to see all table that...
June 5, 2007 at 10:50 pm
In SQL Server Agent create a new job. In that job create 2 steps - one for each of the packages. The job steps will both be type...
June 3, 2007 at 10:55 pm
DTS packages are scheduled using SQL Server Agent.
The tables you need to look at are sysjobs and sysjobschedules (both in MSDB).
You may find sp_help_job and sp_help_jobschedule useful as...
May 22, 2007 at 10:34 pm
I don't think so but you could use the Server Network Utility to disable all protocols. This should mean the only option for connections is Shared Memory which only...
May 21, 2007 at 5:37 pm
There is no need to worry about using differeny directories. By default, the common files for SQL 2000 are in "C:\Program Files\Microsoft SQL Server\80" and the common files for...
May 20, 2007 at 10:49 pm
It would be more accurate to include the name of the schema (column TABLE_SCHEMA) in the query. There is potential with the solution for tables in different schemas to...
May 20, 2007 at 10:28 pm
You cannot deny a sysadmin access to any database object - they are allowed to see and doing anything they see fit. Hence, even if you use the DENY...
May 20, 2007 at 5:04 pm
There is no need to deny access - if you are not a sysadmin you can only see your own jobs anyway.
May 16, 2007 at 10:27 pm
Are the passwords for x\a and y\a the same ? If they are, you will be able to connect because of a feature of windows called passwthrough authentication (i.e....
April 12, 2007 at 9:50 pm
This is easily done using SQL Server Agent Tokens (have a look at sp_add_jobstep in Books Online).
In your job step, you can get the job name using the token [JOBID]
e.g.
Declare...
April 11, 2007 at 11:15 pm
Viewing 15 posts - 1,021 through 1,035 (of 1,222 total)