We are going to deploy a SQL Server 2000 for an
application which information is static. We just provide
queries for end users.
In order to minimize the backup procedure, we would like
to use RAID 1 mirroring configuration. Is this choice OK ?Your backup procedure has nothing to do with your choice of RAID
configuration (unless I'm missing something here). Performance and
Redundancy has.
Aramid
On Wed, 6 Apr 2005 22:50:08 -0700, "Peter"
<anonymous@.discussions.microsoft.com> wrote:
>We are going to deploy a SQL Server 2000 for an
>application which information is static. We just provide
>queries for end users.
>In order to minimize the backup procedure, we would like
>to use RAID 1 mirroring configuration. Is this choice OK ?|||We will make a backup of whole drive once a week as the
data is static.
The reason why we think RAID 1 is because we think that if
one of the disk breaks down, the other one still works
properly.
Re the performance issue, we would like to know what is
the pros and cons of RAID 1.
Thanks
>--Original Message--
>Your backup procedure has nothing to do with your choice
of RAID
>configuration (unless I'm missing something here).
Performance and
>Redundancy has.
>Aramid
>On Wed, 6 Apr 2005 22:50:08 -0700, "Peter"
><anonymous@.discussions.microsoft.com> wrote:
>>We are going to deploy a SQL Server 2000 for an
>>application which information is static. We just
provide
>>queries for end users.
>>In order to minimize the backup procedure, we would like
>>to use RAID 1 mirroring configuration. Is this choice
OK ?
>.
>|||Hi
The more spindles you have, the better your performance.
RAID-1 is good for performance and tolerance to failure, but RAID-10 (Or
0+1) is much better as it is striped and mirrored. So, you have the benefit
of Mirroring, plus you have multiple drives doing requests at the same time.
SCSI, not IDE or SATA.
Hardware mirroring, not software.
RAID-5 is evil, don't go there.
SQL Serrver does it's IO in 64k blocks (8 extents of 8k pages), so format
NTFS using 64Kb blocks.
Regards
Mike
"Peter" wrote:
> We will make a backup of whole drive once a week as the
> data is static.
> The reason why we think RAID 1 is because we think that if
> one of the disk breaks down, the other one still works
> properly.
> Re the performance issue, we would like to know what is
> the pros and cons of RAID 1.
> Thanks
> >--Original Message--
> >Your backup procedure has nothing to do with your choice
> of RAID
> >configuration (unless I'm missing something here).
> Performance and
> >Redundancy has.
> >
> >Aramid
> >
> >On Wed, 6 Apr 2005 22:50:08 -0700, "Peter"
> ><anonymous@.discussions.microsoft.com> wrote:
> >
> >>We are going to deploy a SQL Server 2000 for an
> >>application which information is static. We just
> provide
> >>queries for end users.
> >>
> >>In order to minimize the backup procedure, we would like
> >>to use RAID 1 mirroring configuration. Is this choice
> OK ?
> >
> >.
> >
>
Showing posts with label provide. Show all posts
Showing posts with label provide. Show all posts
Monday, March 26, 2012
Radiobutton List from SQL Server Table
Hi! There must be a very simple answer to this question, but it's my first venture into using SQL Server data.
I've set up an ASP.NET site to provide for on-line sign-up of events. The site has a masterpage and utilizes a wizard to create an e-mail to request sign-up for an event.
I'd like to make my radiobuttonlist dynamic so that events past the signup deadline will not be displayed. So, I've created a database table that includes two fields: event_description and event_date – such that the radiobuttonlist will only show those events that are at least three days beyond today's date.
I've configured the data source and the radiobuttonlist so that I can display all the entries in the event table, but I can't figure out how to restrict them to today + 3 events only.
I'm guessing my problem is in the "Add Where Clause" of the "Configure Data Source" wizard. I'm sure the "Column" should be set to event_date and the "Operator" should be set to ">", but what should I set the "Source" & "Parameter Properties" to? I've set a variable in my program as "Dim deadline As Date = Today.AddDays(3)", but the wizard doesn't seem to see it.
Can anyone steer me in the right direction?
Try this for your where clause:
WHERE
(event_date>DATEADD(Day, 3,GETDATE()))|||
limno:
Try this for your where clause:
WHERE
(event_date>DATEADD(Day, 3,GETDATE()))
Limno,
Thanks, works like a "champ!"
From your profile, I see you're from Iowa. ...Go 'Clones!
...Jerry
|||Hi Jerry:
I should add Ames to my profile. Have a nice day.
Wednesday, March 7, 2012
Quick Question
Are there any alternatives to 15 if...else...statements in SQL Server
Programming. If so do they scale better and/or provide performance gains?
Thx
MarcMost likely, but it is a bit hard to come up with a solution unless you
provide us with some more specifics of your problem. (See
www.apsfaq.com/5006)
Jacco Schalkwijk
SQL Server MVP
"marcmc" <marcmc@.discussions.microsoft.com> wrote in message
news:8C3457C2-7FA1-454E-B2B0-4F9D4DB0A7DC@.microsoft.com...
> Are there any alternatives to 15 if...else...statements in SQL Server
> Programming. If so do they scale better and/or provide performance gains?
> Thx
> Marc|||it's hypothethical.
I know I will have this problem in a few months and was hoping to guide
myself to a better/different solution.
say for example ages if you are 20 do something, if you are 25 do something
etc etc.
I know the answer is probably the CASE Stmt which is fine but is it hot on
performance?|||Hi
You can use CASE structure if you want.
best Regards,
Chandra
http://chanduas.blogspot.com/
---
*** Sent via Developersdex http://www.examnotes.net ***|||CASE most likely performs better than doing a number of IF...ELSEs. But in
the end the finer details of performance all depends on your particular
problem and data.
Jacco Schalkwijk
SQL Server MVP
"marcmc" <marcmc@.discussions.microsoft.com> wrote in message
news:66F90280-5A66-49C1-95BF-BCFA50741A60@.microsoft.com...
> it's hypothethical.
> I know I will have this problem in a few months and was hoping to guide
> myself to a better/different solution.
> say for example ages if you are 20 do something, if you are 25 do
> something
> etc etc.
> I know the answer is probably the CASE Stmt which is fine but is it hot on
> performance?|||Hi
Another option may be a lookup table.
As Itzik says "Think outside the box"
John
"marcmc" wrote:
> it's hypothethical.
> I know I will have this problem in a few months and was hoping to guide
> myself to a better/different solution.
> say for example ages if you are 20 do something, if you are 25 do somethin
g
> etc etc.
> I know the answer is probably the CASE Stmt which is fine but is it hot on
> performance?|||You can use the Case statement which can help when breaking down your age
example. Take a look at the following example:
SELECT title, price,
Budget = CASE price
WHEN price > 20.00 THEN 'Expensive'
WHEN price BETWEEN 10.00 AND 19.99 THEN 'Moderate'
WHEN price < 10.00 THEN 'Inexpensive'
ELSE 'Unknown'
END,
FROM titles
CASE expressions bring a vast degree of power and control to SQL Server
programmers. A working knowledge of CASE expressions can make accessing and
updating SQL Server data easier and perhaps, even more efficient.
Additionally, CASE expressions enable more work to be accomplished using a
single SQL statement, which should also improve efficiency and decrease
development time. As such, CASE expressions should be a component of every
SQL Server developer’s arsenal of programming techniques.
For more information go here which gives some good simplistic examples.
http://www.craigsmullins.com/ssu_0899.htm
"marcmc" wrote:
> Are there any alternatives to 15 if...else...statements in SQL Server
> Programming. If so do they scale better and/or provide performance gains?
> Thx
> Marc|||You are really going to have to give more information. Like what do you
mean by "do something" Case is an scalar expression, so you cannot use is
as a flow control mechanism. If you mean using it like a switch case in VB,
to replace if...else constructs then T-SQL is pretty weak that way, though
it isn't meant not to be.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"marcmc" <marcmc@.discussions.microsoft.com> wrote in message
news:66F90280-5A66-49C1-95BF-BCFA50741A60@.microsoft.com...
> it's hypothethical.
> I know I will have this problem in a few months and was hoping to guide
> myself to a better/different solution.
> say for example ages if you are 20 do something, if you are 25 do
> something
> etc etc.
> I know the answer is probably the CASE Stmt which is fine but is it hot on
> performance?
Programming. If so do they scale better and/or provide performance gains?
Thx
MarcMost likely, but it is a bit hard to come up with a solution unless you
provide us with some more specifics of your problem. (See
www.apsfaq.com/5006)
Jacco Schalkwijk
SQL Server MVP
"marcmc" <marcmc@.discussions.microsoft.com> wrote in message
news:8C3457C2-7FA1-454E-B2B0-4F9D4DB0A7DC@.microsoft.com...
> Are there any alternatives to 15 if...else...statements in SQL Server
> Programming. If so do they scale better and/or provide performance gains?
> Thx
> Marc|||it's hypothethical.
I know I will have this problem in a few months and was hoping to guide
myself to a better/different solution.
say for example ages if you are 20 do something, if you are 25 do something
etc etc.
I know the answer is probably the CASE Stmt which is fine but is it hot on
performance?|||Hi
You can use CASE structure if you want.
best Regards,
Chandra
http://chanduas.blogspot.com/
---
*** Sent via Developersdex http://www.examnotes.net ***|||CASE most likely performs better than doing a number of IF...ELSEs. But in
the end the finer details of performance all depends on your particular
problem and data.
Jacco Schalkwijk
SQL Server MVP
"marcmc" <marcmc@.discussions.microsoft.com> wrote in message
news:66F90280-5A66-49C1-95BF-BCFA50741A60@.microsoft.com...
> it's hypothethical.
> I know I will have this problem in a few months and was hoping to guide
> myself to a better/different solution.
> say for example ages if you are 20 do something, if you are 25 do
> something
> etc etc.
> I know the answer is probably the CASE Stmt which is fine but is it hot on
> performance?|||Hi
Another option may be a lookup table.
As Itzik says "Think outside the box"
John
"marcmc" wrote:
> it's hypothethical.
> I know I will have this problem in a few months and was hoping to guide
> myself to a better/different solution.
> say for example ages if you are 20 do something, if you are 25 do somethin
g
> etc etc.
> I know the answer is probably the CASE Stmt which is fine but is it hot on
> performance?|||You can use the Case statement which can help when breaking down your age
example. Take a look at the following example:
SELECT title, price,
Budget = CASE price
WHEN price > 20.00 THEN 'Expensive'
WHEN price BETWEEN 10.00 AND 19.99 THEN 'Moderate'
WHEN price < 10.00 THEN 'Inexpensive'
ELSE 'Unknown'
END,
FROM titles
CASE expressions bring a vast degree of power and control to SQL Server
programmers. A working knowledge of CASE expressions can make accessing and
updating SQL Server data easier and perhaps, even more efficient.
Additionally, CASE expressions enable more work to be accomplished using a
single SQL statement, which should also improve efficiency and decrease
development time. As such, CASE expressions should be a component of every
SQL Server developer’s arsenal of programming techniques.
For more information go here which gives some good simplistic examples.
http://www.craigsmullins.com/ssu_0899.htm
"marcmc" wrote:
> Are there any alternatives to 15 if...else...statements in SQL Server
> Programming. If so do they scale better and/or provide performance gains?
> Thx
> Marc|||You are really going to have to give more information. Like what do you
mean by "do something" Case is an scalar expression, so you cannot use is
as a flow control mechanism. If you mean using it like a switch case in VB,
to replace if...else constructs then T-SQL is pretty weak that way, though
it isn't meant not to be.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"marcmc" <marcmc@.discussions.microsoft.com> wrote in message
news:66F90280-5A66-49C1-95BF-BCFA50741A60@.microsoft.com...
> it's hypothethical.
> I know I will have this problem in a few months and was hoping to guide
> myself to a better/different solution.
> say for example ages if you are 20 do something, if you are 25 do
> something
> etc etc.
> I know the answer is probably the CASE Stmt which is fine but is it hot on
> performance?
Subscribe to:
Posts (Atom)