change the TCP/IP port SQL Server listens on

Hi:
To change the TCP/IP port SQL Server listens on:
1) Launch the Server network utility on the server
2) Select the instance you want to configure from the drop-down
3) Select TCP/IP from Enabled protocols
4) Click Properties
5) Change the default port to a different port
6) Restart SQL Server service
And for client side what should we do ? Normally i didn't install
client access library on the client site, so the client network utility
will not be in the client machine right ?
Please help
Thanks
JCVoonOn the clientside, you would just run Client Network Utility (cliconfg.exe).
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143613530.062172.268920@.v46g2000cwv.googlegroups.com...
> Hi:
> To change the TCP/IP port SQL Server listens on:
> 1) Launch the Server network utility on the server
> 2) Select the instance you want to configure from the drop-down
> 3) Select TCP/IP from Enabled protocols
> 4) Click Properties
> 5) Change the default port to a different port
> 6) Restart SQL Server service
>
> And for client side what should we do ? Normally i didn't install
> client access library on the client site, so the client network utility
> will not be in the client machine right ?
> Please help
> Thanks
> JCVoon
>|||oj:
Is the Client Network Utility (cliconfg.exe) exists in default windows
installation ?
Thanks
JCvoon|||Cliconfg.exe is installed part of the MDAC
(http://msdn.microsoft.com/data/mdac...ds/default.aspx)
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143679737.916913.97130@.t31g2000cwb.googlegroups.com...
> oj:
> Is the Client Network Utility (cliconfg.exe) exists in default windows
> installation ?
> Thanks
> JCvoon
>|||oj:
Thank you.
JCVoon

change the TCP/IP port SQL Server listens on

Hi:
To change the TCP/IP port SQL Server listens on:
1) Launch the Server network utility on the server
2) Select the instance you want to configure from the drop-down
3) Select TCP/IP from Enabled protocols
4) Click Properties
5) Change the default port to a different port
6) Restart SQL Server service
And for client side what should we do ? Normally i didn't install
client access library on the client site, so the client network utility
will not be in the client machine right ?
Please help
Thanks
JCVoonOn the clientside, you would just run Client Network Utility (cliconfg.exe).
--
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143613530.062172.268920@.v46g2000cwv.googlegroups.com...
> Hi:
> To change the TCP/IP port SQL Server listens on:
> 1) Launch the Server network utility on the server
> 2) Select the instance you want to configure from the drop-down
> 3) Select TCP/IP from Enabled protocols
> 4) Click Properties
> 5) Change the default port to a different port
> 6) Restart SQL Server service
>
> And for client side what should we do ? Normally i didn't install
> client access library on the client site, so the client network utility
> will not be in the client machine right ?
> Please help
> Thanks
> JCVoon
>|||oj:
Is the Client Network Utility (cliconfg.exe) exists in default windows
installation ?
Thanks
JCvoon|||Cliconfg.exe is installed part of the MDAC
(http://msdn.microsoft.com/data/mdac/downloads/default.aspx)
--
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143679737.916913.97130@.t31g2000cwb.googlegroups.com...
> oj:
> Is the Client Network Utility (cliconfg.exe) exists in default windows
> installation ?
> Thanks
> JCvoon
>|||oj:
Thank you.
JCVoon

change the TCP/IP port SQL Server listens on

Hi:
To change the TCP/IP port SQL Server listens on:
1) Launch the Server network utility on the server
2) Select the instance you want to configure from the drop-down
3) Select TCP/IP from Enabled protocols
4) Click Properties
5) Change the default port to a different port
6) Restart SQL Server service
And for client side what should we do ? Normally i didn't install
client access library on the client site, so the client network utility
will not be in the client machine right ?
Please help
Thanks
JCVoon
On the clientside, you would just run Client Network Utility (cliconfg.exe).
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143613530.062172.268920@.v46g2000cwv.googlegr oups.com...
> Hi:
> To change the TCP/IP port SQL Server listens on:
> 1) Launch the Server network utility on the server
> 2) Select the instance you want to configure from the drop-down
> 3) Select TCP/IP from Enabled protocols
> 4) Click Properties
> 5) Change the default port to a different port
> 6) Restart SQL Server service
>
> And for client side what should we do ? Normally i didn't install
> client access library on the client site, so the client network utility
> will not be in the client machine right ?
> Please help
> Thanks
> JCVoon
>
|||oj:
Is the Client Network Utility (cliconfg.exe) exists in default windows
installation ?
Thanks
JCvoon
|||Cliconfg.exe is installed part of the MDAC
(http://msdn.microsoft.com/data/mdac/...s/default.aspx)
-oj
"jcvoon" <jcvoon@.maximas.com.my> wrote in message
news:1143679737.916913.97130@.t31g2000cwb.googlegro ups.com...
> oj:
> Is the Client Network Utility (cliconfg.exe) exists in default windows
> installation ?
> Thanks
> JCvoon
>
|||oj:
Thank you.
JCVoon

Change Object Ownership

I'm running SQL2K on an Win 2K Server. Because of addition of additions to our network, we've installed AD on the Win 2K to graduate
it to a Domain Controller Server. Checking the event log, one finds
an ownership warning:

Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/15/2002
Time: 8:00:01 PM
User: N/A
Computer: XXXXX-XXX
Description:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1'' (0x72097D93A71E1842AA6C46E6AC59750B) - Status: Failed - Invoked on: 2002-01-15 20:00:01 - Message: The job failed. The owner () of job DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1' does not have server access.

I believe this warning is generated because the SQLServer system is
looking to execute the DB Backup plan using the new Domain
administrative account. I came to this conclusion after reviewing
replication ownership warnings in the event log. I was easly able to
change replication jobs from then new Domain administrative account
to sa.

I would like to change the ownership to sa for a Maintenance Plan.
Is there a way to do this? Is this the solution?You would be better off not using a maintenance plan but coding the requirement yourself in a stored procedure. It is very easy to do and gets round these problems as you know what it is doing.

change Login Name

I just create a new DB under SQL 2000 and the Login Name is my network id
How can i change this to be SA like it should beCan you just disconnect the server in Enterprise Manager, then re-register
the server selecting SQL Server Authentication, and using the username 'sa'
"Mike" <csharpcoder@.sbcglobal.net> wrote in message
news:eqMH7O05DHA.1672@.TK2MSFTNGP12.phx.gbl...
> I just create a new DB under SQL 2000 and the Login Name is my network id
> How can i change this to be SA like it should be
>
>|||no, that don't work, it is still my name under the Login Name, i need it to
be sa
"Ryan Breakspear" <r.breakspear@.removespamfdsltd.co.uk> wrote in message
news:uRIL2R05DHA.2416@.TK2MSFTNGP10.phx.gbl...
> Can you just disconnect the server in Enterprise Manager, then re-register
> the server selecting SQL Server Authentication, and using the username
'sa'
> "Mike" <csharpcoder@.sbcglobal.net> wrote in message
> news:eqMH7O05DHA.1672@.TK2MSFTNGP12.phx.gbl...
> > I just create a new DB under SQL 2000 and the Login Name is my network
id
> > How can i change this to be SA like it should be
> >
> >
> >
>|||So if you look at the Users list, the Name says sa, and the Login Name is
your user name? That sounds a bit strange. I know that if you try and log
in as 'sa', and get the password wrong, then SQL Server will try and log you
on using integrated login without you knowing. I always thought that sa
couldn't be an integrated login.
"Mike" <csharpcoder@.sbcglobal.net> wrote in message
news:eKiSpY05DHA.2580@.TK2MSFTNGP11.phx.gbl...
> no, that don't work, it is still my name under the Login Name, i need it
to
> be sa
> "Ryan Breakspear" <r.breakspear@.removespamfdsltd.co.uk> wrote in message
> news:uRIL2R05DHA.2416@.TK2MSFTNGP10.phx.gbl...
> > Can you just disconnect the server in Enterprise Manager, then
re-register
> > the server selecting SQL Server Authentication, and using the username
> 'sa'
> > "Mike" <csharpcoder@.sbcglobal.net> wrote in message
> > news:eqMH7O05DHA.1672@.TK2MSFTNGP12.phx.gbl...
> > > I just create a new DB under SQL 2000 and the Login Name is my network
> id
> > > How can i change this to be SA like it should be
> > >
> > >
> > >
> >
> >
>|||Use the sp_changedbowner stored procedure. It is documented in Books on
Line.
Rand
This posting is provided "as is" with no warranties and confers no rights.

change Login Name

I just create a new DB under SQL 2000 and the Login Name is my network id
How can i change this to be SA like it should beCan you just disconnect the server in Enterprise Manager, then re-register
the server selecting SQL Server Authentication, and using the username 'sa'
"Mike" <csharpcoder@.sbcglobal.net> wrote in message
news:eqMH7O05DHA.1672@.TK2MSFTNGP12.phx.gbl...

quote:

---

> I just create a new DB under SQL 2000 and the Login Name is my network id
> How can i change this to be SA like it should be
>
>

---

|||no, that don't work, it is still my name under the Login Name, i need it to
be sa
"Ryan Breakspear" <r.breakspear@.removespamfdsltd.co.uk> wrote in message
news:uRIL2R05DHA.2416@.TK2MSFTNGP10.phx.gbl...

quote:

---

> Can you just disconnect the server in Enterprise Manager, then re-register
> the server selecting SQL Server Authentication, and using the username

---

'sa'

quote:

---

> "Mike" <csharpcoder@.sbcglobal.net> wrote in message
> news:eqMH7O05DHA.1672@.TK2MSFTNGP12.phx.gbl...
id[QUOTE]
>

---

|||So if you look at the Users list, the Name says sa, and the Login Name is
your user name? That sounds a bit strange. I know that if you try and log
in as 'sa', and get the password wrong, then SQL Server will try and log you
on using integrated login without you knowing. I always thought that sa
couldn't be an integrated login.
"Mike" <csharpcoder@.sbcglobal.net> wrote in message
news:eKiSpY05DHA.2580@.TK2MSFTNGP11.phx.gbl...

quote:

---

> no, that don't work, it is still my name under the Login Name, i need it

---

to

quote:

---

> be sa
> "Ryan Breakspear" <r.breakspear@.removespamfdsltd.co.uk> wrote in message
> news:uRIL2R05DHA.2416@.TK2MSFTNGP10.phx.gbl...
re-register[QUOTE]
> 'sa'
> id
>

---

|||Use the sp_changedbowner stored procedure. It is documented in Books on
Line.
Rand
This posting is provided "as is" with no warranties and confers no rights.