MS SQL/ADP loses records

anyone have this problem? it was reported to me that the records entered over the past 4 weeks are gone. i checked for rights and any sp's that would delete.
they just disappeared? thanks.

Quote:

Originally Posted by jf951

anyone have this problem? it was reported to me that the records entered over the past 4 weeks are gone. i checked for rights and any sp's that would delete.
they just disappeared? thanks.

Your question has been moved into the MS SQL forum.|||

Quote:

Originally Posted by jf951

anyone have this problem? it was reported to me that the records entered over the past 4 weeks are gone. i checked for rights and any sp's that would delete.
they just disappeared? thanks.

Hi there,

It sounds a little weird to me, anyway, by any chance did you or anyone else might have accidently restored old database? Well, this is what i can think of at this time, please check this out. Good luck & Take care.

MS SQL Server 2000 - Search a table with 300,000+ records in less then a second or two

I have one table with 300,000 records and 30 columns.
For example columns are ID, COMPANY, PhONE, NOTES ...
ID - nvarchar length-9
COMPANY - nvarchar length-30
NOTES - nvarchar length-250
Select * from database
where NOTES like '%something%'
Is there a way to get results from this query in less then 1-2 second
and how?
Maybe. If possible begin the % with a leading character and try creating a
NC index on the NOTES column. Or might also consider creating a Full-Text
index on the NOTES column and then use CONTAINS or FREETEXT.
HTH
Jerry
"nywebmaster" <scgwebmaster@.yahoo.com> wrote in message
news:1129306144.751022.186010@.o13g2000cwo.googlegr oups.com...
>
> I have one table with 300,000 records and 30 columns.
> For example columns are ID, COMPANY, PhONE, NOTES ...
> ID - nvarchar length-9
> COMPANY - nvarchar length-30
> NOTES - nvarchar length-250
> ----
> Select * from database
> where NOTES like '%something%'
> Is there a way to get results from this query in less then 1-2 second
> and how?
>
|||Thanks.

MS SQL Server 2000 - Search a table with 300,000+ records in less then a second or two

I have one table with 300,000 records and 30 columns.
For example columns are ID, COMPANY, PhONE, NOTES ...
ID - nvarchar lenth-9
COMPANY - nvarchar lenth-30
NOTES - nvarchar length-250

Select * from database
where NOTES like '%something%'

Is there a way to get results from this query in less then 1-2 second
and how?Hello
I think that using like it would be impossible.
You will get better results when you use full text search (read about it in
books online), however I have not experience with looking for a phrase, but
with single words it works fast.
Alwik

> I have one table with 300,000 records and 30 columns.
> For example columns are ID, COMPANY, PhONE, NOTES ...
> ID - nvarchar lenth-9
> COMPANY - nvarchar lenth-30
> NOTES - nvarchar length-250
> Select * from database
> where NOTES like '%something%'
> Is there a way to get results from this query in less then 1-2 second
> and how?|||On a Athon3200+ (32 bits) home computer
it takes 1692ms to search something like '%RRIDA%' on 393951 rows
table. The maximum length of a row is 3576 bytes. So you only need a
faster CPU and faster memory controler and enough memory to hold the
data pages in memory to achive subsecond time. But IMHO I think this
kind of search is a nonsense for this number of rows.|||So what kind of search are you recommend?|||Am 14 Oct 2005 12:33:10 -0700 schrieb nydefender:

> So what kind of search are you recommend?

What hardware do you use? And how long does it last to get the result? Have
you tried it with an index on NOTES? And i think, a second search should be
much faster then the first one. If you always search on NOTES maybe you can
hold a second table with only PK and field NOTES, which is redundant
(managed by triggers) but can be pinned into memory (DBCC PINTABLE() -
maybe a silly idea, only brainstorming).
Sometimes i have the same problem to find some records out of a big table
where it lasts up to 30 seconds. At first the user knows from
training/docu, that this could need a "long" time to proceed, second i show
a window with a wait-message and something blinking in it, so the user has
not the feeling that the program hangs.

