August 11, 2008 at 7:04 am
Just curious if we can have just named instances, selecting one to be the default, or does one instance always have to be "unnamed" in the server environment? Not sure about best practices here, but I'd rather they all have a designation. (very NOOB I know).
Bob
Not a downstroke, fistpicker
August 11, 2008 at 7:27 am
rmaggio (8/11/2008)
Just curious if we can have just named instances, selecting one to be the default, or does one instance always have to be "unnamed" in the server environment? Not sure about best practices here, but I'd rather they all have a designation. (very NOOB I know).
You can have only named instances if you wish. However, you can have only one default instance.
Regards,
Andras
August 12, 2008 at 2:20 am
Entirely up to you...
As an example we have 8 named instances on our dev server and 4 named instances on our production servers... all working fine within a VMware ESX environment. Be sure to allocate enough memory to all instances.
Cheers,
Mark
August 14, 2008 at 11:46 am
I've been trying out SS 2005 Developers Edition and did not have a default instance. I did run into a problem when I was trying to check out running Management Studio against the Integration Services Server. Apparently it only runs against the default instance?
Steve
August 14, 2008 at 11:57 am
SSIS is based on the default instance. I ran into a major bug with that a little while back, since Workgroup Edition doesn't support SSIS, but Standard does, and the default instance was Workgroup. Couldn't schedule SSIS packages through Agent on the Standard instance till I uninstalled Workgroup and installed Standard as the default.
(Was really tough to debug because the packages worked just fine in BIDS on that same server, but wouldn't run through Agent, and the error messages were not very clear.)
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
August 14, 2008 at 1:44 pm
GSquared (8/14/2008)
SSIS is based on the default instance. I ran into a major bug with that a little while back, since Workgroup Edition doesn't support SSIS, but Standard does, and the default instance was Workgroup. Couldn't schedule SSIS packages through Agent on the Standard instance till I uninstalled Workgroup and installed Standard as the default.(Was really tough to debug because the packages worked just fine in BIDS on that same server, but wouldn't run through Agent, and the error messages were not very clear.)
Hey Gus, I vaguely remember this issue but cannot remember if you ever tried modifying the ini file for SSIS. The file is MsDtsSrvr.ini.xml in the DTS\Binn folder.
All I have had to do in the past is add in the instance name to this file to get access to SSIS from that instance.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 14, 2008 at 1:54 pm
Nope. Didn't know about that option. MS Tech Support apparently didn't either (they weren't very helpful, but did at least help me figure out what was wrong, even though they didn't have the faintest clue how to solve it).
Good to know if it ever comes up again.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
August 14, 2008 at 2:04 pm
Not sure if that would have fixed your problem with Workgroup edition - just something I remember having to do with multiple instances.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 14, 2008 at 2:06 pm
GSquared (8/14/2008)
Nope. Didn't know about that option. MS Tech Support apparently didn't either
LOL.
The same file needs to be changes when running SSIS on a cluster. SSIS isn't itself cluster-aware and so is installed on each node. To get it to point to the SQL Server virtual requires changing that file. I believe that by default the server name that's in the ini file is '.'
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 14, 2008 at 3:15 pm
Now that you mention that, Gail, I have read that before.
Haven't had to play with clustered servers yet, so didn't think of it. Not sure I would have connected that to the SSIS/Agent issues I was running into.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply