Newbie question

hi,
I am interested in building a DW for my company. As usual, we have 4
different systems which holds different applications. I would like to know
what is the first step of buidling the DW? Retrieve the columns / data that
we need? Any good link to view?
Thanks so much
Ed
On Nov 5, 10:26 pm, Ed <E...@.discussions.microsoft.com> wrote:
> hi,
> I am interested in building a DW for my company. As usual, we have 4
> different systems which holds different applications. I would like to know
> what is the first step of buidling the DW? Retrieve the columns / data that
> we need? Any good link to view?
> Thanks so much
> Ed
The first step is to close your eyes, take a deep breath, and prepare
for a long and exciting journey.
I am _very_ new to the DW/BI scene so bear that in mind when reading
this post.
I have found these websites helpful:
http://www.dwinfocenter.org/
http://www.kimballgroup.com/
However, what works best for me is the old-fashioned approach: book
learning combined with trail-and-error. You might want to stop by a
bookstore (or use Amazon's "Search Inside" feature) and flip through
some of these titles: http://www.kimballgroup.com/html/books.html
I all but stopped buying technical books several years ago because the
information is often outdated by the time the book goes to press.
Having said that, for a subject that is deep, wide, and unfamiliar,
trying to get up to speed using only internet searches can be
frustrating and counterproductive.
Best wishes on your project!
|||You can hire my team!
"happy camper" <keenan@.p2sol.com> wrote in message
news:1194471643.414378.82940@.57g2000hsv.googlegrou ps.com...
> On Nov 5, 10:26 pm, Ed <E...@.discussions.microsoft.com> wrote:
> The first step is to close your eyes, take a deep breath, and prepare
> for a long and exciting journey.
> I am _very_ new to the DW/BI scene so bear that in mind when reading
> this post.
> I have found these websites helpful:
> http://www.dwinfocenter.org/
> http://www.kimballgroup.com/
> However, what works best for me is the old-fashioned approach: book
> learning combined with trail-and-error. You might want to stop by a
> bookstore (or use Amazon's "Search Inside" feature) and flip through
> some of these titles: http://www.kimballgroup.com/html/books.html
> I all but stopped buying technical books several years ago because the
> information is often outdated by the time the book goes to press.
> Having said that, for a subject that is deep, wide, and unfamiliar,
> trying to get up to speed using only internet searches can be
> frustrating and counterproductive.
> Best wishes on your project!
>
|||Gartner claimed a short time ago that DW efforts were the near 50% failure
rate.
Maybe start with just a data mart on a specific subject area on just one of
your 4 applications. Get the ETL working with SSIS, develop a cube in SSAS
and use Excel 2007 to browse cubes or just use SSMS.
Once you are succesful on a specific subject area then you can start pulling
in your other hetrogenous sources.
Without help you will flail about some - so if at all possible; hire some
assistance.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:eS3A$SdIIHA.4196@.TK2MSFTNGP04.phx.gbl...
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:CD21EB5F-6FA2-422B-A115-CDCC5D5910AD@.microsoft.com...
> If you don't have BI experience then get some experienced assistance on
> site. A DW is only one part of a BI solution. To be successful and deliver
> value to your business customers you should first consider the whole
> end-to-end picture.
> --
> David Portas
>
|||To name just a few items: Create small wins for yourself by Implementing
incrementally, always working on those sections that will have the biggest
positive businss impact and can released in the shortest amount of time. If
you don't already know how to data model, learn. Read Ralph Kimball's books
on OLAP design and implementation
Sincerely,
John K
President
Knowledgy Consulting, LLC
1024 Spalding Forest Ct.
Atlanta, GA 30328
Knowledgy.org
Contact: Knowledgy$knowledgy.org
Replace $ with @. for emails

Newbie Question

I have 3 busines applications that will be porting to SQL server. Can I size
a SQL server to house the 3 databases and the associated programs on the same
box? Or should I put up a SQL box and have the apps on a seperate server? We
are a small company so the IT budget is small so I'm looking for the most
cost effective solution. But I'm also concerned about the single point of
failure this will create. Any suggestions would be appreciated.
Thanks,
rwbeck
"rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
news:A7DC6DB7-2123-4F1B-B362-77DE287D1CF9@.microsoft.com...
> I have 3 busines applications that will be porting to SQL server. Can I
size
> a SQL server to house the 3 databases and the associated programs on the
same
> box? Or should I put up a SQL box and have the apps on a seperate server?
We
> are a small company so the IT budget is small so I'm looking for the most
> cost effective solution. But I'm also concerned about the single point of
> failure this will create. Any suggestions would be appreciated.
> Thanks,
> rwbeck
How big are the databases? How much activity will be going on in those
systems? How much activity in the front-end applications?
Depending on what and how the front-end is developed, you may have many
different points of "single point of failure".
The best answer is to use Tier 1 hardware for your production environment.
If it is small and fairly low in activity, then you can put it all on the
same box. You should continually monitor your SQL Server's performance to
ensure that everything is operating and playing well together. If the SQL
Server is being starved for memory or CPU cycles etc., then you may want to
start looking at a multi-box solution. It is all about balancing.
Ensure that you have a good backup and RECOVERY strategy and PRACTICE it.
Perform a sample disaster recovery, and I'm not just talking about restoring
the database on the same server. Pretend you had a fire in the building and
have to rebuild a new server from scratch. Where is the s/w located for
the O/S, SQL Server etc. Where are the backups of your current software
packages that runs on this system. How will it connect to it's users
(remember we had a "fire" in the building and lost everying in the
building.). How long does it take to truly recover. Write it all down in
a disaster recovery plan.
HTH
Rick Sawtell
|||Thank you for the input. I'm providing answers to the questions you posted.
Each of the 3 DB's are 2-3GB. Two of the three are core apps, all 40 users
are in one all day(Case management/contact management). The second is
accessed concurrently by no more than 10 users. The third is time and billing
which is accessed sporadically throughout the day. The hardware will
definitely be tier 1.
Do you think it is feasible to house 3 DBs of that size on one tier 1
server? As far as sizing, using the requirements of each application do we
double up or is there some basic formula we can reference to help with sizing
a server for this type of deployment.
Are there any other sources you think I should reference that would help?
Thanks again.
Rwbeck
"Rick Sawtell" wrote:

> "rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
> news:A7DC6DB7-2123-4F1B-B362-77DE287D1CF9@.microsoft.com...
> size
> same
> We
>
> How big are the databases? How much activity will be going on in those
> systems? How much activity in the front-end applications?
> Depending on what and how the front-end is developed, you may have many
> different points of "single point of failure".
> The best answer is to use Tier 1 hardware for your production environment.
> If it is small and fairly low in activity, then you can put it all on the
> same box. You should continually monitor your SQL Server's performance to
> ensure that everything is operating and playing well together. If the SQL
> Server is being starved for memory or CPU cycles etc., then you may want to
> start looking at a multi-box solution. It is all about balancing.
> Ensure that you have a good backup and RECOVERY strategy and PRACTICE it.
> Perform a sample disaster recovery, and I'm not just talking about restoring
> the database on the same server. Pretend you had a fire in the building and
> have to rebuild a new server from scratch. Where is the s/w located for
> the O/S, SQL Server etc. Where are the backups of your current software
> packages that runs on this system. How will it connect to it's users
> (remember we had a "fire" in the building and lost everying in the
> building.). How long does it take to truly recover. Write it all down in
> a disaster recovery plan.
> HTH
> Rick Sawtell
>
>
|||"rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
news:9067FEAF-604C-41A8-83C4-33967AD48CD9@.microsoft.com...
> Thank you for the input. I'm providing answers to the questions you
posted.
> Each of the 3 DB's are 2-3GB. Two of the three are core apps, all 40 users
> are in one all day(Case management/contact management). The second is
> accessed concurrently by no more than 10 users. The third is time and
billing
> which is accessed sporadically throughout the day. The hardware will
> definitely be tier 1.
> Do you think it is feasible to house 3 DBs of that size on one tier 1
> server? As far as sizing, using the requirements of each application do we
> double up or is there some basic formula we can reference to help with
sizing
> a server for this type of deployment.
> Are there any other sources you think I should reference that would help?
> Thanks again.
> Rwbeck
>
Those databases are relatively small and if you are simply doing contact
management and case management, then I would say that those systems are very
lightweight. The billing application may see some activity if it is
performing calculations, or doing heavy reporting, but with so few users on
the system, I would not worry about this impacting performance much.
As far as sizing your server etc. there are many different books of SQL
Server Administration. Pick one that you like and read through it. Once
you have a good understanding of what SQL Server does behind the scenes you
will be able to make better choices. This website is a gold-mine of great
information http://www.sql-server-performance.com/ Check it out.
HTH
Rick Sawtell
|||Really appreciate your help!
"Rick Sawtell" wrote:

> "rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
> news:9067FEAF-604C-41A8-83C4-33967AD48CD9@.microsoft.com...
> posted.
> billing
> sizing
> Those databases are relatively small and if you are simply doing contact
> management and case management, then I would say that those systems are very
> lightweight. The billing application may see some activity if it is
> performing calculations, or doing heavy reporting, but with so few users on
> the system, I would not worry about this impacting performance much.
> As far as sizing your server etc. there are many different books of SQL
> Server Administration. Pick one that you like and read through it. Once
> you have a good understanding of what SQL Server does behind the scenes you
> will be able to make better choices. This website is a gold-mine of great
> information http://www.sql-server-performance.com/ Check it out.
> HTH
> Rick Sawtell
>
>
sql

Newbie question

hi,
I am interested in building a DW for my company. As usual, we have 4
different systems which holds different applications. I would like to know
what is the first step of buidling the DW? Retrieve the columns / data that
we need? Any good link to view?
Thanks so much
EdOn Nov 5, 10:26 pm, Ed <E...@.discussions.microsoft.com> wrote:
> hi,
> I am interested in building a DW for my company. As usual, we have 4
> different systems which holds different applications. I would like to kno
w
> what is the first step of buidling the DW? Retrieve the columns / data th
at
> we need? Any good link to view?
> Thanks so much
> Ed
The first step is to close your eyes, take a deep breath, and prepare
for a long and exciting journey.
I am _very_ new to the DW/BI scene so bear that in mind when reading
this post.
I have found these websites helpful:
http://www.dwinfocenter.org/
http://www.kimballgroup.com/
However, what works best for me is the old-fashioned approach: book
learning combined with trail-and-error. You might want to stop by a
bookstore (or use Amazon's "Search Inside" feature) and flip through
some of these titles: http://www.kimballgroup.com/html/books.html
I all but stopped buying technical books several years ago because the
information is often outdated by the time the book goes to press.
Having said that, for a subject that is deep, wide, and unfamiliar,
trying to get up to speed using only internet searches can be
frustrating and counterproductive.
Best wishes on your project!|||You can hire my team!
"happy camper" <keenan@.p2sol.com> wrote in message
news:1194471643.414378.82940@.57g2000hsv.googlegroups.com...
> On Nov 5, 10:26 pm, Ed <E...@.discussions.microsoft.com> wrote:
> The first step is to close your eyes, take a deep breath, and prepare
> for a long and exciting journey.
> I am _very_ new to the DW/BI scene so bear that in mind when reading
> this post.
> I have found these websites helpful:
> http://www.dwinfocenter.org/
> http://www.kimballgroup.com/
> However, what works best for me is the old-fashioned approach: book
> learning combined with trail-and-error. You might want to stop by a
> bookstore (or use Amazon's "Search Inside" feature) and flip through
> some of these titles: http://www.kimballgroup.com/html/books.html
> I all but stopped buying technical books several years ago because the
> information is often outdated by the time the book goes to press.
> Having said that, for a subject that is deep, wide, and unfamiliar,
> trying to get up to speed using only internet searches can be
> frustrating and counterproductive.
> Best wishes on your project!
>|||"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:CD21EB5F-6FA2-422B-A115-CDCC5D5910AD@.microsoft.com...
> hi,
> I am interested in building a DW for my company. As usual, we have 4
> different systems which holds different applications. I would like to
> know
> what is the first step of buidling the DW? Retrieve the columns / data
> that
> we need? Any good link to view?
> Thanks so much
> Ed
If you don't have BI experience then get some experienced assistance on
site. A DW is only one part of a BI solution. To be successful and deliver
value to your business customers you should first consider the whole
end-to-end picture.
David Portas|||Gartner claimed a short time ago that DW efforts were the near 50% failure
rate.
Maybe start with just a data mart on a specific subject area on just one of
your 4 applications. Get the ETL working with SSIS, develop a cube in SSAS
and use Excel 2007 to browse cubes or just use SSMS.
Once you are succesful on a specific subject area then you can start pulling
in your other hetrogenous sources.
Without help you will flail about some - so if at all possible; hire some
assistance.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:eS3A$SdIIHA.4196@.TK2MSFTNGP04.phx.gbl...
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:CD21EB5F-6FA2-422B-A115-CDCC5D5910AD@.microsoft.com...
> If you don't have BI experience then get some experienced assistance on
> site. A DW is only one part of a BI solution. To be successful and deliver
> value to your business customers you should first consider the whole
> end-to-end picture.
> --
> David Portas
>|||To name just a few items: Create small wins for yourself by Implementing
incrementally, always working on those sections that will have the biggest
positive businss impact and can released in the shortest amount of time. If
you don't already know how to data model, learn. Read Ralph Kimball's books
on OLAP design and implementation
Sincerely,
John K
President
Knowledgy Consulting, LLC
1024 Spalding Forest Ct.
Atlanta, GA 30328
---
Knowledgy.org
---
Contact: Knowledgy$knowledgy.org
Replace $ with @. for emails
---

Newbie Question

I have 3 busines applications that will be porting to SQL server. Can I size
a SQL server to house the 3 databases and the associated programs on the sam
e
box? Or should I put up a SQL box and have the apps on a seperate server? We
are a small company so the IT budget is small so I'm looking for the most
cost effective solution. But I'm also concerned about the single point of
failure this will create. Any suggestions would be appreciated.
Thanks,
rwbeck"rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
news:A7DC6DB7-2123-4F1B-B362-77DE287D1CF9@.microsoft.com...
> I have 3 busines applications that will be porting to SQL server. Can I
size
> a SQL server to house the 3 databases and the associated programs on the
same
> box? Or should I put up a SQL box and have the apps on a seperate server?
We
> are a small company so the IT budget is small so I'm looking for the most
> cost effective solution. But I'm also concerned about the single point of
> failure this will create. Any suggestions would be appreciated.
> Thanks,
> rwbeck
How big are the databases? How much activity will be going on in those
systems? How much activity in the front-end applications?
Depending on what and how the front-end is developed, you may have many
different points of "single point of failure".
The best answer is to use Tier 1 hardware for your production environment.
If it is small and fairly low in activity, then you can put it all on the
same box. You should continually monitor your SQL Server's performance to
ensure that everything is operating and playing well together. If the SQL
Server is being starved for memory or CPU cycles etc., then you may want to
start looking at a multi-box solution. It is all about balancing.
Ensure that you have a good backup and RECOVERY strategy and PRACTICE it.
Perform a sample disaster recovery, and I'm not just talking about restoring
the database on the same server. Pretend you had a fire in the building and
have to rebuild a new server from scratch. Where is the s/w located for
the O/S, SQL Server etc. Where are the backups of your current software
packages that runs on this system. How will it connect to it's users
(remember we had a "fire" in the building and lost everying in the
building.). How long does it take to truly recover. Write it all down in
a disaster recovery plan.
HTH
Rick Sawtell|||Thank you for the input. I'm providing answers to the questions you posted.
Each of the 3 DB's are 2-3GB. Two of the three are core apps, all 40 users
are in one all day(Case management/contact management). The second is
accessed concurrently by no more than 10 users. The third is time and billin
g
which is accessed sporadically throughout the day. The hardware will
definitely be tier 1.
Do you think it is feasible to house 3 DBs of that size on one tier 1
server? As far as sizing, using the requirements of each application do we
double up or is there some basic formula we can reference to help with sizin
g
a server for this type of deployment.
Are there any other sources you think I should reference that would help?
Thanks again.
Rwbeck
"Rick Sawtell" wrote:

> "rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
> news:A7DC6DB7-2123-4F1B-B362-77DE287D1CF9@.microsoft.com...
> size
> same
> We
>
> How big are the databases? How much activity will be going on in those
> systems? How much activity in the front-end applications?
> Depending on what and how the front-end is developed, you may have many
> different points of "single point of failure".
> The best answer is to use Tier 1 hardware for your production environment.
> If it is small and fairly low in activity, then you can put it all on the
> same box. You should continually monitor your SQL Server's performance t
o
> ensure that everything is operating and playing well together. If the SQL
> Server is being starved for memory or CPU cycles etc., then you may want t
o
> start looking at a multi-box solution. It is all about balancing.
> Ensure that you have a good backup and RECOVERY strategy and PRACTICE it.
> Perform a sample disaster recovery, and I'm not just talking about restori
ng
> the database on the same server. Pretend you had a fire in the building a
nd
> have to rebuild a new server from scratch. Where is the s/w located for
> the O/S, SQL Server etc. Where are the backups of your current software
> packages that runs on this system. How will it connect to it's users
> (remember we had a "fire" in the building and lost everying in the
> building.). How long does it take to truly recover. Write it all down
in
> a disaster recovery plan.
> HTH
> Rick Sawtell
>
>|||"rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
news:9067FEAF-604C-41A8-83C4-33967AD48CD9@.microsoft.com...
> Thank you for the input. I'm providing answers to the questions you
posted.
> Each of the 3 DB's are 2-3GB. Two of the three are core apps, all 40 users
> are in one all day(Case management/contact management). The second is
> accessed concurrently by no more than 10 users. The third is time and
billing
> which is accessed sporadically throughout the day. The hardware will
> definitely be tier 1.
> Do you think it is feasible to house 3 DBs of that size on one tier 1
> server? As far as sizing, using the requirements of each application do we
> double up or is there some basic formula we can reference to help with
sizing
> a server for this type of deployment.
> Are there any other sources you think I should reference that would help?
> Thanks again.
> Rwbeck
>
Those databases are relatively small and if you are simply doing contact
management and case management, then I would say that those systems are very
lightweight. The billing application may see some activity if it is
performing calculations, or doing heavy reporting, but with so few users on
the system, I would not worry about this impacting performance much.
As far as sizing your server etc. there are many different books of SQL
Server Administration. Pick one that you like and read through it. Once
you have a good understanding of what SQL Server does behind the scenes you
will be able to make better choices. This website is a gold-mine of great
information http://www.sql-server-performance.com/ Check it out.
HTH
Rick Sawtell|||Really appreciate your help!
"Rick Sawtell" wrote:

> "rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
> news:9067FEAF-604C-41A8-83C4-33967AD48CD9@.microsoft.com...
> posted.
> billing
> sizing
> Those databases are relatively small and if you are simply doing contact
> management and case management, then I would say that those systems are ve
ry
> lightweight. The billing application may see some activity if it is
> performing calculations, or doing heavy reporting, but with so few users o
n
> the system, I would not worry about this impacting performance much.
> As far as sizing your server etc. there are many different books of SQL
> Server Administration. Pick one that you like and read through it. Onc
e
> you have a good understanding of what SQL Server does behind the scenes yo
u
> will be able to make better choices. This website is a gold-mine of grea
t
> information http://www.sql-server-performance.com/ Check it out.
> HTH
> Rick Sawtell
>
>

Newbie Question

I have 3 busines applications that will be porting to SQL server. Can I size
a SQL server to house the 3 databases and the associated programs on the same
box? Or should I put up a SQL box and have the apps on a seperate server? We
are a small company so the IT budget is small so I'm looking for the most
cost effective solution. But I'm also concerned about the single point of
failure this will create. Any suggestions would be appreciated.
Thanks,
rwbeck"rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
news:A7DC6DB7-2123-4F1B-B362-77DE287D1CF9@.microsoft.com...
> I have 3 busines applications that will be porting to SQL server. Can I
size
> a SQL server to house the 3 databases and the associated programs on the
same
> box? Or should I put up a SQL box and have the apps on a seperate server?
We
> are a small company so the IT budget is small so I'm looking for the most
> cost effective solution. But I'm also concerned about the single point of
> failure this will create. Any suggestions would be appreciated.
> Thanks,
> rwbeck
How big are the databases? How much activity will be going on in those
systems? How much activity in the front-end applications?
Depending on what and how the front-end is developed, you may have many
different points of "single point of failure".
The best answer is to use Tier 1 hardware for your production environment.
If it is small and fairly low in activity, then you can put it all on the
same box. You should continually monitor your SQL Server's performance to
ensure that everything is operating and playing well together. If the SQL
Server is being starved for memory or CPU cycles etc., then you may want to
start looking at a multi-box solution. It is all about balancing.
Ensure that you have a good backup and RECOVERY strategy and PRACTICE it.
Perform a sample disaster recovery, and I'm not just talking about restoring
the database on the same server. Pretend you had a fire in the building and
have to rebuild a new server from scratch. Where is the s/w located for
the O/S, SQL Server etc. Where are the backups of your current software
packages that runs on this system. How will it connect to it's users
(remember we had a "fire" in the building and lost everying in the
building.). How long does it take to truly recover. Write it all down in
a disaster recovery plan.
HTH
Rick Sawtell|||Thank you for the input. I'm providing answers to the questions you posted.
Each of the 3 DB's are 2-3GB. Two of the three are core apps, all 40 users
are in one all day(Case management/contact management). The second is
accessed concurrently by no more than 10 users. The third is time and billing
which is accessed sporadically throughout the day. The hardware will
definitely be tier 1.
Do you think it is feasible to house 3 DBs of that size on one tier 1
server? As far as sizing, using the requirements of each application do we
double up or is there some basic formula we can reference to help with sizing
a server for this type of deployment.
Are there any other sources you think I should reference that would help?
Thanks again.
Rwbeck
"Rick Sawtell" wrote:
> "rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
> news:A7DC6DB7-2123-4F1B-B362-77DE287D1CF9@.microsoft.com...
> > I have 3 busines applications that will be porting to SQL server. Can I
> size
> > a SQL server to house the 3 databases and the associated programs on the
> same
> > box? Or should I put up a SQL box and have the apps on a seperate server?
> We
> > are a small company so the IT budget is small so I'm looking for the most
> > cost effective solution. But I'm also concerned about the single point of
> > failure this will create. Any suggestions would be appreciated.
> > Thanks,
> >
> > rwbeck
>
> How big are the databases? How much activity will be going on in those
> systems? How much activity in the front-end applications?
> Depending on what and how the front-end is developed, you may have many
> different points of "single point of failure".
> The best answer is to use Tier 1 hardware for your production environment.
> If it is small and fairly low in activity, then you can put it all on the
> same box. You should continually monitor your SQL Server's performance to
> ensure that everything is operating and playing well together. If the SQL
> Server is being starved for memory or CPU cycles etc., then you may want to
> start looking at a multi-box solution. It is all about balancing.
> Ensure that you have a good backup and RECOVERY strategy and PRACTICE it.
> Perform a sample disaster recovery, and I'm not just talking about restoring
> the database on the same server. Pretend you had a fire in the building and
> have to rebuild a new server from scratch. Where is the s/w located for
> the O/S, SQL Server etc. Where are the backups of your current software
> packages that runs on this system. How will it connect to it's users
> (remember we had a "fire" in the building and lost everying in the
> building.). How long does it take to truly recover. Write it all down in
> a disaster recovery plan.
> HTH
> Rick Sawtell
>
>|||"rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
news:9067FEAF-604C-41A8-83C4-33967AD48CD9@.microsoft.com...
> Thank you for the input. I'm providing answers to the questions you
posted.
> Each of the 3 DB's are 2-3GB. Two of the three are core apps, all 40 users
> are in one all day(Case management/contact management). The second is
> accessed concurrently by no more than 10 users. The third is time and
billing
> which is accessed sporadically throughout the day. The hardware will
> definitely be tier 1.
> Do you think it is feasible to house 3 DBs of that size on one tier 1
> server? As far as sizing, using the requirements of each application do we
> double up or is there some basic formula we can reference to help with
sizing
> a server for this type of deployment.
> Are there any other sources you think I should reference that would help?
> Thanks again.
> Rwbeck
>
Those databases are relatively small and if you are simply doing contact
management and case management, then I would say that those systems are very
lightweight. The billing application may see some activity if it is
performing calculations, or doing heavy reporting, but with so few users on
the system, I would not worry about this impacting performance much.
As far as sizing your server etc. there are many different books of SQL
Server Administration. Pick one that you like and read through it. Once
you have a good understanding of what SQL Server does behind the scenes you
will be able to make better choices. This website is a gold-mine of great
information http://www.sql-server-performance.com/ Check it out.
HTH
Rick Sawtell|||Really appreciate your help!
"Rick Sawtell" wrote:
> "rwbeck" <rwbeck@.discussions.microsoft.com> wrote in message
> news:9067FEAF-604C-41A8-83C4-33967AD48CD9@.microsoft.com...
> > Thank you for the input. I'm providing answers to the questions you
> posted.
> >
> > Each of the 3 DB's are 2-3GB. Two of the three are core apps, all 40 users
> > are in one all day(Case management/contact management). The second is
> > accessed concurrently by no more than 10 users. The third is time and
> billing
> > which is accessed sporadically throughout the day. The hardware will
> > definitely be tier 1.
> >
> > Do you think it is feasible to house 3 DBs of that size on one tier 1
> > server? As far as sizing, using the requirements of each application do we
> > double up or is there some basic formula we can reference to help with
> sizing
> > a server for this type of deployment.
> >
> > Are there any other sources you think I should reference that would help?
> >
> > Thanks again.
> > Rwbeck
> >
> Those databases are relatively small and if you are simply doing contact
> management and case management, then I would say that those systems are very
> lightweight. The billing application may see some activity if it is
> performing calculations, or doing heavy reporting, but with so few users on
> the system, I would not worry about this impacting performance much.
> As far as sizing your server etc. there are many different books of SQL
> Server Administration. Pick one that you like and read through it. Once
> you have a good understanding of what SQL Server does behind the scenes you
> will be able to make better choices. This website is a gold-mine of great
> information http://www.sql-server-performance.com/ Check it out.
> HTH
> Rick Sawtell
>
>

Newbie needs to be told where to go! (Cross-Post)

Greetings:
I've been developing web applications with asp/sql and access for some
time now on existing servers. I am now in a situation that requires me to
install SQL Server (SBS 2K sp3) as the backend for an intranet served from
IIS. I've installed the SQL services and have created the database and I
have some of the web based application written, no problem, but I've yet to
be able to access the database that I created on the newly installed SQL
server from the web based applications. Even after setting up the virtual
directory with the IIS SQL snap-in, I only get a DNS Server not found error
when I try to browse the site. If I remove the IIS/SQL virtual directory, I
can browse pages that don't error out due to data references.
Where can I find a walk through for setting up SQL Server and IIS to
function together in this very basic manner?
Thanks in advance.
--
Jerry M. Gartner
www.gartnerwebdev.comHi,
Have a look at these...
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;176378
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;176380
http://support.microsoft.com/default.aspx?scid=kb;zh-
cn;chs264921
http://support.microsoft.com/default.aspx?scid=kb;PL;264921
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;245243
>--Original Message--
>Greetings:
> I've been developing web applications with asp/sql
and access for some
>time now on existing servers. I am now in a situation
that requires me to
>install SQL Server (SBS 2K sp3) as the backend for an
intranet served from
>IIS. I've installed the SQL services and have created
the database and I
>have some of the web based application written, no
problem, but I've yet to
>be able to access the database that I created on the
newly installed SQL
>server from the web based applications. Even after
setting up the virtual
>directory with the IIS SQL snap-in, I only get a DNS
Server not found error
>when I try to browse the site. If I remove the IIS/SQL
virtual directory, I
>can browse pages that don't error out due to data
references.
> Where can I find a walk through for setting up SQL
Server and IIS to
>function together in this very basic manner?
>Thanks in advance.
>
>--
>Jerry M. Gartner
>www.gartnerwebdev.com
>
>.
>|||Peter:
Preliminarily, this appears to be what I'm looking for. I didn't think
to use ODBC and a DSN. What are the major differences between ODBC and
"direct" connection? There will be under 30 clients using the DB - this is
an on demand intranet application and will be hit lightly and sporadically
throughout the day. The SQL server is also the PDC and fileserver/DFS root
and gateway. (2K SP4)
--
Jerry M. Gartner
www.gartnerwebdev.com
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:03de01c3a83a$14ef9140$a001280a@.phx.gbl...
> Hi,
> Have a look at these...
> http://support.microsoft.com/default.aspx?scid=kb;EN-
> US;176378
> http://support.microsoft.com/default.aspx?scid=kb;EN-
> US;176380
> http://support.microsoft.com/default.aspx?scid=kb;zh-
> cn;chs264921
> http://support.microsoft.com/default.aspx?scid=kb;PL;264921
> http://support.microsoft.com/default.aspx?scid=kb;EN-
> US;245243

Newbie - What do I need

Hi All
At work we use SQL server to host all our databases. I develop web applications but don't do the SQL maintenance but do build db (my dba checks everything and sets all the permissions, etc). Anyway, a nonprofit has asked me to build them a web applicati
on to collect and display information nothing too fancy but lots of data and lot of users.
What are my options? Do I have to buy the server version if I just want to build a database but it is going to be collecting and serving the information from our web host (they've agreed to the extra cost for a web host providing SQL), we aren't keeping
a local version of the records. So I just need SQL to build the db and upload it to our web host. My dba said try access but it only allows 5 concurrent connections. I've heard of MySql or something but since I am somewhat familiar with the basics of
SQL was hoping there was some option for me. They don't need to do analysis or use the info other than to display it on web pages. They estimate they have 5,000 - 10,000 users who will enter 10 to 20 records each including photos.
I appreciate any recommendations or advice you could provide.
Thanks!!
"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> Hi All
> At work we use SQL server to host all our databases. I develop web
applications but don't do the SQL maintenance but do build db (my dba checks
everything and sets all the permissions, etc). Anyway, a nonprofit has
asked me to build them a web application to collect and display information
nothing too fancy but lots of data and lot of users.
> What are my options? Do I have to buy the server version if I just want
to build a database but it is going to be collecting and serving the
information from our web host (they've agreed to the extra cost for a web
host providing SQL), we aren't keeping a local version of the records. So I
just need SQL to build the db and upload it to our web host. My dba said
try access but it only allows 5 concurrent connections. I've heard of MySql
or something but since I am somewhat familiar with the basics of SQL was
hoping there was some option for me. They don't need to do analysis or use
the info other than to display it on web pages. They estimate they have
5,000 - 10,000 users who will enter 10 to 20 records each including photos.
> I appreciate any recommendations or advice you could provide.
> Thanks!!
MSDE is free and is SQLServer. It comes free with many products including
the free ASP.NET web matrix.
http://www.asp.net/
You can buy a $50 copy of SQL Server developer edition.
http://www.microsoft.com/sql/howtobuy/development.asp
To get a copy of SQL Enterprise Manager and the rest of the tools.
David
|||Hi David
So if I bought the developer edition I would be legal to build the database and upload it to our web hosting server?
I purchased visual studio.net so I don't have matrix. Would you recommend I go that way using MSDN or the developer edition?
Thanks for the FAST feedback!!
Tracie
"David Browne" wrote:

> "Tracie" <Tracie@.discussions.microsoft.com> wrote in message
> news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> applications but don't do the SQL maintenance but do build db (my dba checks
> everything and sets all the permissions, etc). Anyway, a nonprofit has
> asked me to build them a web application to collect and display information
> nothing too fancy but lots of data and lot of users.
> to build a database but it is going to be collecting and serving the
> information from our web host (they've agreed to the extra cost for a web
> host providing SQL), we aren't keeping a local version of the records. So I
> just need SQL to build the db and upload it to our web host. My dba said
> try access but it only allows 5 concurrent connections. I've heard of MySql
> or something but since I am somewhat familiar with the basics of SQL was
> hoping there was some option for me. They don't need to do analysis or use
> the info other than to display it on web pages. They estimate they have
> 5,000 - 10,000 users who will enter 10 to 20 records each including photos.
> MSDE is free and is SQLServer. It comes free with many products including
> the free ASP.NET web matrix.
> http://www.asp.net/
> You can buy a $50 copy of SQL Server developer edition.
> http://www.microsoft.com/sql/howtobuy/development.asp
> To get a copy of SQL Enterprise Manager and the rest of the tools.
> David
>
>
|||If your company has SQL, and you have a client license, then you can load
the personal edition (from the company CD) to your desktop dev
environment...
(If it were me, I'd get the non-profit to purchase you the Development
Edition, that you keep, for the $50)... It is a great great price, (just
reduced from $500)..
Have fun!...This may the start of a great new thing for you!
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> Hi All
> At work we use SQL server to host all our databases. I develop web
applications but don't do the SQL maintenance but do build db (my dba checks
everything and sets all the permissions, etc). Anyway, a nonprofit has
asked me to build them a web application to collect and display information
nothing too fancy but lots of data and lot of users.
> What are my options? Do I have to buy the server version if I just want
to build a database but it is going to be collecting and serving the
information from our web host (they've agreed to the extra cost for a web
host providing SQL), we aren't keeping a local version of the records. So I
just need SQL to build the db and upload it to our web host. My dba said
try access but it only allows 5 concurrent connections. I've heard of MySql
or something but since I am somewhat familiar with the basics of SQL was
hoping there was some option for me. They don't need to do analysis or use
the info other than to display it on web pages. They estimate they have
5,000 - 10,000 users who will enter 10 to 20 records each including photos.
> I appreciate any recommendations or advice you could provide.
> Thanks!!
|||"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:5EE69FF4-4DFF-4DB0-982B-EF3C5BA28896@.microsoft.com...
> Hi David
> So if I bought the developer edition I would be legal to build the
database and upload it to our web hosting server?
The hosting server must have Sql server or MSDE on it.

> I purchased visual studio.net so I don't have matrix. Would you recommend
I go that way using MSDN or the >developer edition?
MSDE comes with visual studio so you have it. In fact you can just download
it now.
http://www.microsoft.com/sql/msde/do...s/download.asp
David

Newbie - What do I need

Hi All
At work we use SQL server to host all our databases. I develop web applications but don't do the SQL maintenance but do build db (my dba checks everything and sets all the permissions, etc). Anyway, a nonprofit has asked me to build them a web application to collect and display information nothing too fancy but lots of data and lot of users.
What are my options? Do I have to buy the server version if I just want to build a database but it is going to be collecting and serving the information from our web host (they've agreed to the extra cost for a web host providing SQL), we aren't keeping a local version of the records. So I just need SQL to build the db and upload it to our web host. My dba said try access but it only allows 5 concurrent connections. I've heard of MySql or something but since I am somewhat familiar with the basics of SQL was hoping there was some option for me. They don't need to do analysis or use the info other than to display it on web pages. They estimate they have 5,000 - 10,000 users who will enter 10 to 20 records each including photos.
I appreciate any recommendations or advice you could provide.
Thanks!!"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> Hi All
> At work we use SQL server to host all our databases. I develop web
applications but don't do the SQL maintenance but do build db (my dba checks
everything and sets all the permissions, etc). Anyway, a nonprofit has
asked me to build them a web application to collect and display information
nothing too fancy but lots of data and lot of users.
> What are my options? Do I have to buy the server version if I just want
to build a database but it is going to be collecting and serving the
information from our web host (they've agreed to the extra cost for a web
host providing SQL), we aren't keeping a local version of the records. So I
just need SQL to build the db and upload it to our web host. My dba said
try access but it only allows 5 concurrent connections. I've heard of MySql
or something but since I am somewhat familiar with the basics of SQL was
hoping there was some option for me. They don't need to do analysis or use
the info other than to display it on web pages. They estimate they have
5,000 - 10,000 users who will enter 10 to 20 records each including photos.
> I appreciate any recommendations or advice you could provide.
> Thanks!!
MSDE is free and is SQLServer. It comes free with many products including
the free ASP.NET web matrix.
http://www.asp.net/
You can buy a $50 copy of SQL Server developer edition.
http://www.microsoft.com/sql/howtobuy/development.asp
To get a copy of SQL Enterprise Manager and the rest of the tools.
David|||Hi David
So if I bought the developer edition I would be legal to build the database and upload it to our web hosting server?
I purchased visual studio.net so I don't have matrix. Would you recommend I go that way using MSDN or the developer edition?
Thanks for the FAST feedback!!
Tracie
"David Browne" wrote:
> "Tracie" <Tracie@.discussions.microsoft.com> wrote in message
> news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> > Hi All
> > At work we use SQL server to host all our databases. I develop web
> applications but don't do the SQL maintenance but do build db (my dba checks
> everything and sets all the permissions, etc). Anyway, a nonprofit has
> asked me to build them a web application to collect and display information
> nothing too fancy but lots of data and lot of users.
> > What are my options? Do I have to buy the server version if I just want
> to build a database but it is going to be collecting and serving the
> information from our web host (they've agreed to the extra cost for a web
> host providing SQL), we aren't keeping a local version of the records. So I
> just need SQL to build the db and upload it to our web host. My dba said
> try access but it only allows 5 concurrent connections. I've heard of MySql
> or something but since I am somewhat familiar with the basics of SQL was
> hoping there was some option for me. They don't need to do analysis or use
> the info other than to display it on web pages. They estimate they have
> 5,000 - 10,000 users who will enter 10 to 20 records each including photos.
> > I appreciate any recommendations or advice you could provide.
> > Thanks!!
> MSDE is free and is SQLServer. It comes free with many products including
> the free ASP.NET web matrix.
> http://www.asp.net/
> You can buy a $50 copy of SQL Server developer edition.
> http://www.microsoft.com/sql/howtobuy/development.asp
> To get a copy of SQL Enterprise Manager and the rest of the tools.
> David
>
>|||If your company has SQL, and you have a client license, then you can load
the personal edition (from the company CD) to your desktop dev
environment...
(If it were me, I'd get the non-profit to purchase you the Development
Edition, that you keep, for the $50)... It is a great great price, (just
reduced from $500)..
Have fun!...This may the start of a great new thing for you!
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> Hi All
> At work we use SQL server to host all our databases. I develop web
applications but don't do the SQL maintenance but do build db (my dba checks
everything and sets all the permissions, etc). Anyway, a nonprofit has
asked me to build them a web application to collect and display information
nothing too fancy but lots of data and lot of users.
> What are my options? Do I have to buy the server version if I just want
to build a database but it is going to be collecting and serving the
information from our web host (they've agreed to the extra cost for a web
host providing SQL), we aren't keeping a local version of the records. So I
just need SQL to build the db and upload it to our web host. My dba said
try access but it only allows 5 concurrent connections. I've heard of MySql
or something but since I am somewhat familiar with the basics of SQL was
hoping there was some option for me. They don't need to do analysis or use
the info other than to display it on web pages. They estimate they have
5,000 - 10,000 users who will enter 10 to 20 records each including photos.
> I appreciate any recommendations or advice you could provide.
> Thanks!!|||"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:5EE69FF4-4DFF-4DB0-982B-EF3C5BA28896@.microsoft.com...
> Hi David
> So if I bought the developer edition I would be legal to build the
database and upload it to our web hosting server?
The hosting server must have Sql server or MSDE on it.
> I purchased visual studio.net so I don't have matrix. Would you recommend
I go that way using MSDN or the >developer edition?
MSDE comes with visual studio so you have it. In fact you can just download
it now.
http://www.microsoft.com/sql/msde/downloads/download.asp
David

Newbie - What do I need

Hi All
At work we use SQL server to host all our databases. I develop web applicat
ions but don't do the SQL maintenance but do build db (my dba checks everyth
ing and sets all the permissions, etc). Anyway, a nonprofit has asked me to
build them a web applicati
on to collect and display information nothing too fancy but lots of data and
lot of users.
What are my options? Do I have to buy the server version if I just want to
build a database but it is going to be collecting and serving the informatio
n from our web host (they've agreed to the extra cost for a web host providi
ng SQL), we aren't keeping
a local version of the records. So I just need SQL to build the db and uplo
ad it to our web host. My dba said try access but it only allows 5 concurr
ent connections. I've heard of mysql or something but since I am somewhat f
amiliar with the basics of
SQL was hoping there was some option for me. They don't need to do analysis
or use the info other than to display it on web pages. They estimate they
have 5,000 - 10,000 users who will enter 10 to 20 records each including pho
tos.
I appreciate any recommendations or advice you could provide.
Thanks!!"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> Hi All
> At work we use SQL server to host all our databases. I develop web
applications but don't do the SQL maintenance but do build db (my dba checks
everything and sets all the permissions, etc). Anyway, a nonprofit has
asked me to build them a web application to collect and display information
nothing too fancy but lots of data and lot of users.
> What are my options? Do I have to buy the server version if I just want
to build a database but it is going to be collecting and serving the
information from our web host (they've agreed to the extra cost for a web
host providing SQL), we aren't keeping a local version of the records. So I
just need SQL to build the db and upload it to our web host. My dba said
try access but it only allows 5 concurrent connections. I've heard of MySql
or something but since I am somewhat familiar with the basics of SQL was
hoping there was some option for me. They don't need to do analysis or use
the info other than to display it on web pages. They estimate they have
5,000 - 10,000 users who will enter 10 to 20 records each including photos.
> I appreciate any recommendations or advice you could provide.
> Thanks!!
MSDE is free and is SQLServer. It comes free with many products including
the free ASP.NET web matrix.
http://www.asp.net/
You can buy a $50 copy of SQL Server developer edition.
http://www.microsoft.com/sql/howtobuy/development.asp
To get a copy of SQL Enterprise Manager and the rest of the tools.
David|||Hi David
So if I bought the developer edition I would be legal to build the database
and upload it to our web hosting server?
I purchased visual studio.net so I don't have matrix. Would you recommend I
go that way using MSDN or the developer edition?
Thanks for the FAST feedback!!
Tracie
"David Browne" wrote:

> "Tracie" <Tracie@.discussions.microsoft.com> wrote in message
> news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> applications but don't do the SQL maintenance but do build db (my dba chec
ks
> everything and sets all the permissions, etc). Anyway, a nonprofit has
> asked me to build them a web application to collect and display informatio
n
> nothing too fancy but lots of data and lot of users.
> to build a database but it is going to be collecting and serving the
> information from our web host (they've agreed to the extra cost for a web
> host providing SQL), we aren't keeping a local version of the records. So
I
> just need SQL to build the db and upload it to our web host. My dba said
> try access but it only allows 5 concurrent connections. I've heard of MyS
ql
> or something but since I am somewhat familiar with the basics of SQL was
> hoping there was some option for me. They don't need to do analysis or us
e
> the info other than to display it on web pages. They estimate they have
> 5,000 - 10,000 users who will enter 10 to 20 records each including photos
.
> MSDE is free and is SQLServer. It comes free with many products including
> the free ASP.NET web matrix.
> http://www.asp.net/
> You can buy a $50 copy of SQL Server developer edition.
> http://www.microsoft.com/sql/howtobuy/development.asp
> To get a copy of SQL Enterprise Manager and the rest of the tools.
> David
>
>|||If your company has SQL, and you have a client license, then you can load
the personal edition (from the company CD) to your desktop dev
environment...
(If it were me, I'd get the non-profit to purchase you the Development
Edition, that you keep, for the $50)... It is a great great price, (just
reduced from $500)..
Have fun!...This may the start of a great new thing for you!
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:BAA314D3-FC30-4808-A27F-8C74BAAB6185@.microsoft.com...
> Hi All
> At work we use SQL server to host all our databases. I develop web
applications but don't do the SQL maintenance but do build db (my dba checks
everything and sets all the permissions, etc). Anyway, a nonprofit has
asked me to build them a web application to collect and display information
nothing too fancy but lots of data and lot of users.
> What are my options? Do I have to buy the server version if I just want
to build a database but it is going to be collecting and serving the
information from our web host (they've agreed to the extra cost for a web
host providing SQL), we aren't keeping a local version of the records. So I
just need SQL to build the db and upload it to our web host. My dba said
try access but it only allows 5 concurrent connections. I've heard of MySql
or something but since I am somewhat familiar with the basics of SQL was
hoping there was some option for me. They don't need to do analysis or use
the info other than to display it on web pages. They estimate they have
5,000 - 10,000 users who will enter 10 to 20 records each including photos.
> I appreciate any recommendations or advice you could provide.
> Thanks!!|||"Tracie" <Tracie@.discussions.microsoft.com> wrote in message
news:5EE69FF4-4DFF-4DB0-982B-EF3C5BA28896@.microsoft.com...
> Hi David
> So if I bought the developer edition I would be legal to build the
database and upload it to our web hosting server?
The hosting server must have Sql server or MSDE on it.

> I purchased visual studio.net so I don't have matrix. Would you recommend
I go that way using MSDN or the >developer edition?
MSDE comes with visual studio so you have it. In fact you can just download
it now.
http://www.microsoft.com/sql/msde/d...ds/download.asp
David