bye,
Helmut|||helmut woess (hw@.iis.at) writes:
> (managed by triggers) but can be pinned into memory (DBCC PINTABLE() -
> maybe a silly idea, only brainstorming).

Yes, DBCC PINTABLE was really a silly idea of Microsoft/Sybase. (Don't
really know who came up with it.) So silly, that in fact in SQL 2005, the
command DBCC PINTABLE is a no-op that performs nothing.

If a table is referenced often enough, it will be in cache anyway, so
PINTABLE has no effect. But if you pin a large table of which only portions
are referenced with some frequency, this means that you are wasting memory
that could have been used for other table, and thus degrade performance.

The only point I can see with PINTABLE is that you have table that you
query so rarely, that it will fall out of the cache. But when you need to
query it, you need the answers snap.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||You want subsecond performance for your query. And the query can return
thousands of rows. How many time the clerk will spend searching for the
correct row?. subsecond querys are needed for routine operations and
they return only the necessary information to do the task, if not, the
worker is wasting his time. When you look for %something%, do you
really know what you are looking for?

In an hospitalizaton patient table, if I look for %seropositive% in the
observations field or even for %positive% I'm pretty sure its for a
report or an adhoc decission suport query and this doesn't need
subsecond response time. SQL Server is an OLTP system, designed for a
lot of small transactions, and this kind of queries is an incorrect use
of the system in my opinion.

You sould use something like Microsoft Search Service or a similar
product.|||Maybe this kind of query is "incorect" but is necessary. Now this query
takes for about 15-20 secs. I try to find a better way. I will try with
full text search.
Thanks to all of you.

MS SQL Server 2000 - Search a table with 300,000+ records in less then a second or two

I have one table with 300,000 records and 30 columns.
For example columns are ID, COMPANY, PhONE, NOTES ...
ID - nvarchar length-9
COMPANY - nvarchar length-30
NOTES - nvarchar length-250
Select * from database
where NOTES like '%something%'
Is there a way to get results from this query in less then 1-2 second
and how?
Full Text index this table and run a full population.
The query would look like this
select * from database where contains(NOTES,'something')
Use the wizard to build the FTS index on your table and make sure you run a
full population.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<scgwebmaster@.yahoo.com> wrote in message
news:1129307133.782947.259880@.f14g2000cwb.googlegr oups.com...
> I have one table with 300,000 records and 30 columns.
> For example columns are ID, COMPANY, PhONE, NOTES ...
> ID - nvarchar length-9
> COMPANY - nvarchar length-30
> NOTES - nvarchar length-250
> ----
> Select * from database
> where NOTES like '%something%'
> Is there a way to get results from this query in less then 1-2 second
> and how?
>

MS SQL Server 2000 - Search a table with 300,000+ records in less then a second or two

I have one table with 300,000 records and 30 columns.
For example columns are ID, COMPANY, PhONE, NOTES ...
---
ID - nvarchar length-9
COMPANY - nvarchar length-30
NOTES - nvarchar length-250
----
Select * from database
where NOTES like '%something%'
Is there a way to get results from this query in less then 1-2 second
and how?Maybe. If possible begin the % with a leading character and try creating a
NC index on the NOTES column. Or might also consider creating a Full-Text
index on the NOTES column and then use CONTAINS or FREETEXT.
HTH
Jerry
"nywebmaster" <scgwebmaster@.yahoo.com> wrote in message
news:1129306144.751022.186010@.o13g2000cwo.googlegroups.com...
>
> I have one table with 300,000 records and 30 columns.
> For example columns are ID, COMPANY, PhONE, NOTES ...
> ---
> ID - nvarchar length-9
> COMPANY - nvarchar length-30
> NOTES - nvarchar length-250
> ----
> Select * from database
> where NOTES like '%something%'
> Is there a way to get results from this query in less then 1-2 second
> and how?
>|||Thanks.

MS SQL Server 2000 - Search a table with 300,000+ records in less then a second or two

I have one table with 300,000 records and 30 columns.
For example columns are ID, COMPANY, PhONE, NOTES ...
---
ID - nvarchar length-9
COMPANY - nvarchar length-30
NOTES - nvarchar length-250
----
Select * from database
where NOTES like '%something%'
Is there a way to get results from this query in less then 1-2 second
and how?Maybe. If possible begin the % with a leading character and try creating a
NC index on the NOTES column. Or might also consider creating a Full-Text
index on the NOTES column and then use CONTAINS or FREETEXT.
HTH
Jerry
"nywebmaster" <scgwebmaster@.yahoo.com> wrote in message
news:1129306144.751022.186010@.o13g2000cwo.googlegroups.com...
>
> I have one table with 300,000 records and 30 columns.
> For example columns are ID, COMPANY, PhONE, NOTES ...
> ---
> ID - nvarchar length-9
> COMPANY - nvarchar length-30
> NOTES - nvarchar length-250
> ----
> Select * from database
> where NOTES like '%something%'
> Is there a way to get results from this query in less then 1-2 second
> and how?
>|||Thanks.sql

MS SQL Server 2000 - Search a table with 300,000+ records in less then a second or tw

I have one table with 300,000 records and 30 columns.
For example columns are ID, COMPANY, PhONE, NOTES ...
---
ID - nvarchar length-9
COMPANY - nvarchar length-30
NOTES - nvarchar length-250
----
Select * from database
where NOTES like '%something%'
Is there a way to get results from this query in less then 1-2 second
and how?You need to use a Full Text Index to do that kind of search quickly. Look
it up in Books Online.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"nywebmaster" <scgwebmaster@.yahoo.com> wrote in message
news:1129306366.597973.143180@.g43g2000cwa.googlegroups.com...
> I have one table with 300,000 records and 30 columns.
> For example columns are ID, COMPANY, PhONE, NOTES ...
> ---
> ID - nvarchar length-9
> COMPANY - nvarchar length-30
> NOTES - nvarchar length-250
> ----
> Select * from database
> where NOTES like '%something%'
> Is there a way to get results from this query in less then 1-2 second
> and how?
>|||Pattern matched searching when the wild card is prefixed to the parameter
cannot use an index and so in most cases, a table scan in employed. If this
is something critical, you might want to look into full text indexing
options.
If you know the pattern upfront, one trick you can use like create a
computed column representing the part of the string and indexing the column.
Anith|||To begin with, insure that NOTES is indexed.
http://www.microsoft.com/technet/pr...s/c0618260.mspx
Performing a LIKE search on '%something%' will not efficeintly utilize an
index on NOTES, however, 'something%' would.
http://msdn.microsoft.com/library/d...dcharacters.asp
If you need to perform fast 'wildcard' type searches, then consider
implemeting Index Server and full-text search. It is a service that runs
along side SQL Server. Just remember that the predicates CONTAINS and
FREETEXT are used for free-text searches, so it will involve making
revisions to some of your queries.
http://msdn.microsoft.com/library/d...r />
_3rqg.asp
"nywebmaster" <scgwebmaster@.yahoo.com> wrote in message
news:1129306366.597973.143180@.g43g2000cwa.googlegroups.com...
> I have one table with 300,000 records and 30 columns.
> For example columns are ID, COMPANY, PhONE, NOTES ...
> ---
> ID - nvarchar length-9
> COMPANY - nvarchar length-30
> NOTES - nvarchar length-250
> ----
> Select * from database
> where NOTES like '%something%'
> Is there a way to get results from this query in less then 1-2 second
> and how?
>|||Thanks

MS SQL Server 2000 - Search a table with 250,000+ records in less then a second

I have one table with 300,000 records and 30 columns.
For example columns are ID, COMPANY, PhONE, NOTES ...
----
ID - nvarchar length-9
COMPANY - nvarchar length-30
NOTES - nvarchar length-250
----
Select * from database
where NOTES like '%something%'
----
Is there a way to get results from this query in less then 1-2 second
and how?A few posts below is a remarkably similar question, only the table has
300,000+ rows. I think it applies to your case as well.
<scgwebmaster@.yahoo.com> wrote in message
news:1129305896.814659.100590@.g43g2000cwa.googlegroups.com...
>I have one table with 300,000 records and 30 columns.
> For example columns are ID, COMPANY, PhONE, NOTES ...
> ----
> ID - nvarchar length-9
> COMPANY - nvarchar length-30
> NOTES - nvarchar length-250
> ----
> Select * from database
> where NOTES like '%something%'
> ----
> Is there a way to get results from this query in less then 1-2 second
> and how?
>

MS SQL records pagination (LIMIT/OFSET)

What is best way to return 1st 20 records, then next 20 records, so on,
dynamically? (MySQL/pgSQL, others have limit/ofset).
Use co-related like this:
http://josephlindsay.com/archives/20...-ms-sql-server
http://msdn.microsoft.com/library/de...nethowto05.asp
Is there another better way ?
tia,
..V
"netsql" <netsql@.roomity.com> wrote in message
news:eI4KJytRGHA.1576@.tk2msftngp13.phx.gbl...
> What is best way to return 1st 20 records, then next 20 records, so on,
> dynamically? (MySQL/pgSQL, others have limit/ofset).
> Use co-related like this:
> http://josephlindsay.com/archives/20...-ms-sql-server
> http://msdn.microsoft.com/library/de...nethowto05.asp
> Is there another better way ?
> tia,
> .V
http://www.aspfaq.com/show.asp?id=2120
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||Is there a good SQL answer (for use w/
DataSource/WinForms/DataGrid/SmartClient and not ASP)
like http://dev.mysql.com/doc/refman/5.0/en/select.html ?
..V
David Portas wrote:
> "netsql" <netsql@.roomity.com> wrote in message
> news:eI4KJytRGHA.1576@.tk2msftngp13.phx.gbl...
> http://www.aspfaq.com/show.asp?id=2120
>
|||"netsql" <netsql@.roomity.com> wrote in message
news:4415DE37.2060805@.roomity.com...
> Is there a good SQL answer (for use w/
> DataSource/WinForms/DataGrid/SmartClient and not ASP)
> like http://dev.mysql.com/doc/refman/5.0/en/select.html ?
>
Read the whole article. Six of those techniques are pure SQL and don't use
ASP.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx

MS SQL records pagination (LIMIT/OFSET)

What is best way to return 1st 20 records, then next 20 records, so on,
dynamically? (MySQL/pgSQL, others have limit/ofset).
Use co-related like this:
http://josephlindsay.com/archives/2...n-ms-sql-server
http://msdn.microsoft.com/library/d...
ethowto05.asp
Is there another better way ?
tia,
.V"netsql" <netsql@.roomity.com> wrote in message
news:eI4KJytRGHA.1576@.tk2msftngp13.phx.gbl...
> What is best way to return 1st 20 records, then next 20 records, so on,
> dynamically? (MySQL/pgSQL, others have limit/ofset).
> Use co-related like this:
> http://josephlindsay.com/archives/2...enethowto05.asp
> Is there another better way ?
> tia,
> .V
http://www.aspfaq.com/show.asp?id=2120
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Is there a good SQL answer (for use w/
DataSource/WinForms/DataGrid/SmartClient and not ASP)
like http://dev.mysql.com/doc/refman/5.0/en/select.html ?
.V
David Portas wrote:
> "netsql" <netsql@.roomity.com> wrote in message
> news:eI4KJytRGHA.1576@.tk2msftngp13.phx.gbl...
> http://www.aspfaq.com/show.asp?id=2120
>|||"netsql" <netsql@.roomity.com> wrote in message
news:4415DE37.2060805@.roomity.com...
> Is there a good SQL answer (for use w/
> DataSource/WinForms/DataGrid/SmartClient and not ASP)
> like http://dev.mysql.com/doc/refman/5.0/en/select.html ?
>
Read the whole article. Six of those techniques are pure SQL and don't use
ASP.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

MS SQL records pagination (LIMIT/OFSET)

