April 27, 2007 at 10:55 am
HI. I have been asked if it is recommended or even possible to run MSDE and SQL Server on the same server.
Thank you,
Juanita
April 29, 2007 at 5:52 am
actualy the engines are the same (msde has got some restrictions).
Concider it like running two instances of sqlserver. (cpu/memory/...)
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 29, 2007 at 11:37 pm
It's certainly possible. They will of course compete for resources (cpu, memory, and disk) when both are under load.
I wouldn't recommend it for a production server.
---------------------------------------
elsasoft.org
April 30, 2007 at 3:03 am
As previous people have said, it is possible to run a mixture of MSDE and full SQL instances on the same machine.
Because of likely memory and CPU pressure, you should not run more instances than you really need. The main reasons why searate instances may be needed are: a) Different system collation requirements, b) Different authentication requirements where site standards require separate instances for this, c) Cluster requirements.
If you have 2 applications both wanting the same system requirements, you should normally run these in the same instance, as they will both perform faster in the same instance than in separate instances.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 30, 2007 at 3:49 am
maybe this should be added :
If "legacy" is the only reason for the msde to live, migrate the databases to your sqlservers instance.
If the servicelevels of both instances match, and you find the databases can live together, you may want to ask the dev-teams or user-responsible if they aggree the migration of users and databases. Applications will have to connect to the sqlserver-instance.
- Databases can be migrated using sp_detach_db/sp_attach_db
If you're still on sql7, this can only be done if the instances have the same collation settings !
- You can copy the logins using :
select 'exec sp_addlogin ['
+ name
+ '],'
, password
, ', @encryptopt=skip_encryption'
from master..sysxlogins
- jobs can be scripted and implemented on the sqlserver-instance
- dts packages ... if there aren't to many, maybe migrate them manualy.
- also check alerts, mail-profiles, ...
prepare your action and walk through your checklist.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 30, 2007 at 3:35 pm
Thank you everyone!
Juanita
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy