Viewing 15 posts - 61 through 75 (of 387 total)
Using an ssis package with a forloop container and a lookup table of the instances you are interested in is how we get info from all the instances we look...
November 19, 2009 at 1:50 pm
You could also use xp_logininfo
Andrew
November 18, 2009 at 3:07 pm
If it's 2005+ you can use GRANT VIEW DEFINITION
Andrew
November 16, 2009 at 2:48 pm
We had an issue like this, turned out to be excessive transaction log VLFs due to log auto growth, we followed the directions in the below doc and our restore...
November 13, 2009 at 3:11 pm
Is the hotfix the 64 bit version meant for your chip set, definitley not X86?
Andrew
November 12, 2009 at 1:12 pm
SERVERPROPERTY will work fine for a MS cluster, but for VERITAS cluster setups it returns the lanman name, we use the below script to get the physical node name, we...
November 11, 2009 at 12:33 pm
One way we have worked around this is have the job that runs the SSIS package check if a flag in a table is set, if so the run ssis...
November 9, 2009 at 3:26 pm
You can use these two snippets, I got them from a bog I believe:
--SQL 2005
UPDATE msdb.dbo.sysdtspackages90
SET ownersid = 0x01
where packagetype = 6
--SQL 2008
UPDATE msdb.dbo.sysssispackages
SET [ownersid] = SUSER_SID('sa')
where packagetype =...
November 3, 2009 at 2:35 pm
Idera has a nice free product that does this its called Idera SQLpermissions, use it when going from one dev enviroment to another, could script but this does it with...
October 28, 2009 at 4:21 pm
Here is an article that I believe explains your issue and details a way to kill the negative spids
http://www.sqlserverclub.com/articles/how-to-deal-with-negative-spids-in-sql-server.aspx
andrew
October 15, 2009 at 2:43 pm
We run this code in SSIS packages against our ditributers and send alerts if we have any issues:
SELECT
MSdistribution_agents.name, MSdistribution_agents.publisher_db,
MSdistribution_agents.publication,
MSdistribution_agents.subscriber_db,
case when runstatus ...
October 13, 2009 at 1:51 pm
You may want to look at setting a proc to fire whenever SQL is restarted
exec sp_procoption
@ProcName = 'YourProcName',
@OptionName = 'startup',
@OptionValue = 'on'
Andrew
October 12, 2009 at 3:54 pm
I would ask the network team if they have blocked access to xp_cmdshell remotley, they did it at company I worked for, because they where told it was best practice,...
October 9, 2009 at 2:34 pm
Run profiler when you add the atricles through the gui and see what code SQL is creating, then use that for the automation.
Andrew
October 9, 2009 at 1:19 pm
When installing you have the option of installing the client tools and SSIS, it looks like this wasn't installed, if not you need to install, these are not clustered, so...
October 2, 2009 at 1:38 pm
Viewing 15 posts - 61 through 75 (of 387 total)