Arthur Fuller
artful at rogers.com
Mon Oct 11 14:33:19 CDT 2004
Colby, John wrote: >Francisco, > >Thanks for that. I am not running the XP firewall (never will) but I am >running a firewall. However I disabled all the firewalls for the purposes >of testing this stuff and that didn't help. Having the port number is >important though for setting up my firewalls so I appreciate that. > >The problem with using SQL Server authentication is that as soon as I get >into that I have to set up users (none exist at this point) and that brings >up what rights they need. There are a TON of them and I don't really >understand that stuff. One of the reasons I specifically asked for "step by >step". > >John W. Colby >The DIS Database Guy > > >-----Original Message----- >From: Francisco Tapia [mailto:fhtapia at gmail.com] >Sent: Monday, October 11, 2004 1:10 PM >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] Problems registering database > > >Not only that, you are running XP SP2 IIRC from one of your ealier >posts... please check that your software firewall is allowing sql >server to get through it default listens on port 1433, so please make >sure that at least this port is open. > >2ndly make sure that the Sql Server is set up to listen in mixed mode >so you can at your whim, choose between nt authentication and sql >Server sercuity... to do this go to Neo2, and right click the server >in EM, and choose the type of authentication allowed. > >when registering from other pc's you can elect to use the IP instead >of the name, and thus make for less headaches.. > > >On Mon, 11 Oct 2004 09:25:41 +0930, Haslett, Andrew ><andrew.haslett at ilc.gov.au> wrote: > > >>Use SQL Server authentication and specify a username and password when >>connecting. >> >> >> >>-----Original Message----- >>From: John W. Colby [mailto:jwcolby at colbyconsulting.com] >>Sent: Sunday, 10 October 2004 4:06 PM >>To: SQLServer >>Subject: [dba-SQLServer] Problems registering database >> >>OK, I really need to get my SQL Server on one machine registered on my >> >> >other > > >>machines so I can get some work done. >> >>I have 5 computers I need to use. >> >>I have the nVLDB database running on Neo2 I have SQL Server (client and >>server) running on Neo1, Soltek1, ColbyM6805 and soon on MaryDesktop. >> >>I need to get as many computers as possible running against Neo2 doing >>updates to the data in nVLDB. The deal is that a single field in nVLDB >> >> >has > > >>a mishmash of data for the names of people, i.e. titles, first name, >> >> >middle > > >>name, last name, in any combination. For my purposes all I really need is >>the last complete word (name) from this mishmash. I am not swift enough >>with SQL Server and its built-in functions to find the position of the >> >> >LAST > > >>space (if any) but I do have code to find the FIRST space. Thus my >>objective is to pull out everything after the first space from the >>EntireName field and save it in a LastName field, then on the second and >>subsequent passes pull everything after the first space from the LastName >>field and drop it back into the last name field. Crude, but I have plenty >>of horsepower if I can get all my computers banging away at this. >> >>BTW, I ran (and timed) the "everything after the first space" query on >> >> >Neo2 > > >>itself for a subset of 100,000 records and came up with about 10 hours to >>perform the update query for 64 million records, directly by a single >>machine. Which means I could just do this if I have to by setting it to >> >> >run > > >>overnight. >> >>I make a giant assumption that SQL Server can handle 4 different computers >>all trying to update data in the same field but against a different set of >>records? >> >>Once that is finished, I will do essentially the same thing except against >>the last name field itself, in order to get rid of middle names. Thus >> >> >this > > >>will be an iterative process until eventually I am left with the last name >>itself, in the last name field. >> >>My problem here is that I can't get any other computer to register Neo2 >> >> >SQL > > >>server. I always get a "login failed as guest". Any help in getting >> >> >around > > >>this would be much appreciated. Explicit step by step instructions would >>help the most as I am by no stretch of the imagination fluent in SQL >>Server-ese. >> >>Thanks, >> >>John W. Colby >>www.ColbyConsulting.com >> >>Contribute your unused CPU cycles to a good cause: >>http://folding.stanford.edu/ >> >>_______________________________________________ >>dba-SQLServer mailing list >>dba-SQLServer at databaseadvisors.com >>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >>http://www.databaseadvisors.com >> >>IMPORTANT - PLEASE READ ******************** >>This email and any files transmitted with it are confidential and may >>contain information protected by law from disclosure. >>If you have received this message in error, please notify the sender >>immediately and delete this email from your system. >>No warranty is given that this email or files, if attached to this >>email, are free from computer viruses or other defects. They >>are provided on the basis the user assumes all responsibility for >>loss, damage or consequence resulting directly or indirectly from >>their use, whether caused by the negligence of the sender or not. >> >> >>_______________________________________________ >>dba-SQLServer mailing list >>dba-SQLServer at databaseadvisors.com >>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >>http://www.databaseadvisors.com >> >> >> >> > > > > At least for the time being, you only need 1 user, which you already have -- sa. Once you finally get around to adding users I STRONGLY recommend that you use roles rather than just users. That way you can define a role once, and then add all the users you want to it. Change the roles of the role and all users inherit the change. You can also build roles up. I often go this route. I.e. Role -- sales staff:: no table rights. Rights to various procedures that allow update, insert, delete maybe. Role -- Manager: no table rights. Rights to do anything Sales can do, plus run some reports and view salaries. Role -- Developer:: rights to tables, sprocs, views, etc. Now add JWC to Sales and also to Manager. Everyone else in Sales gets only those rights, but JWC gets Manager rights as well.