Domain Vs. Workgroup
Jan 31, 2008
My company has a large-ish website and we are migrating to new
servers. There will be a web server (accessible to the world) backed
by a SQL Server 2005 Standard server (only accessible by the web server and
through VPN/Remote Desktop to administrators and our internal
network). We can either put the database server (which is not in a
cluster) on our domain or leave it in a workgroup. My first thought
is leave it in a workgroup simply for security and reliability (i.e.
if the DC goes down or loses connectivity), but people here are
disagreeing with me.
Should I put the database server (which is not used internally at all)
on the domain or leave it in a workgroup?
View 1 Replies
ADVERTISEMENT
Jan 31, 2008
My company has a large-ish website and we are migrating to new
servers. There will be a web server (accessible to the world) backed
by a SQL Server 2005 Standard server (only accessible by the web server and
through VPN/Remote Desktop to administrators and our internal
network). We can either put the database server (which is not in a
cluster) on our domain or leave it in a workgroup. My first thought
is leave it in a workgroup simply for security and reliability (i.e.
if the DC goes down or loses connectivity), but people here are
disagreeing with me.
Should I put the database server (which is not used internally at all)
on the domain or leave it in a workgroup?
View 1 Replies
View Related
Sep 26, 2005
We have a set of client servers which will include a SQL Server 2000 active/passive cluster attached to a SAN. We have all the equipment here (no attachment to client site) to configure. My worry is since it will have to be setup as a workgroup, and then shipped to client to add to their domain, is this a doable option. has anyone had to do this or tried this? Or would we be better off shipping whole thing to client and setting up cluster there?
View 6 Replies
View Related
Jul 20, 2005
Hi have a small network setup and have MS sql server on workstation.Can access it locally but cannot access it from other work stations.I am assuming it is some sort of logon error, being it is not adomain. Any ideas on getting by this ?
View 2 Replies
View Related
Jul 8, 2006
In the following scenario, I am getting the message 'Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection'.
I am running a Windows Server 2003 with development environment and Sql Server Management Studio in a workgroup on a virtual PC.
My SQL Server 2000 is running on a domain server.
On the virtual Pc I have setup my user login and password to be the same as my domain login and password. Why is the Management Studio not using impersonation and allowing me to connect to the SQL server on the domain?
View 4 Replies
View Related
May 8, 2008
Hi folks,
For the past couple of days, I have been trying to get my SQL Server to work with Distributed Views. I am created linked servers, linked server logins, set XACT Abort ON.
I am successful in running a select against the distributed view, but was unable to run an "INSERT"
When I try a simple insert, the query took 3:14 minutes. Then I get an error message like:
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].
I have checked that MSDTC is running and configured under a domain account on both machines - running sQL 2000 and win2K
I have been unsuccessful still after tinkering for several days. I have checked my network configurations and noticed that when I try to ping the other machine by name, I don't get a response. I can only get a response to a ping when I enter the IP address directly.
Could this be a problem? Also, I noticed that for some strange reason, whenever I ping from either machine it is showing an external IP - always the same one no matter which computer name I try to ping. Something like 209.xxx.xxx.xxx instead of the 192.xxx.xxx.xxx that I expect.
Finally, I thought that problem was possibly due to incorrect Active Directory configuration. I tried to remove both machines from the domain by changing them to a workgroup "TEST" instead of the domain.
When I restarted the PC, I am unable to start SQL Server. It shows the Red Stop sign. When I try to start it, it gives an error like: Service could not start because one or more dependencies failed.
When I add the machine back to the domain, SQL server starts working on reboot.
Can anyone help me please.
Thanks.
View 7 Replies
View Related
Dec 27, 2006
This question is regarding a brand new out-of-the-box SQL Server 2005 Workgroup Edition install. The old SQL Server 2000 server is working properly with regard to the issue we're having:
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access.
The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN heuser" (example values). The
domain user is properly a member of group added as a login to SQL Server, and we've
confirmed that there are not conflicting permissions that would deny those
users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same domain users a member of THAT group, and finally then
follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
View 20 Replies
View Related
Aug 24, 2006
I have been asked to move a system running MS SQL 2000 Server from a workgroup to a domain. The SQL server is running in SQL Authentication and the services are running as local system.
Will SQL Server break after the move?
Any advice will help. I thought I remember this being the case, but possibly only with Windows Authentication.
View 3 Replies
View Related
Oct 12, 2007
Hi,
I have a quick question regarding domains and workgroups.
Currently I am working on an issue in the office of a small business. Right now there are 3 client computers that connect to a dell server running windows std. server 2003. The server has sql running on it that takes care of the invoicing system. Two out of the three work stations are able to use the database fine, but there is one that is unable to connect to the database. The only different that I could find is that the two workstations that DO work are currently set to use a workgroup, whereas the one workstation that does NOT work is set to use a domain...... I tried switching that computer to workgroup, but then I was unable to login as the normal user that I had always logged in as before.....
What can I do to solve this dilemma?
Any help would be greatly appreciated!
I apologize if this is the wrong forum for this, and if it is, if someone would point me to the correct one I would appreciate it.
Thanks
-steve
View 4 Replies
View Related
Jul 22, 1999
I'm trying to establish connection between two SQL servers, one on a Domain and one on a Workgroup. When I log as the local administrator to the Domain machine, everthing is fine and both machines can register each other (both machines have the same local admin user name & password.) When I log back into the Domain on the Domain machine, I cannot register the Workgroup server but I can register Domain server from the Workgroup server. Putting the Workgroup machine on my Domain won't work because I'm going to be using a firewall. Do I need to set up another domain for the Workgroup machine and configure a trust on the Domain machine? Any suggestions?
View 2 Replies
View Related
May 12, 2007
hi
COMPUTER-1
IP ::::: 129.100.100.5
COMPUTER NAME IS ::::: HASH
MEMBER OF DOMAIN
in this computer sqlserver express edition is installed, i want to remove this express becoz in configuration manager it show two SQLSERVER'S are running. when i browse from COMPUTER - 2 for network servers it show server name as HASH/SQLEXPRESS, but not the main SQLSERVER.
COMPUTER -2
IP::::129.100.100.142
COMPUTER NAME::: FEROZ
MEMBER OF WORKGROUP
can anyone help me how to connect these two computers and remove this express edition
iam new to sqlserver configuration
thanks in advance
waiting for eager reply
View 1 Replies
View Related
Sep 28, 2007
Hi,
We have the followoing:
-A "master domain" AD, a "sub domain" AD, a trust relationship between the two (sub trust master)
-A sql server 2005 on a win server 2003 in "sub domain" AD
-A linked server to "sub domain" AD
-A linked server login using a "sub domain" admin acccount
-A view to this linked server
-A grant on masterDomain/Domain Users to the database
-A grant on subDomain/Domain Users to the database
-We want all connections done through "Windows Authentication" not "Database Authentication".
Queries on the view work fine using "sub domain" user accounts.
Queries on the view fail using "master domain" user accounts (including master domain admin accounts)
"Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation."
All connections are done through "Windows Authentication" not "Database Authentication".
Can we establish cross domain connectivity with "Windows Authentication" ?
Below are details of the implementation:
SELECT TOP (100) PERCENT *
FROM OPENQUERY(ADSI,
'SELECT displayname, givenName, sn, cn (etc...)
FROM ''LDAP://OU=PEOPLE,DC=subDomain,DC=com''
WHERE objectCategory = ''Person'' AND objectClass = ''user'' ')
EXEC sp_addlinkedsrvlogin @rmtsrvname ='ADSI', @useself='false',
@rmtuser='subDomainAdminAccnt', @rmtpassword='sunDomainAdminAccntPassword';
In SQL Server Mngt Studio in Server Objects/Linked Servers/Providers/ ADSI properties security tab I have:
"connections will: <be made using this security context> Remote login:'subDomainAdminAccnt' With password: 'subDomainAdminAccntPassword'
Error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation.
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT displayname, givenName, sn, cn
FROM 'LDAP://OU=PEOPLE,DC=subDomain,DC=com'
WHERE
objectCategory = 'Person'
AND objectClass = 'user'
" against OLE DB provider "ADsDSOObject" for linked server "ADSI".
View 7 Replies
View Related
Apr 5, 2007
I have a root domain and child domain.
After using ADMT to migrate the domain user or group into the root domain, when I use enterprise manager to try and change the permissions allocated to that domain user/group, i get the 'Error 15401 NT user or Group not found'.
This is a correct error as the user is now in the root domain, however sql (in sysxlogins) still thinks its in the child domain.
Is there a simpler way, other than collecting the users permissions, deleting the user from SQL then adding back in with the correct domainusername format, then adding the permissions back?
I tried renaming the 'name' in sysxlogins (not recommended) and while that worked, whenever I tried to add the migrated user to another database, the login name was missing and would not resolve.
I believe it is something to do with the SID not matching.
Any ideas on how to fix this ?
View 1 Replies
View Related
Jun 19, 2015
we recently migrated from our in-house domain to the Enterprise domain. Everything went smooth except for the fact that I can no longer accept my dBs using my SA or my domain admin account. There is only 1 account I can get into the management studio with but it has no admin privileges, so I can't make any  password changes or add accounts. I don't have a test environment so kind of hesitant to experiment with our production system.
View 6 Replies
View Related
Sep 26, 2006
I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.
- I have try following the KB265808 - no success.
- Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.Error Message:
TITLE: Connect to Server
------------------------------
Cannot connect to ardsqldatawh.
------------------------------
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
Question: Could Windows 2003 security be blocking access? I'm using sa account to access.
Also, sa account does not seems to work for remote access. It is ok when accessing locally.
Any help would be appreciated.
949jc
View 1 Replies
View Related
Jul 20, 2005
Hi all,it happen to me a strange problem:i have a mdb file (in Access 2K) with SQL Server 2K linked tables whoruns on a workstation which is on a different domain that the SQLServer. It works.If i create a mdb file from a workstation which is a the domain of theSQL Server and then i run it a my non-domain workstation i have errormessage:Login failed for user '(null)'. Reason: Not associated with a trustedSQL Server connectionBut if i reattached my tables it works.If someone have an idea....PS: same ODBC on both machines
View 1 Replies
View Related
Mar 2, 2006
Currently running a SQL 2000 server in 2000 domain and want to migrate it to a new 2003 domain of the same name.
How do I go about it and is there any problems with this plan?
View 1 Replies
View Related
Jan 20, 2006
My package is to copy data from an Access 97 db into a SQL2k5 table.
Problem is that the 'mdb' is subscribed to a 'mdw' workgroup and I have been unable to workout / read how to get the SSIS manager to join the workgroup. Connection fails because "...you don't have necessary permission..."
I was able to do this previously for SQL 2k by messing with the registry, but I'm now on unfamiliar teritory.
Any answers? Cheers.
View 2 Replies
View Related
Jul 6, 2007
Has anyone had problems like this.
I recently got SQL Server 2005 Workgroup edition. I did the normal
'read everything I could' to make sure I was getting the correct version for my business.
After having to wait 4 weeks to upgrade, as we were waiting for our accounting system to be upgraded to come inline with SQL 2005, I came across the problem where DTS is not really compatible to the degree I needed with this edition.
I have since gone back to the reseller and they say we can't exchange it for Standard edition as 4 weeks has passed.
The only thing we can do is pay out (1 month later) another £6,000 to get the version we need, totaling £11,000
Being that we are a small business, paying out another £6,000 isn't an option.
Does anyone have any good advise on this?
Many thanks
Scott
View 4 Replies
View Related
Aug 16, 2006
Hi
I've build a client management (Windows) application in VS2005 which works fine on the local development machine but falls over when trying to connect to the SQL Server Express file located on a second machine on the same Workgroup. Several of the apllications will connect to the database file from networked computers.
The error I get when testing the connection or trying to connect via the App is:---------------------------------------------------------------The file "Z:BushBreaks.MDF" is on a network path that is not supported for database files.An attempt to attach and auto-named database for file z:ushbreaks.mdf failed. A database with the same name exists, or specified file cannot be opened or it is on a UNC share.---------------------------------------------------------------
How can I configure this database and/or connection to be able to allow connections to the MDF file? Please note that security is not an issue if that is at all relevant.
Many ThanksJohn
View 1 Replies
View Related
Apr 8, 2004
I want to copy the database backup files to another server as a part of logshipping implementation. tried using xcopy it doesn't work.
it says "invalid drive specification"
also tried using a dll, the dll does the copying i just had to call the dll through an sp, while trying this the QA hanged, tried killing the process but the process didn't kill, i had to restart the service.
the network in not a domain its workgroup.
with sql server 2000 on win2k server.
any inputs are welcome.
thanks in advance
regards,
harshal.
View 5 Replies
View Related
Apr 26, 2007
Hello,
I am currently hosting my ecommerce site on a dedicated server with dual AMD processors and 2 gigs of ram. I have on average 20 people on the site at one time.
on this server i have sql express, from which i understand, only utilizes one of the processors and 1gig of ram. I have the choice to pay an extra 150 a month to have my host put sql workgroup on my system.
My question is, will i notice any kind of real performace boost by upgrading. Or at the level that i am at, there wont be much difference?
Any help would be very useful.
Thanks
View 5 Replies
View Related
Jul 18, 2007
I would like to ask regarding sa performance difference between the two version of SQL 2005. Which is better the SQL 2005 workgroup or the standard edition..?
Darren Bernabe Blanco
View 1 Replies
View Related
Jul 23, 2005
We're running a simple network with a Windows XP Pro machine runningSQL Server. I have a VB application that runs fine on machines withinthe workgroup. There are several computers outside the workgroup butphysically reside on the network that generate OLEDB errors. I knowwith certainty it is establishing a connection to SQL Server. Theerror occurs on a SELECT statement. The user has read and writepermission to the database. I even tried giving the user Admin rightsjust as a test and it still generated the error. Is this a result ofthe cnmputer not being a member of the Workgroup? Thanks.Damon
View 4 Replies
View Related
Jan 4, 2006
How to establish connection string for sql server on non-domain network?
View 2 Replies
View Related
Jan 17, 2007
Good afternoon,so here is a question I've been struggling with that I thought folks onthe forum might have some wisdom kicking around on. I have severalproduction servers that are living within a workgroup where there is nodomain controler. However, I would still like to set up trustedsecurity for my asp.net applications. IIS is living on one server, andSQL server on another. Is there a way I can add a trusted relationshipto the machine and account that the IIS app is running under?My thanks in advance!Jonathan Wiggs*** Sent via Developersdex http://www.developersdex.com ***
View 1 Replies
View Related
Jul 19, 2007
I have two SQL servers that I am trying to setup log shipping on. I am unable to get the restore of the initial database to work on the standby server. It gets a "unable to open file" error when trying to do the restore.
I have created a "syncaccount" user on both machines, and both have same password. I have used configuration manager to set the user/password for the agents on both servers.
I have given syncaccount admin access. I have added syncaccount to the shares on both servers.
Wy am I getting this error.
Does anyone else think it is VERY difficult to make this function work.
View 7 Replies
View Related
Apr 5, 2007
Hi guys,
I am a Systems Engineer and was sent on a job to a site that has a newly created SBS 2003 R2 Premium box which was OEM pre-installed from Dell. The SBS install was evidently finished off by the I.T. guys at the site. Now along comes some software house to install their propritery application. During this install process, the software guy was unable to find an instance of SQL running and installs SQL 2005 Express and the Express Studio management console. He installs his application and before he leaves says to the I.T. guys "Oh and by the way, there is a 4GB limit per database on SQL Express. You will have to change that to workgroup edition before the data grows too big. Have a nice day byeee!!!".
The I.T. guys go "Huh? Lets call James." So now I have to get this database off the SQL Express instance and onto a workgroup instance. I understand about detaching a database and re-attaching it. No prob there. What is confusing me is when I look at the default instance which should be a Workgroup instance, all I see is an Express instance.
What I am planning to do is rip out all the SQL 2005 stuff, leaving behind only Sharepoint, SBSmonitoring and WSUS stuff. The, using the SBS Premium cd's, install SQL 2005 again and updating the service packs for it again. Then mount the databases under it and get the software guys back in to reconfigure their application if need be.
Thing is, I have no idea how to sort it all out other than "Add remove programs" in control panel and remove the SQL 2005 stuff. What scares me however, is the thought of also removing the Sharepoint, WSUS and SBSMonitoring databases too.
Can someone help me with a procedure for sorting it out? How can I tell what I should uninstall and what I shouldn't? How do I tell if workgroup is already there and why did express steal the default instance?
Cheers
James
View 1 Replies
View Related
Apr 6, 2007
I have 2 web servers in a workgroup both running SQl 2005 SP2. both servers have a user called sqluser which is the main login for sql on both boxes. When I use the mirroring wizard it creates the end points ok but does not like the fqdn of each server, these are called webserver1 and webserver2. Is the problem because of the name and lack of domain ? Can I add a user for server1 on server2 or do I need to use certificates to get Mirroring working in this type of environment ?
View 10 Replies
View Related
Jul 6, 2007
We have got the wrong version of SQL Server 2005 due to not having SSIS. We have loads of DTS packages running and I have tried to import them and its shows no SSIS service installed.
Is the route to upgrade straight forward? We have a couple of databases running on 2005 upgraded from 2000 but most still are active on 2000.
Cheers
Scott
View 1 Replies
View Related
Dec 3, 2007
I am a very beginner in setting sql server 2005.
I was not sure if sql 2005 workgroup edition supported online database when I compared on MSN comparison chart.
Does workgroup edition only work in local computers?
Can I install 2005 workgroup edition on a windows server and run a business website requiring database?Thanks in advance.
View 1 Replies
View Related
Aug 8, 2007
Hi Guys,
I'm trying to connect to a sql express on a workgroup PC through sql server 2005 standard edition remotely but i can't.
I have checked and make sure that tcp/ip and other protocals are allowed. There is no firewall on both PCs and the sql browser service is running as well.
Somehow i can connect using the IP address but not the name?
Any idea why?
TA
Gemma
View 4 Replies
View Related
Feb 3, 2007
HI All,
After i installed SQL Server 2005 workgroups edition to my Laptop, P4 and 1 Giga memory. I had a problem.
my problem is: when i start my laptop need 4 minutes to start the windows xp pro edition.
then I format my laptop and install the windows again, and every thing works fine, but I installed the SQL again and i had same problem with windows startup, there is nothing related to SQL in ;msconfig utilities.
do you have any tip about this problem ?
Thank You
View 3 Replies
View Related
