Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 Agent Jobs / Named Instance

Author  Topic 

WJHamel
Aged Yak Warrior

651 Posts

Posted - 2015-02-13 : 12:06:35
in reference to both MSSQL 2k8R2 and 2012, if i have a named instance AND a default instance on the same installation, and i create agent jobs (backups, indexing, etc) on either one, those same jobs appear on the "other" instance without having actually created them while logged IN to that instance.

Is this a normal feature of MSSQL? Doesn't seem like it should be happening that way.

gbritton
Master Smack Fu Yak Hacker

2780 Posts

Posted - 2015-02-13 : 12:30:53
Sounds impossible to me. The agent jobs are stored in msdb.dbo.sysjobs and msdb.dbo.sysjobsteps IIRC. msdb is unique by instance, not server
Go to Top of Page

WJHamel
Aged Yak Warrior

651 Posts

Posted - 2015-02-13 : 13:28:58
Just verified it. Took an existing job on the default instance, modified it. Disconnected from the default instance and opened the named instance, opened that job and the modification was there too. Also, created a NEW job on the named instance, disconnected from the named instance, opened the default, and that new job was now in the default instance.
Go to Top of Page

gbritton
Master Smack Fu Yak Hacker

2780 Posts

Posted - 2015-02-13 : 13:39:00
This cannot be unless the two instances are somehow using the same filepaths for msdb (corruption follows!) or the named instance is also the default instance.
Go to Top of Page

WJHamel
Aged Yak Warrior

651 Posts

Posted - 2015-02-13 : 13:48:47
I found a server that is using a default AND a named instance where this symptom does NOT appear. The difference is, that particular server is using different file names in the database settings for the data and log file. The server where this symptom IS happening is using the same data and log files.

The only thing which might be keeping this from being catastrophic is the fact that, on the server where the same data and log file are being used for both instances, the application is NOT touching the default instance at all. Therefore, all the transactions are hitting only the named instance.

All i know is, I am NOT the one who configured that server.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2015-02-13 : 13:57:10
I don't think you have two instances on that server. I think you have just a named instance that has been setup to also allow you to connect without using the instance name, which can be done via an alias or by using port 1433.

Check the services applet.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

WJHamel
Aged Yak Warrior

651 Posts

Posted - 2015-02-14 : 15:00:46
The connection string for the application which touches that server is specifying the named instance.

Just sayin.


quote:
Originally posted by tkizer

I don't think you have two instances on that server. I think you have just a named instance that has been setup to also allow you to connect without using the instance name, which can be done via an alias or by using port 1433.

Check the services applet.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/

Go to Top of Page

gbritton
Master Smack Fu Yak Hacker

2780 Posts

Posted - 2015-02-15 : 14:23:49
Fine, but that could also be the default instance (which also has a name).

Could you post the connection string?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2015-02-16 : 12:27:38
quote:
Originally posted by WJHamel

The connection string for the application which touches that server is specifying the named instance.

Just sayin.


quote:
Originally posted by tkizer

I don't think you have two instances on that server. I think you have just a named instance that has been setup to also allow you to connect without using the instance name, which can be done via an alias or by using port 1433.

Check the services applet.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/





So did you check the services applet? What I'm saying is that you CAN connect to a named instance if you only specify the host name. There are two ways to do this that I know of, maybe more: alias or port 1433 for named instance.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page
   

- Advertisement -