is it possible to add 2012 standard server to sbs2003 domain

Hi,

EULA rules states SBS servers should be the only ones in a network. In other words Microsoft does not approve 2 domain controllers in one SBS driven network.
It is possible though but not recommendable.

There is no problem adding the 2012 box as a memberserver (as long as your domain functional level is 2003)

yes i will only have 1 sbs srver as the new server is 2012 standard
currently all the fsmo roles would be on the 2003 sbs server
so is it ok to add the new server as a domain controller
could i demote the sbs server to a member server and continue to use sql and exchange on it

Yes you are fine if you just install the new 2012 server as a domain controller.

But it is not alright to demote the SBS 2003 this is against the license agreement, SBS needs to be a domain controller if you demote it you will probably destroy other features of SBS. Only time you demote a SBS server is the moment you are removing it from your domain completly.

you can promote a 2012 server in a 2003 SBS domain
the requirements are that the 2003 SBS hold the FSMO roles and be at the root of the domain

http://blogs.technet.com/b/sbs/archive/2007/10/04/debunking-the-myth-about-additional-domain-controllers-replica-dcs-in-an-sbs-domain.aspx

i don't recommend having this same 2012 domain controller running sql

http://support.microsoft.com/kb/2032911

i have created a seperate 2012 sql server its also virtual
so how would i go about removing the sbs server

and is it ok to have the 2012 server running as a dc for say 6 months to a year

yes...as long as you abide by the 2003 SBS rules, 2012 domain controller can co-exist

no its 2012 standard

understood...just wanted to throw that out there in case you decide to go with R2 either now (once it's available next month) or in the future while your 2003 server is still there

no problem so it is safe for me to promote the 2012 server to be a dc
as long as i dont touch fsmo roles
this will then give me active directory dns dhcp and dc redundancy??
then i can move the sql install implement exchange 365 move my data then move fsmo roles
and demote sbs server
is this correct?

Yes it is safe to promote 2012 to a dc if you leave the fsmo roles on the SBS.

this will give you DC and dns redundancy, dhcp is not redundant it is not in Active directory and dhcp high availability can only be created since server 2012 (you need two 2012 servers for that).

Than move indeed everything away from your SBS server and I would recommend uninstall exchange before you demote SBS this will cleanup you AD by removing all Exchange objects. It might give you problems in the future if you would like to go back to a local Exchange installation.

After demoting the SBS you have to manual remove some DNS records pointing to the old SBS and delete the computer object from active directory users and computers.

I don't know if anyone is still active in this thread, but if so I have a DNS issue in a SBS 2003 adding a 2012 DNS Server.

It says to manually delegate the new server, but I have never done this and am not sure. Our first attempt at this caused complete loss of access to the domain and had to bring in Microsoft Paid support to help cleanup everything after removing the new DC from the Domain.

I have followed the steps in this process, but DNS is giving access denied errors and I cannot connect to the existing DNS on the 2003 server, access denied errors.

Can someone assist me?

please open a new question for your issue