Forum Replies Created

Viewing 15 posts - 1 through 15 (of 45 total)

  • RE: Linked servers from 2012 to 2005

    Eirikur Eiriksson (4/6/2015)


    pveilleux (4/6/2015)


    Eirikur Eiriksson (4/6/2015)

    Was it running before? Just thinking of what could have changed|.

    😎

    It was not running. The 2005 server is a production server and the 2012...

  • RE: Linked servers from 2012 to 2005

    Eirikur Eiriksson (4/6/2015)

    Was it running before? Just thinking of what could have changed|.

    😎

    It was not running. The 2005 server is a production server and the 2012 instances (sql101, sql102)...

  • RE: Linked servers from 2012 to 2005

    Eirikur Eiriksson (4/6/2015)


    pveilleux (4/6/2015)


    I also went ahead and disabled Named Pipes on sql102, tried the queries, enabled Named Pipes, tried queries again. Everything on sql102 is behaving just...

  • RE: Linked servers from 2012 to 2005

    I also went ahead and disabled Named Pipes on sql102, tried the queries, enabled Named Pipes, tried queries again. Everything on sql102 is behaving just fine. As...

  • RE: Linked servers from 2012 to 2005

    I did not disable Named Pipes on sql101 because it is not disabled on sql102. From sql102, I can get to SQL2005INST no problem. In fact, from sql101,...

  • RE: Linked servers from 2012 to 2005

    No, we're not using Named Pipes to connect. Not sure why that is coming back in the message.

    Just for giggles, with the same set up, I tried to run...

  • RE: foreign key and sys.dm_db_index_usage_stats

    No idea. My post is almost a year and a half old, and references something from my last job. I left about 2 months after I posted this....

  • RE: SQL Server Agent - who ran that job?

    opc.three (6/6/2012)


    You say they are sysadmins, well they could be doing something like this which does not require them to know the password of the service account and would still...

  • RE: SQL Server Agent - who ran that job?

    SQLKnowItAll (6/6/2012)


    pveilleux (6/6/2012)


    SQLKnowItAll (6/6/2012)


    If someone is a sysadmin, they are automatically in all fixed database roles. They have full access. You could add an SQL Agent role, or...

  • RE: SQL Server Agent - who ran that job?

    SQLKnowItAll (6/6/2012)


    If someone is a sysadmin, they are automatically in all fixed database roles. They have full access. You could add an SQL Agent role, or take it...

  • RE: SQL Server Agent - who ran that job?

    This is good stuff, info I couldn't find in any of the BOL.

    So, here's what I have:

    JobA is owned by sa. SQL Agent and SQL Server are both run...

  • RE: SQL Server Agent - who ran that job?

    opc.three (6/1/2012)


    pveilleux (5/31/2012)


    Hello, all,

    In digging around on one of our servers, I found what appears to be someone logging in as the SQL Server/Agent service account and running jobs. ...

  • RE: SQL Server Agent - who ran that job?

    SQLKnowItAll (5/31/2012)In that case, I would make sure to have a separate agent account from the database engine. That 15 minutes will give you time to switch that and keep...

  • RE: SQL Server Agent - who ran that job?

    SQLKnowItAll (5/31/2012)


    http://beyondrelational.com/modules/2/blogs/77/posts/11360/changing-sql-server-service-account-or-password-avoid-restarting-sql-server.aspx

    Good point. I have always done a reboot to be on the safe side. This client has many, many, many processes that move data among multiple servers,...

  • RE: SQL Server Agent - who ran that job?

    SQLKnowItAll (5/31/2012)


    Since it is a domain account, why not just change the password and see who comes complaining to you? Who all needs to know that password? Hopefully only you...

    It's...

Viewing 15 posts - 1 through 15 (of 45 total)