Hi.
I am in the process of "ramping-up" (read: spending more money)
on a home project. To date, I have done the web and database
development on the same machine. I have been advised to put the
DB stuff on its own box. My question is, what kind of box should this
be? What are the essentials when buying hardware for a DB connection
(ie. serverboard vs. workstation motherboard, speen, disk space,
etc).
Thanks for any tips and advice you have."pbd22" <dushkin@.gmail.com> wrote in message
news:1175186968.716011.45140@.p77g2000hsh.googlegroups.com...
> Hi.
> I am in the process of "ramping-up" (read: spending more money)
> on a home project. To date, I have done the web and database
> development on the same machine. I have been advised to put the
> DB stuff on its own box. My question is, what kind of box should this
> be? What are the essentials when buying hardware for a DB connection
> (ie. serverboard vs. workstation motherboard, speen, disk space,
> etc).
"It depends" a lot on the nature of your data.
However, databases tend to like lots of RAM and fast disk channels.
I'd have at least 2 separate disk channels with RAID 1 (or other raid such
as 10, or 5/50 for data) for data and logs.
And as much RAM as your version of SQL Server can use.
But beyond that, impossible to really advise w/o knowing more about your
database setup.
> Thanks for any tips and advice you have.
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Waiting for more infos about your database, i suggest another point of view:
I suppose that "home project" means something developed for your pleasure.
If not, and especially if you intend expose on the Network your Web Server,
it's strongly recommended to protect the dbserver (this probably would be the
meaning of "...its own box"). At the box should added security (firewalling
and so on...)
Gilberto
"Greg D. Moore (Strider)" wrote:
>
>
> "pbd22" <dushkin@.gmail.com> wrote in message
> news:1175186968.716011.45140@.p77g2000hsh.googlegroups.com...
> > Hi.
> >
> > I am in the process of "ramping-up" (read: spending more money)
> > on a home project. To date, I have done the web and database
> > development on the same machine. I have been advised to put the
> > DB stuff on its own box. My question is, what kind of box should this
> > be? What are the essentials when buying hardware for a DB connection
> > (ie. serverboard vs. workstation motherboard, speen, disk space,
> > etc).
> "It depends" a lot on the nature of your data.
> However, databases tend to like lots of RAM and fast disk channels.
> I'd have at least 2 separate disk channels with RAID 1 (or other raid such
> as 10, or 5/50 for data) for data and logs.
> And as much RAM as your version of SQL Server can use.
> But beyond that, impossible to really advise w/o knowing more about your
> database setup.
>
> >
> > Thanks for any tips and advice you have.
> >
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>|||On Mar 30, 3:34 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> Waiting for more infos about your database, i suggest another point of view:
> I suppose that "home project" means something developed for your pleasure.
> If not, and especially if you intend expose on the Network your Web Server,
> it's strongly recommended to protect the dbserver (this probably would be the
> meaning of "...its own box"). At the box should added security (firewalling
> and so on...)
> Gilberto
> "Greg D. Moore (Strider)" wrote:
>
> > "pbd22" <dush...@.gmail.com> wrote in message
> >news:1175186968.716011.45140@.p77g2000hsh.googlegroups.com...
> > > Hi.
> > > I am in the process of "ramping-up" (read: spending more money)
> > > on a home project. To date, I have done the web and database
> > > development on the same machine. I have been advised to put the
> > > DB stuff on its own box. My question is, what kind of box should this
> > > be? What are the essentials when buying hardware for a DB connection
> > > (ie. serverboard vs. workstation motherboard, speen, disk space,
> > > etc).
> > "It depends" a lot on the nature of your data.
> > However, databases tend to like lots of RAM and fast disk channels.
> > I'd have at least 2 separate disk channels with RAID 1 (or other raid such
> > as 10, or 5/50 for data) for data and logs.
> > And as much RAM as your version of SQL Server can use.
> > But beyond that, impossible to really advise w/o knowing more about your
> > database setup.
> > > Thanks for any tips and advice you have.
> > --
> > Greg Moore
> > SQL Server DBA Consulting Remote and Onsite available!
> > Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
Thanks all for your advice. Gilberto, indeed this is a stand-alone DB
server
but, per your firewalling suggestion, would you advise putting an
additional
router in between the connection from the web server and the DB box?
Or,
should the operating system's own firewalling software be sufficient
protection?
thanks again.|||Honestly i have poor skill in firewalling software; however i think that a
separated firewall would work better, considering that in this case you let
both your servers (application and DB) better devoted to their natural
"vocation", not spending CPU and resources do defend your network against
intrusions.
Gilberto
"pbd22" wrote:
> On Mar 30, 3:34 am, Gilberto Zampatti
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
> > Waiting for more infos about your database, i suggest another point of view:
> > I suppose that "home project" means something developed for your pleasure.
> > If not, and especially if you intend expose on the Network your Web Server,
> > it's strongly recommended to protect the dbserver (this probably would be the
> > meaning of "...its own box"). At the box should added security (firewalling
> > and so on...)
> > Gilberto
> >
> > "Greg D. Moore (Strider)" wrote:
> >
> >
> >
> > > "pbd22" <dush...@.gmail.com> wrote in message
> > >news:1175186968.716011.45140@.p77g2000hsh.googlegroups.com...
> > > > Hi.
> >
> > > > I am in the process of "ramping-up" (read: spending more money)
> > > > on a home project. To date, I have done the web and database
> > > > development on the same machine. I have been advised to put the
> > > > DB stuff on its own box. My question is, what kind of box should this
> > > > be? What are the essentials when buying hardware for a DB connection
> > > > (ie. serverboard vs. workstation motherboard, speen, disk space,
> > > > etc).
> >
> > > "It depends" a lot on the nature of your data.
> >
> > > However, databases tend to like lots of RAM and fast disk channels.
> >
> > > I'd have at least 2 separate disk channels with RAID 1 (or other raid such
> > > as 10, or 5/50 for data) for data and logs.
> >
> > > And as much RAM as your version of SQL Server can use.
> >
> > > But beyond that, impossible to really advise w/o knowing more about your
> > > database setup.
> >
> > > > Thanks for any tips and advice you have.
> >
> > > --
> > > Greg Moore
> > > SQL Server DBA Consulting Remote and Onsite available!
> > > Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
> Thanks all for your advice. Gilberto, indeed this is a stand-alone DB
> server
> but, per your firewalling suggestion, would you advise putting an
> additional
> router in between the connection from the web server and the DB box?
> Or,
> should the operating system's own firewalling software be sufficient
> protection?
> thanks again.
>|||On 29 Mar 2007 09:49:28 -0700, "pbd22" <dushkin@.gmail.com> wrote:
>I am in the process of "ramping-up" (read: spending more money)
>on a home project. To date, I have done the web and database
>development on the same machine. I have been advised to put the
>DB stuff on its own box. My question is, what kind of box should this
>be? What are the essentials when buying hardware for a DB connection
>(ie. serverboard vs. workstation motherboard, speen, disk space,
>etc).
Besides other good advice, know that SQLServer likes multiple
processors. A single dual-core is good and might do you for a start,
but depending on your anticipated load, more might be (much) better.
When things go mondo you'll want to go 64-bit, but that's probably
overkill at the moment. Say, 4gb RAM would be a good start.
If the database is large and the contents valuable, you'll need some
backup plans. These days it's probably easiest to buy a stack of USB
drives and/or burn DVDs regularly, but do plan ahead!
Again, if the system is likely to be heavily loaded, gigabit LAN is a
good thing, too.
J.
Showing posts with label home. Show all posts
Showing posts with label home. Show all posts
Wednesday, March 21, 2012
Database Server Hardware Architecture
Hi.
I am in the process of "ramping-up" (read: spending more money)
on a home project. To date, I have done the web and database
development on the same machine. I have been advised to put the
DB stuff on its own box. My question is, what kind of box should this
be? What are the essentials when buying hardware for a DB connection
(ie. serverboard vs. workstation motherboard, speen, disk space,
etc).
Thanks for any tips and advice you have."pbd22" <dushkin@.gmail.com> wrote in message
news:1175186968.716011.45140@.p77g2000hsh.googlegroups.com...
> Hi.
> I am in the process of "ramping-up" (read: spending more money)
> on a home project. To date, I have done the web and database
> development on the same machine. I have been advised to put the
> DB stuff on its own box. My question is, what kind of box should this
> be? What are the essentials when buying hardware for a DB connection
> (ie. serverboard vs. workstation motherboard, speen, disk space,
> etc).
"It depends" a lot on the nature of your data.
However, databases tend to like lots of RAM and fast disk channels.
I'd have at least 2 separate disk channels with RAID 1 (or other raid such
as 10, or 5/50 for data) for data and logs.
And as much RAM as your version of SQL Server can use.
But beyond that, impossible to really advise w/o knowing more about your
database setup.
> Thanks for any tips and advice you have.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Waiting for more infos about your database, i suggest another point of view:
I suppose that "home project" means something developed for your pleasure.
If not, and especially if you intend expose on the Network your Web Server,
it's strongly recommended to protect the dbserver (this probably would be th
e
meaning of "...its own box"). At the box should added security (firewalling
and so on...)
Gilberto
"Greg D. Moore (Strider)" wrote:
>
>
> "pbd22" <dushkin@.gmail.com> wrote in message
> news:1175186968.716011.45140@.p77g2000hsh.googlegroups.com...
> "It depends" a lot on the nature of your data.
> However, databases tend to like lots of RAM and fast disk channels.
> I'd have at least 2 separate disk channels with RAID 1 (or other raid such
> as 10, or 5/50 for data) for data and logs.
> And as much RAM as your version of SQL Server can use.
> But beyond that, impossible to really advise w/o knowing more about your
> database setup.
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>|||On Mar 30, 3:34 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> Waiting for more infos about your database, i suggest another point of vie
w:
> I suppose that "home project" means something developed for your pleasure.
> If not, and especially if you intend expose on the Network your Web Server
,
> it's strongly recommended to protect the dbserver (this probably would be
the
> meaning of "...its own box"). At the box should added security (firewallin
g
> and so on...)
> Gilberto
> "Greg D. Moore (Strider)" wrote:
>
>
>
>
>
>
>
>
>
>
Thanks all for your advice. Gilberto, indeed this is a stand-alone DB
server
but, per your firewalling suggestion, would you advise putting an
additional
router in between the connection from the web server and the DB box?
Or,
should the operating system's own firewalling software be sufficient
protection?
thanks again.|||Honestly i have poor skill in firewalling software; however i think that a
separated firewall would work better, considering that in this case you let
both your servers (application and DB) better devoted to their natural
"vocation", not spending CPU and resources do defend your network against
intrusions.
Gilberto
"pbd22" wrote:
> On Mar 30, 3:34 am, Gilberto Zampatti
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
>
> Thanks all for your advice. Gilberto, indeed this is a stand-alone DB
> server
> but, per your firewalling suggestion, would you advise putting an
> additional
> router in between the connection from the web server and the DB box?
> Or,
> should the operating system's own firewalling software be sufficient
> protection?
> thanks again.
>|||On 29 Mar 2007 09:49:28 -0700, "pbd22" <dushkin@.gmail.com> wrote:
>I am in the process of "ramping-up" (read: spending more money)
>on a home project. To date, I have done the web and database
>development on the same machine. I have been advised to put the
>DB stuff on its own box. My question is, what kind of box should this
>be? What are the essentials when buying hardware for a DB connection
>(ie. serverboard vs. workstation motherboard, speen, disk space,
>etc).
Besides other good advice, know that SQLServer likes multiple
processors. A single dual-core is good and might do you for a start,
but depending on your anticipated load, more might be (much) better.
When things go mondo you'll want to go 64-bit, but that's probably
overkill at the moment. Say, 4gb RAM would be a good start.
If the database is large and the contents valuable, you'll need some
backup plans. These days it's probably easiest to buy a stack of USB
drives and/or burn DVDs regularly, but do plan ahead!
Again, if the system is likely to be heavily loaded, gigabit LAN is a
good thing, too.
J.
I am in the process of "ramping-up" (read: spending more money)
on a home project. To date, I have done the web and database
development on the same machine. I have been advised to put the
DB stuff on its own box. My question is, what kind of box should this
be? What are the essentials when buying hardware for a DB connection
(ie. serverboard vs. workstation motherboard, speen, disk space,
etc).
Thanks for any tips and advice you have."pbd22" <dushkin@.gmail.com> wrote in message
news:1175186968.716011.45140@.p77g2000hsh.googlegroups.com...
> Hi.
> I am in the process of "ramping-up" (read: spending more money)
> on a home project. To date, I have done the web and database
> development on the same machine. I have been advised to put the
> DB stuff on its own box. My question is, what kind of box should this
> be? What are the essentials when buying hardware for a DB connection
> (ie. serverboard vs. workstation motherboard, speen, disk space,
> etc).
"It depends" a lot on the nature of your data.
However, databases tend to like lots of RAM and fast disk channels.
I'd have at least 2 separate disk channels with RAID 1 (or other raid such
as 10, or 5/50 for data) for data and logs.
And as much RAM as your version of SQL Server can use.
But beyond that, impossible to really advise w/o knowing more about your
database setup.
> Thanks for any tips and advice you have.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Waiting for more infos about your database, i suggest another point of view:
I suppose that "home project" means something developed for your pleasure.
If not, and especially if you intend expose on the Network your Web Server,
it's strongly recommended to protect the dbserver (this probably would be th
e
meaning of "...its own box"). At the box should added security (firewalling
and so on...)
Gilberto
"Greg D. Moore (Strider)" wrote:
>
>
> "pbd22" <dushkin@.gmail.com> wrote in message
> news:1175186968.716011.45140@.p77g2000hsh.googlegroups.com...
> "It depends" a lot on the nature of your data.
> However, databases tend to like lots of RAM and fast disk channels.
> I'd have at least 2 separate disk channels with RAID 1 (or other raid such
> as 10, or 5/50 for data) for data and logs.
> And as much RAM as your version of SQL Server can use.
> But beyond that, impossible to really advise w/o knowing more about your
> database setup.
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>|||On Mar 30, 3:34 am, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> Waiting for more infos about your database, i suggest another point of vie
w:
> I suppose that "home project" means something developed for your pleasure.
> If not, and especially if you intend expose on the Network your Web Server
,
> it's strongly recommended to protect the dbserver (this probably would be
the
> meaning of "...its own box"). At the box should added security (firewallin
g
> and so on...)
> Gilberto
> "Greg D. Moore (Strider)" wrote:
>
>
>
>
>
>
>
>
>
>
Thanks all for your advice. Gilberto, indeed this is a stand-alone DB
server
but, per your firewalling suggestion, would you advise putting an
additional
router in between the connection from the web server and the DB box?
Or,
should the operating system's own firewalling software be sufficient
protection?
thanks again.|||Honestly i have poor skill in firewalling software; however i think that a
separated firewall would work better, considering that in this case you let
both your servers (application and DB) better devoted to their natural
"vocation", not spending CPU and resources do defend your network against
intrusions.
Gilberto
"pbd22" wrote:
> On Mar 30, 3:34 am, Gilberto Zampatti
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
>
> Thanks all for your advice. Gilberto, indeed this is a stand-alone DB
> server
> but, per your firewalling suggestion, would you advise putting an
> additional
> router in between the connection from the web server and the DB box?
> Or,
> should the operating system's own firewalling software be sufficient
> protection?
> thanks again.
>|||On 29 Mar 2007 09:49:28 -0700, "pbd22" <dushkin@.gmail.com> wrote:
>I am in the process of "ramping-up" (read: spending more money)
>on a home project. To date, I have done the web and database
>development on the same machine. I have been advised to put the
>DB stuff on its own box. My question is, what kind of box should this
>be? What are the essentials when buying hardware for a DB connection
>(ie. serverboard vs. workstation motherboard, speen, disk space,
>etc).
Besides other good advice, know that SQLServer likes multiple
processors. A single dual-core is good and might do you for a start,
but depending on your anticipated load, more might be (much) better.
When things go mondo you'll want to go 64-bit, but that's probably
overkill at the moment. Say, 4gb RAM would be a good start.
If the database is large and the contents valuable, you'll need some
backup plans. These days it's probably easiest to buy a stack of USB
drives and/or burn DVDs regularly, but do plan ahead!
Again, if the system is likely to be heavily loaded, gigabit LAN is a
good thing, too.
J.
Database Server Hardware Architecture
Hi.
I am in the process of "ramping-up" (read: spending more money)
on a home project. To date, I have done the web and database
development on the same machine. I have been advised to put the
DB stuff on its own box. My question is, what kind of box should this
be? What are the essentials when buying hardware for a DB connection
(ie. serverboard vs. workstation motherboard, speen, disk space,
etc).
Thanks for any tips and advice you have.
"pbd22" <dushkin@.gmail.com> wrote in message
news:1175186968.716011.45140@.p77g2000hsh.googlegro ups.com...
> Hi.
> I am in the process of "ramping-up" (read: spending more money)
> on a home project. To date, I have done the web and database
> development on the same machine. I have been advised to put the
> DB stuff on its own box. My question is, what kind of box should this
> be? What are the essentials when buying hardware for a DB connection
> (ie. serverboard vs. workstation motherboard, speen, disk space,
> etc).
"It depends" a lot on the nature of your data.
However, databases tend to like lots of RAM and fast disk channels.
I'd have at least 2 separate disk channels with RAID 1 (or other raid such
as 10, or 5/50 for data) for data and logs.
And as much RAM as your version of SQL Server can use.
But beyond that, impossible to really advise w/o knowing more about your
database setup.
> Thanks for any tips and advice you have.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||On 29 Mar 2007 09:49:28 -0700, "pbd22" <dushkin@.gmail.com> wrote:
>I am in the process of "ramping-up" (read: spending more money)
>on a home project. To date, I have done the web and database
>development on the same machine. I have been advised to put the
>DB stuff on its own box. My question is, what kind of box should this
>be? What are the essentials when buying hardware for a DB connection
>(ie. serverboard vs. workstation motherboard, speen, disk space,
>etc).
Besides other good advice, know that SQLServer likes multiple
processors. A single dual-core is good and might do you for a start,
but depending on your anticipated load, more might be (much) better.
When things go mondo you'll want to go 64-bit, but that's probably
overkill at the moment. Say, 4gb RAM would be a good start.
If the database is large and the contents valuable, you'll need some
backup plans. These days it's probably easiest to buy a stack of USB
drives and/or burn DVDs regularly, but do plan ahead!
Again, if the system is likely to be heavily loaded, gigabit LAN is a
good thing, too.
J.
I am in the process of "ramping-up" (read: spending more money)
on a home project. To date, I have done the web and database
development on the same machine. I have been advised to put the
DB stuff on its own box. My question is, what kind of box should this
be? What are the essentials when buying hardware for a DB connection
(ie. serverboard vs. workstation motherboard, speen, disk space,
etc).
Thanks for any tips and advice you have.
"pbd22" <dushkin@.gmail.com> wrote in message
news:1175186968.716011.45140@.p77g2000hsh.googlegro ups.com...
> Hi.
> I am in the process of "ramping-up" (read: spending more money)
> on a home project. To date, I have done the web and database
> development on the same machine. I have been advised to put the
> DB stuff on its own box. My question is, what kind of box should this
> be? What are the essentials when buying hardware for a DB connection
> (ie. serverboard vs. workstation motherboard, speen, disk space,
> etc).
"It depends" a lot on the nature of your data.
However, databases tend to like lots of RAM and fast disk channels.
I'd have at least 2 separate disk channels with RAID 1 (or other raid such
as 10, or 5/50 for data) for data and logs.
And as much RAM as your version of SQL Server can use.
But beyond that, impossible to really advise w/o knowing more about your
database setup.
> Thanks for any tips and advice you have.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||On 29 Mar 2007 09:49:28 -0700, "pbd22" <dushkin@.gmail.com> wrote:
>I am in the process of "ramping-up" (read: spending more money)
>on a home project. To date, I have done the web and database
>development on the same machine. I have been advised to put the
>DB stuff on its own box. My question is, what kind of box should this
>be? What are the essentials when buying hardware for a DB connection
>(ie. serverboard vs. workstation motherboard, speen, disk space,
>etc).
Besides other good advice, know that SQLServer likes multiple
processors. A single dual-core is good and might do you for a start,
but depending on your anticipated load, more might be (much) better.
When things go mondo you'll want to go 64-bit, but that's probably
overkill at the moment. Say, 4gb RAM would be a good start.
If the database is large and the contents valuable, you'll need some
backup plans. These days it's probably easiest to buy a stack of USB
drives and/or burn DVDs regularly, but do plan ahead!
Again, if the system is likely to be heavily loaded, gigabit LAN is a
good thing, too.
J.
Friday, February 17, 2012
Database port
What port does SQL Server 2000 is using for connection ?
What I want to do is I want to connect my application from my home machine
to my office server, so I need to open the port in my office server.
Do I need to have VPN in order to connect over the internet ?Alan,
On the Microsoft SQL Server group select Server Network Utility, select
TCP/IP and click Properties. You will see the default port (usually 1433).
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
>|||Sorry, I can't find the Server Network Utility.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...[vbcol=seagreen]
> Alan,
> On the Microsoft SQL Server group select Server Network Utility, select
> TCP/IP and click Properties. You will see the default port (usually 1433).
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Alan" wrote:
>
machine[vbcol=seagreen]|||Alan wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
By default SQL server is using port 1433 so you'll have to have that
open. I'd strongly recommend that you use a VPN connection. Otherwise
you'll open your server to everyone and I doubt that's what you want...:-).
Regards
Steen Schlter Persson
Databaseadministrator / Systemadministrator|||It is in the SQL Server Program group on the server machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alan" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:%235HFdHRkGHA.836@.TK2MSFTNGP02.phx.gbl...
> Sorry, I can't find the Server Network Utility.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...
> machine
>|||Alan,
On the Microsoft SQL Server group select Server Network Utility, select
TCP/IP and click Properties. You will see the default port (usually 1433).
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
>|||Sorry, I can't find the Server Network Utility.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...[vbcol=seagreen]
> Alan,
> On the Microsoft SQL Server group select Server Network Utility, select
> TCP/IP and click Properties. You will see the default port (usually 1433).
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Alan" wrote:
>
machine[vbcol=seagreen]|||Alan wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
By default SQL server is using port 1433 so you'll have to have that
open. I'd strongly recommend that you use a VPN connection. Otherwise
you'll open your server to everyone and I doubt that's what you want...:-).
Regards
Steen Schlter Persson
Databaseadministrator / Systemadministrator|||It is in the SQL Server Program group on the server machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alan" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:%235HFdHRkGHA.836@.TK2MSFTNGP02.phx.gbl...
> Sorry, I can't find the Server Network Utility.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...
> machine
>|||Steen Persson (DK) wrote:
> Alan wrote:
> By default SQL server is using port 1433 so you'll have to have that
> open. I'd strongly recommend that you use a VPN connection. Otherwise
> you'll open your server to everyone and I doubt that's what you want...:-)
.
>
Hopefully the server is behind an existing firewall. If VPN isn't an
option, use the firewall rules to open port 1433, but only allow
connections from the IP address of your home machine. Either way, some
basic network security needs to be observed here.
What I want to do is I want to connect my application from my home machine
to my office server, so I need to open the port in my office server.
Do I need to have VPN in order to connect over the internet ?Alan,
On the Microsoft SQL Server group select Server Network Utility, select
TCP/IP and click Properties. You will see the default port (usually 1433).
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
>|||Sorry, I can't find the Server Network Utility.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...[vbcol=seagreen]
> Alan,
> On the Microsoft SQL Server group select Server Network Utility, select
> TCP/IP and click Properties. You will see the default port (usually 1433).
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Alan" wrote:
>
machine[vbcol=seagreen]|||Alan wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
By default SQL server is using port 1433 so you'll have to have that
open. I'd strongly recommend that you use a VPN connection. Otherwise
you'll open your server to everyone and I doubt that's what you want...:-).
Regards
Steen Schlter Persson
Databaseadministrator / Systemadministrator|||It is in the SQL Server Program group on the server machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alan" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:%235HFdHRkGHA.836@.TK2MSFTNGP02.phx.gbl...
> Sorry, I can't find the Server Network Utility.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...
> machine
>|||Alan,
On the Microsoft SQL Server group select Server Network Utility, select
TCP/IP and click Properties. You will see the default port (usually 1433).
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
>|||Sorry, I can't find the Server Network Utility.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...[vbcol=seagreen]
> Alan,
> On the Microsoft SQL Server group select Server Network Utility, select
> TCP/IP and click Properties. You will see the default port (usually 1433).
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Alan" wrote:
>
machine[vbcol=seagreen]|||Alan wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
By default SQL server is using port 1433 so you'll have to have that
open. I'd strongly recommend that you use a VPN connection. Otherwise
you'll open your server to everyone and I doubt that's what you want...:-).
Regards
Steen Schlter Persson
Databaseadministrator / Systemadministrator|||It is in the SQL Server Program group on the server machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alan" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:%235HFdHRkGHA.836@.TK2MSFTNGP02.phx.gbl...
> Sorry, I can't find the Server Network Utility.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...
> machine
>|||Steen Persson (DK) wrote:
> Alan wrote:
> By default SQL server is using port 1433 so you'll have to have that
> open. I'd strongly recommend that you use a VPN connection. Otherwise
> you'll open your server to everyone and I doubt that's what you want...:-)
.
>
Hopefully the server is behind an existing firewall. If VPN isn't an
option, use the firewall rules to open port 1433, but only allow
connections from the IP address of your home machine. Either way, some
basic network security needs to be observed here.
Database port
What port does SQL Server 2000 is using for connection ?
What I want to do is I want to connect my application from my home machine
to my office server, so I need to open the port in my office server.
Do I need to have VPN in order to connect over the internet ?Alan,
On the Microsoft SQL Server group select Server Network Utility, select
TCP/IP and click Properties. You will see the default port (usually 1433).
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
>|||Sorry, I can't find the Server Network Utility.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...
> Alan,
> On the Microsoft SQL Server group select Server Network Utility, select
> TCP/IP and click Properties. You will see the default port (usually 1433).
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Alan" wrote:
> > What port does SQL Server 2000 is using for connection ?
> > What I want to do is I want to connect my application from my home
machine
> > to my office server, so I need to open the port in my office server.
> > Do I need to have VPN in order to connect over the internet ?
> >
> >
> >|||Alan wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
By default SQL server is using port 1433 so you'll have to have that
open. I'd strongly recommend that you use a VPN connection. Otherwise
you'll open your server to everyone and I doubt that's what you want...:-).
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||It is in the SQL Server Program group on the server machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alan" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:%235HFdHRkGHA.836@.TK2MSFTNGP02.phx.gbl...
> Sorry, I can't find the Server Network Utility.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...
>> Alan,
>> On the Microsoft SQL Server group select Server Network Utility, select
>> TCP/IP and click Properties. You will see the default port (usually 1433).
>> Ben Nevarez, MCDBA, OCP
>> Database Administrator
>>
>> "Alan" wrote:
>> > What port does SQL Server 2000 is using for connection ?
>> > What I want to do is I want to connect my application from my home
> machine
>> > to my office server, so I need to open the port in my office server.
>> > Do I need to have VPN in order to connect over the internet ?
>> >
>> >
>> >
>|||Steen Persson (DK) wrote:
> Alan wrote:
>> What port does SQL Server 2000 is using for connection ?
>> What I want to do is I want to connect my application from my home
>> machine
>> to my office server, so I need to open the port in my office server.
>> Do I need to have VPN in order to connect over the internet ?
>>
> By default SQL server is using port 1433 so you'll have to have that
> open. I'd strongly recommend that you use a VPN connection. Otherwise
> you'll open your server to everyone and I doubt that's what you want...:-).
>
Hopefully the server is behind an existing firewall. If VPN isn't an
option, use the firewall rules to open port 1433, but only allow
connections from the IP address of your home machine. Either way, some
basic network security needs to be observed here.|||I used netstat -a to list
but what should I looking at ?
Local Address or Foreign Address ?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:OTgxdVUkGHA.976@.TK2MSFTNGP02.phx.gbl...
> Steen Persson (DK) wrote:
>> Alan wrote:
>> What port does SQL Server 2000 is using for connection ?
>> What I want to do is I want to connect my application from my home
>> machine
>> to my office server, so I need to open the port in my office server.
>> Do I need to have VPN in order to connect over the internet ?
>>
>> By default SQL server is using port 1433 so you'll have to have that
>> open. I'd strongly recommend that you use a VPN connection. Otherwise
>> you'll open your server to everyone and I doubt that's what you
>> want...:-).
>>
> Hopefully the server is behind an existing firewall. If VPN isn't an
> option, use the firewall rules to open port 1433, but only allow
> connections from the IP address of your home machine. Either way, some
> basic network security needs to be observed here.|||Alan T wrote:
> I used netstat -a to list
> but what should I looking at ?
> Local Address or Foreign Address ?
>
"Local" would imply the local machine, so assuming you're running
NETSTAT on the SQL server machine, i.e. the "local" machine, you would
want the Local Address.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com
What I want to do is I want to connect my application from my home machine
to my office server, so I need to open the port in my office server.
Do I need to have VPN in order to connect over the internet ?Alan,
On the Microsoft SQL Server group select Server Network Utility, select
TCP/IP and click Properties. You will see the default port (usually 1433).
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
>|||Sorry, I can't find the Server Network Utility.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...
> Alan,
> On the Microsoft SQL Server group select Server Network Utility, select
> TCP/IP and click Properties. You will see the default port (usually 1433).
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Alan" wrote:
> > What port does SQL Server 2000 is using for connection ?
> > What I want to do is I want to connect my application from my home
machine
> > to my office server, so I need to open the port in my office server.
> > Do I need to have VPN in order to connect over the internet ?
> >
> >
> >|||Alan wrote:
> What port does SQL Server 2000 is using for connection ?
> What I want to do is I want to connect my application from my home machine
> to my office server, so I need to open the port in my office server.
> Do I need to have VPN in order to connect over the internet ?
>
By default SQL server is using port 1433 so you'll have to have that
open. I'd strongly recommend that you use a VPN connection. Otherwise
you'll open your server to everyone and I doubt that's what you want...:-).
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||It is in the SQL Server Program group on the server machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alan" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:%235HFdHRkGHA.836@.TK2MSFTNGP02.phx.gbl...
> Sorry, I can't find the Server Network Utility.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:C2A4874D-96D8-4ABD-BAFD-C0B657C7F437@.microsoft.com...
>> Alan,
>> On the Microsoft SQL Server group select Server Network Utility, select
>> TCP/IP and click Properties. You will see the default port (usually 1433).
>> Ben Nevarez, MCDBA, OCP
>> Database Administrator
>>
>> "Alan" wrote:
>> > What port does SQL Server 2000 is using for connection ?
>> > What I want to do is I want to connect my application from my home
> machine
>> > to my office server, so I need to open the port in my office server.
>> > Do I need to have VPN in order to connect over the internet ?
>> >
>> >
>> >
>|||Steen Persson (DK) wrote:
> Alan wrote:
>> What port does SQL Server 2000 is using for connection ?
>> What I want to do is I want to connect my application from my home
>> machine
>> to my office server, so I need to open the port in my office server.
>> Do I need to have VPN in order to connect over the internet ?
>>
> By default SQL server is using port 1433 so you'll have to have that
> open. I'd strongly recommend that you use a VPN connection. Otherwise
> you'll open your server to everyone and I doubt that's what you want...:-).
>
Hopefully the server is behind an existing firewall. If VPN isn't an
option, use the firewall rules to open port 1433, but only allow
connections from the IP address of your home machine. Either way, some
basic network security needs to be observed here.|||I used netstat -a to list
but what should I looking at ?
Local Address or Foreign Address ?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:OTgxdVUkGHA.976@.TK2MSFTNGP02.phx.gbl...
> Steen Persson (DK) wrote:
>> Alan wrote:
>> What port does SQL Server 2000 is using for connection ?
>> What I want to do is I want to connect my application from my home
>> machine
>> to my office server, so I need to open the port in my office server.
>> Do I need to have VPN in order to connect over the internet ?
>>
>> By default SQL server is using port 1433 so you'll have to have that
>> open. I'd strongly recommend that you use a VPN connection. Otherwise
>> you'll open your server to everyone and I doubt that's what you
>> want...:-).
>>
> Hopefully the server is behind an existing firewall. If VPN isn't an
> option, use the firewall rules to open port 1433, but only allow
> connections from the IP address of your home machine. Either way, some
> basic network security needs to be observed here.|||Alan T wrote:
> I used netstat -a to list
> but what should I looking at ?
> Local Address or Foreign Address ?
>
"Local" would imply the local machine, so assuming you're running
NETSTAT on the SQL server machine, i.e. the "local" machine, you would
want the Local Address.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Tuesday, February 14, 2012
database owner is needed
hi,
| foouser | foouser
objects where created as dbo when they were imported from the server on the hosting company to the local staging environment;
how can i prevent this when using SQL 2000 enterprise manager for import
(note: from my exp. with sql 2005, this problem wasn't encountered when going through the same steps -- or rather similar steps -- using native sql 2005 import/export functionality within the SQL 2005 studio)
side note:
i rather find a script based answer rather learning to use the GUI, because of my DB2, mysql background -- obviously i'm not gifted when using GUI tools
on 1 of my servers (actually, the dev. server I have setup up here at home), I must included the database owner everytime I select something or make a db call.
for example
select T.foo from K inner join T on T.id = K.id
must actualy be written like:
select dbo.T.foo from dbo.K inner join dbo.T on dbo.T.id = dbo.K.id
or else it wont work
what did I do wrong for this database owner thing to be a "must" when writing queries on this server.
spec:
sql 2000 sp4You are not connecting as a dbo user.|||
That's wierd. What error are you getting? It should check the dbo owned objects after checking for an object owned by you.
|||
Amir, please update thread.
Thanks,
Derek
|||sorry folks,I was tied up on another project for the week. I came back and tried to
trouble shoot instead of wasting you guy's time but at the end, i
failed.
basically, here is the situation:
the actual server that will end up hosting the project is setup fine so if i leave out the dbo.* or user.* and just type select * from table it works.
right now, i'm resorting to including the dbo in my queries... and evertime i upload to the server, i do a search in that folder and replace " dbo." with "" in all files.
let me explain how i made this database:
originally, it was on a dev server somewhere in US...
i made the db on my home server. Then created a user and gave it admin privilages over that db.
Then i did "All Tasks > Import" and imported the tables from that server, to this new home db. I had to go back and manually select the primary key for each table, as they got lost during the transfer.
now, when i look at the "Server Explorer" cluster of tables in this new database, i see that they all have (dbo) beside their names, meaning the owner of each table by default is dbo.
i think that should pretty much cover everything....
any clue as to why user "must" be specified?|||
What do you get on the server that requires dbo. when you execute:
select suser_sname(), user_name()
Also, for some object where you have to enter dbo. for the object, execute:
select *
from sysobjects
where name = '<name>'
select *
from information_schema.tables
where table_name = '<name>'
Perhaps this will shed some light? Also what is in @.@.version?
This might just be a stumper that requires a higher power :)
|||> What do you get on the server that requires dbo. when you execute:
>select suser_sname(), user_name()
| __|_| foouser | foouser
>select *
>from sysobjects
>where name = '<name>'
irrelevant
> select *
> from information_schema.tables
> where table_name = '<name>'
TABLE_SCHEMA is 'dbo' for all objects
conclusion:
objects where created as dbo when they were imported from the server on the hosting company to the local staging environment;
how can i prevent this when using SQL 2000 enterprise manager for import
(note: from my exp. with sql 2005, this problem wasn't encountered when going through the same steps -- or rather similar steps -- using native sql 2005 import/export functionality within the SQL 2005 studio)
side note:
i rather find a script based answer rather learning to use the GUI, because of my DB2, mysql background -- obviously i'm not gifted when using GUI tools
Subscribe to:
Posts (Atom)