What is best way to return 1st 20 records, then next 20 records, so on,
dynamically? (MySQL/pgSQL, others have limit/ofset).
Use co-related like this:
http://josephlindsay.com/archives/2005/05/27/paging-results-in-ms-sql-server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenethowto05.asp
Is there another better way ?
tia,
.V"netsql" <netsql@.roomity.com> wrote in message
news:eI4KJytRGHA.1576@.tk2msftngp13.phx.gbl...
> What is best way to return 1st 20 records, then next 20 records, so on,
> dynamically? (MySQL/pgSQL, others have limit/ofset).
> Use co-related like this:
> http://josephlindsay.com/archives/2005/05/27/paging-results-in-ms-sql-server
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenethowto05.asp
> Is there another better way ?
> tia,
> .V
http://www.aspfaq.com/show.asp?id=2120
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Is there a good SQL answer (for use w/
DataSource/WinForms/DataGrid/SmartClient and not ASP)
like http://dev.mysql.com/doc/refman/5.0/en/select.html ?
.V
David Portas wrote:
> "netsql" <netsql@.roomity.com> wrote in message
> news:eI4KJytRGHA.1576@.tk2msftngp13.phx.gbl...
>> What is best way to return 1st 20 records, then next 20 records, so on,
>> dynamically? (MySQL/pgSQL, others have limit/ofset).
>> Use co-related like this:
>> http://josephlindsay.com/archives/2005/05/27/paging-results-in-ms-sql-server
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenethowto05.asp
>> Is there another better way ?
>> tia,
>> .V
> http://www.aspfaq.com/show.asp?id=2120
>|||"netsql" <netsql@.roomity.com> wrote in message
news:4415DE37.2060805@.roomity.com...
> Is there a good SQL answer (for use w/
> DataSource/WinForms/DataGrid/SmartClient and not ASP)
> like http://dev.mysql.com/doc/refman/5.0/en/select.html ?
>
Read the whole article. Six of those techniques are pure SQL and don't use
ASP.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

MS SQL 2000 Standard Edition Capability

Hi,
I'm about to build data warehouse of approx 15 Gb. The biggest table is
expected to be of 10 000 000 records. How will MS SQL 2000 Standard Edition
cope with it?
Thanks,
Alex
Standard edition from memory only supports up to 2Gb of memory. This might
prove problematic depending on how the wareohuse is used.
"Alexander Zotkin" <a@.a> wrote in message
news:emLy0OSDFHA.2220@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I'm about to build data warehouse of approx 15 Gb. The biggest table is
> expected to be of 10 000 000 records. How will MS SQL 2000 Standard
> Edition
> cope with it?
> Thanks,
> Alex
>
|||Hi,
Scott, you are wrong. If Sql Server Standard Edition is running on Windows
2000 Advance Server or Windows 2003 Server and /3GB switch is on in boot.ini,
Sql Server Standard Edition support up to 3GB.
It’s really a small data warehouse. If you don’t break data warehouse rules
in design and you will create necessary indexes, it will work ok.
Tomasz B.
"Scott Delaney" wrote:

