Re: SQL Developer Remote Access

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I just realized that the developer will not be within the organization. I think we are talking the wrong approach to this issue. The developer doesn't have to have access to SQL Server at all in order to develop the application. He can develop locally at their location and when they are ready to deploy they create the database part of the system at your location.

That's the proper way to do it (unless I'm missing something)

--
Costas
http://costas.cpstechgroup.com



"MF" <MF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:883D21B7-2FF5-4327-876C-AA6B62F6FBF2@xxxxxxxxxxxxxxxx
In addition to how to make it available remotely, I was confused about the
setup part where I had to choose an authentication type; Windows
Wuthentication or SQL Server Authentication. WHich is appropriate for this
scenario where the developer only needs access to the databse and nothing
else on the server?

Thanx.



"MF" wrote:

Thanx Costas,

I was able to do exactly how you explained and all seems to be set. It just
remains how to make the database accessible remotely over an IP
network/internet.

Thanx again.



"Costas" wrote:

> We might be OT, discussing SQL Server issues on the SBS forum and > hopefully
> others will be OK with it.
>
> Run SQL Server Management Studio (as Administrator) and connect to your > SQL
> Server, using Windows Authentication. If 'Object Explorer' is not > visible,
> open it from the 'View' menu item.
>
> Click on 'Security' and right-click on 'Logins'. Click 'New Login'. > Click
> the 'Search' button next to the 'Login Name'. Make sure the location > is set
> to the domain name (See: 'From this location') Add the user account you > want
> to have access to the database and click 'OK'. You just created a > Login
> object for user. Click 'OK' again.
>
> Now right click on the 'Databases' folder and select 'New Database'. > Give
> the database a name, next to the 'Owner' field click the button, and > type
> the login name you just created. If you don't type the domain name a > window
> will show up with the name that matches what you typed. Click the > checkbox
> next to the login and then 'OK'. Under 'Database Files' you'll see the > name
> of the the database and the log. To the right, under 'Path', is the > place
> on the hard drive where you specify where you want the files stored. > You
> can change that path if you like. Click 'OK'.
>
> This is the quick and dirty way. There are other options that need to > be
> set, but the developer should be able to set them since s/he is the db
> owner.
>
> Hope that helps
>
> -- > Costas
> http://costas.cpstechgroup.com
>
>
>
> "MF" <MF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:10BB7401-929C-450B-833D-2E53B234C4EA@xxxxxxxxxxxxxxxx
> > Thanx Costas for your response. I would think a specific database > > would be
> > the most secure option, but then again, I am not too familiar with
> > creating a
> > specific database to then restrict access to. I would love help in > > that
> > area
> > as well.
> >
> > Thanx again.
> >
> >
> >
> > "Costas" wrote:
> >
> >> Do you want the developer to have access to the SQL Server or a > >> specific
> >> database within SQL Server?
> >>
> >> -- > >> Costas
> >> http://costas.cpstechgroup.com
> >>
> >>
> >>
> >> "MF" <MF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:97892EC7-0488-4BFD-962D-E8911DE8324F@xxxxxxxxxxxxxxxx
> >> > Hello All,
> >> >
> >> > I am trying to provide remote access "ONLY" to SQL server on our > >> > SBS
> >> > 2003
> >> > Premium ASAP so he can access only SQL server for development > >> > purposes.
> >> >
> >> > Any Ideas how I can accomplish this.
> >> >
> >> > Thanx.
> >>
>

.

Quantcast