> Standard edition from memory only supports up to 2Gb of memory. This might
> prove problematic depending on how the wareohuse is used.
>
> "Alexander Zotkin" <a@.a> wrote in message
> news:emLy0OSDFHA.2220@.TK2MSFTNGP09.phx.gbl...
>
>
|||I doubt if you will have any problems. 10M fact records is a very small
database. Unless there are other issues, such as several large dimensions,
you will be fine with Standard Edition. As you get into more complex
applications, you might start reading and thinking about the various best
practices outlined in the following two Guides:
http://www.microsoft.com/technet/pro.../anservog.mspx
http://www.microsoft.com/technet/pro.../ansvcspg.mspx
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Alexander Zotkin" <a@.a> wrote in message
news:emLy0OSDFHA.2220@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I'm about to build data warehouse of approx 15 Gb. The biggest table is
> expected to be of 10 000 000 records. How will MS SQL 2000 Standard
Edition
> cope with it?
> Thanks,
> Alex
>
|||Actually Tomasz you are incorrect and Scott is correct. While it is true
that you can enable the /3GB switch SQL Standard is hardcoded to not go
above 2GB.
Alex,
It all boils down to requirements and expectations but with a reasonable
design and proper indexing a 15GB warehouse is well within SQL Standards
capability.
Ray
"Tomasz Borawski" <TomaszBorawski@.discussions.microsoft.com> wrote in
message news:C4C34AFB-6747-4CD9-BB7B-12CE782BAED0@.microsoft.com...
> Hi,
> Scott, you are wrong. If Sql Server Standard Edition is running on Windows
> 2000 Advance Server or Windows 2003 Server and /3GB switch is on in
> boot.ini,
> Sql Server Standard Edition support up to 3GB.
> It's really a small data warehouse. If you don't break data warehouse
> rules
> in design and you will create necessary indexes, it will work ok.
> Tomasz B.
> "Scott Delaney" wrote:
>

MS SQL 2000 Standard Edition Capability

Hi,
I'm about to build data warehouse of approx 15 Gb. The biggest table is
expected to be of 10 000 000 records. How will MS SQL 2000 Standard Edition
cope with it?
Thanks,
AlexStandard edition from memory only supports up to 2Gb of memory. This might
prove problematic depending on how the wareohuse is used.
"Alexander Zotkin" <a@.a> wrote in message
news:emLy0OSDFHA.2220@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I'm about to build data warehouse of approx 15 Gb. The biggest table is
> expected to be of 10 000 000 records. How will MS SQL 2000 Standard
> Edition
> cope with it?
> Thanks,
> Alex
>|||Hi,
Scott, you are wrong. If Sql Server Standard Edition is running on Windows
2000 Advance Server or Windows 2003 Server and /3GB switch is on in boot.ini
,
Sql Server Standard Edition support up to 3GB.
It’s really a small data warehouse. If you don’t break data warehouse ru
les
in design and you will create necessary indexes, it will work ok.
Tomasz B.
"Scott Delaney" wrote:

> Standard edition from memory only supports up to 2Gb of memory. This might
> prove problematic depending on how the wareohuse is used.
>
> "Alexander Zotkin" <a@.a> wrote in message
> news:emLy0OSDFHA.2220@.TK2MSFTNGP09.phx.gbl...
>
>|||I doubt if you will have any problems. 10M fact records is a very small
database. Unless there are other issues, such as several large dimensions,
you will be fine with Standard Edition. As you get into more complex
applications, you might start reading and thinking about the various best
practices outlined in the following two Guides:
http://www.microsoft.com/technet/pr...n/anservog.mspx
http://www.microsoft.com/technet/pr...n/ansvcspg.mspx
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Alexander Zotkin" <a@.a> wrote in message
news:emLy0OSDFHA.2220@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I'm about to build data warehouse of approx 15 Gb. The biggest table is
> expected to be of 10 000 000 records. How will MS SQL 2000 Standard
Edition
> cope with it?
> Thanks,
> Alex
>|||Actually Tomasz you are incorrect and Scott is correct. While it is true
that you can enable the /3GB switch SQL Standard is hardcoded to not go
above 2GB.
Alex,
It all boils down to requirements and expectations but with a reasonable
design and proper indexing a 15GB warehouse is well within SQL Standards
capability.
Ray
"Tomasz Borawski" <TomaszBorawski@.discussions.microsoft.com> wrote in
message news:C4C34AFB-6747-4CD9-BB7B-12CE782BAED0@.microsoft.com...
> Hi,
> Scott, you are wrong. If Sql Server Standard Edition is running on Windows
> 2000 Advance Server or Windows 2003 Server and /3GB switch is on in
> boot.ini,
> Sql Server Standard Edition support up to 3GB.
> It's really a small data warehouse. If you don't break data warehouse
> rules
> in design and you will create necessary indexes, it will work ok.
> Tomasz B.
> "Scott Delaney" wrote:
>
>