Reset-button

I want a reset-button which clear my formular....

I have the following code in mypage.aspx.vb:

Sub Reset(ByVal sender As Object, ByVal e As System.EventArgs)

Me.Server.Transfer("Mypage.aspx") 'reloads the page without postback?

End Sub

And a button on mypage.aspx:

<asp:Button ID="Button2" OnClick="Reset" runat="server" Text="Rensa" />

But when I click the button....the validation-controls executes before...so instead for "clearing" the page (reload it without postback) the validation-messages shows that I have forgott to write in som textboxes....

What should I do?

hi
you use this statement:

If Not Page.IsPostBack Then
< validation statement >
End If

good luck

sql

Reserved Error importing Access 2003 Report into VS2005 Report Module, How do I troublesho

Hi,
I'm trying to Import an existing Access 2003 report into into an existing
VS2005 Report Project, I am getting the following error. Is there a way to
troubleshoot what is causing this error?
Importing reports from 'C:\db2.mdb'...
Error : An error occurred while the report Test Report Form was being
imported: Reserved ErrorWe ran across a few reports with this issue. I reviewed my notes but didn't
come up with anything.
I found this in a group:
2 From: Albert Yen [MSFT] - view profile
Date: Tues, Jul 26 2005 3:51 pm
Email: "Albert Yen [MSFT]" <albe...@.online.microsoft.com>
Groups: microsoft.public.sqlserver.reportingsvcs
Not yet ratedRating:
show options
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Report Abuse | Find messages by this author
The first error could be coming from Access. Could you try the following?
Open your database in Microsoft Access. Create a new Module and paste the
following code into it:
Sub Export()
Application.ExportXML ObjectType:=acExportReport, _
DataSource:="DailySales ", _
ImageTarget:=".", _
PresentationTarget:="DailySales .xsl", _
OtherFlags:=acPersistReportML
End Sub
Set the cursor at the beginning of the Sub and click the Run button. If
ExportXML succeeds, it should create a file called "DailySales_report.xml"
in your "My Documents" folder. If you can send the file to me, I'll look at
it. If ExportXML fails, then it's an Access problem. You could try the
Access newsgroups for help.
Albert Yen
SQL Server Reporting Services
Steve MunLeeuw
"Rob Dob" <robdob20012002@.yahoo.com> wrote in message
news:u8Pq0zJ7GHA.4708@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I'm trying to Import an existing Access 2003 report into into an existing
> VS2005 Report Project, I am getting the following error. Is there a way
> to troubleshoot what is causing this error?
> Importing reports from 'C:\db2.mdb'...
> Error : An error occurred while the report Test Report Form was being
> imported: Reserved Error
>

reserved character issue in create folder

When I try and create a folder using the following syntax:
folder/subfolder/anotherfolder
I get the following error
The item name is not valid. Item names cannot contain the following reserved
characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or spaces.
When checking the MSDN documentation for the ReportServices CreatFolder I
noticed it contains the following comment:
Folder names cannot be null, consist of empty strings, or contain the
following reserved characters:
: ? ; @. & = + $ , \ * > < | . "
The difference is the message my ReportServer is giving me includes the '/'
character, while the documentaion does not.
This is causing a great deal of pain with my deployment scripts and I can't
find any information on this issue.Hi
Generally, you need to create folders one level at a time.
folder
cd folder
then
subfolder
cd subfolder
then
anotherfolder
cd anotherfolder
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"DerrickBrown100" <DerrickBrown100@.discussions.microsoft.com> wrote in
message news:D7B14559-8330-453C-A86D-6E137D2AE287@.microsoft.com...
> When I try and create a folder using the following syntax:
> folder/subfolder/anotherfolder
> I get the following error
> The item name is not valid. Item names cannot contain the following
> reserved
> characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or
> spaces.
> When checking the MSDN documentation for the ReportServices CreatFolder I
> noticed it contains the following comment:
> Folder names cannot be null, consist of empty strings, or contain the
> following reserved characters:
> : ? ; @. & = + $ , \ * > < | . "
> The difference is the message my ReportServer is giving me includes the
> '/'
> character, while the documentaion does not.
> This is causing a great deal of pain with my deployment scripts and I
> can't
> find any information on this issue.
>|||Thanks for the reply. Perhaps a little more information regarding the
situation would help. I am currently working on a setup/deployment project
that will install our SRS reports on the target machine. I am using the web
service interface to set up the directory structure and deploy reports via
the CreateFolder method. Including the '/' in the CreateFolder call works on
every machine in the organization except my local developer installation.
Furthermore, the MSDN docs do not list the '/' as a reserved character.
However, my SRS installation returns an error listing the '/' as a reserved
character. I would assume this is a bug having to do with my configuration
and was wondering id anyone else had experienced this.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Generally, you need to create folders one level at a time.
> folder
> cd folder
> then
> subfolder
> cd subfolder
> then
> anotherfolder
> cd anotherfolder
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "DerrickBrown100" <DerrickBrown100@.discussions.microsoft.com> wrote in
> message news:D7B14559-8330-453C-A86D-6E137D2AE287@.microsoft.com...
> > When I try and create a folder using the following syntax:
> >
> > folder/subfolder/anotherfolder
> >
> > I get the following error
> > The item name is not valid. Item names cannot contain the following
> > reserved
> > characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or
> > spaces.
> >
> > When checking the MSDN documentation for the ReportServices CreatFolder I
> > noticed it contains the following comment:
> >
> > Folder names cannot be null, consist of empty strings, or contain the
> > following reserved characters:
> > : ? ; @. & = + $ , \ * > < | . "
> >
> > The difference is the message my ReportServer is giving me includes the
> > '/'
> > character, while the documentaion does not.
> >
> > This is causing a great deal of pain with my deployment scripts and I
> > can't
> > find any information on this issue.
> >
> >
>
>

reregister sqlDmo.dll

When I try to script my database, I get the following error:
schema_name is not recognized function name
I found that I have to reregister sqlDmo.dll
How can I do that?
Thank you,
Simonregsvr32.exe "%ProgramFiles%\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll"
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"simon" <simon.zupan@.stud-moderna.si> wrote in message
news:OQHzo5pCFHA.4004@.tk2msftngp13.phx.gbl...
> When I try to script my database, I get the following error:
> schema_name is not recognized function name
> I found that I have to reregister sqlDmo.dll
> How can I do that?
> Thank you,
> Simon
>

required help

I have written the following stored procedure but I am gettig some errors, can anybody help me.
CREATE PROCEDURE <procedurename>
@.tempstr as varchar(20),
@.ntempstr as varchar(20),
@.cdestr as varchar(20),
@.Indstr as varchar(20),
@.prdstr as varchar(20),
@.notpos as numeric,
@.nnotpos as numeric,
@.orapos as numeric
AS
begin
while (@.tempstr !=' ' )
loop
begin
@.orapos=CHARINDEX("OR", @.tmpstr)
if (@.orapos > 0)
begin
@.ntempstr=LTRIM(LEFT(@.tempstr, 2))
@.tempstr=Ltrim(mid(@.tempstr, (@.orpos+2))
end
else
begin
@.ntempstr=LTRIM(@.tempstr)
@.tempstr= ' '

@.notpos=CHARINDEX("NOT", @.tmpstr)
end
If @. @.notpos > 0 Then
@.nnotpos = LTrim(Mid( @.nnotpos, @.notpos + 3))
end
end

for( loop
GO

Quote:

Originally Posted by samb

I have written the following stored procedure but I am gettig some errors, can anybody help me.
CREATE PROCEDURE <procedurename>
@.tempstr as varchar(20),
@.ntempstr as varchar(20),
@.cdestr as varchar(20),
@.Indstr as varchar(20),
@.prdstr as varchar(20),
@.notpos as numeric,
@.nnotpos as numeric,
@.orapos as numeric
AS
begin
while (@.tempstr !=' ' )
loop
begin
@.orapos=CHARINDEX("OR", @.tmpstr)
if (@.orapos > 0)
begin
@.ntempstr=LTRIM(LEFT(@.tempstr, 2))
@.tempstr=Ltrim(mid(@.tempstr, (@.orpos+2))
end
else
begin
@.ntempstr=LTRIM(@.tempstr)
@.tempstr= ' '

@.notpos=CHARINDEX("NOT", @.tmpstr)
end
If @. @.notpos > 0 Then
@.nnotpos = LTrim(Mid( @.nnotpos, @.notpos + 3))
end
end

for( loop
GO

Unfortunately there really are quite a few errors in it. I suggest you start with a simpler version and then expand it as you get experience. A few corrections:it is not complete code snippet (the 'for' loop at the end is obviously incomplete, plus you have variables which you never use)

Request for confirmation: This bug is fixed

Hello World,
One of our customers keeps getting the following error:
ODBC error code: -1
Net library error code: 2746x (10054)
SQLState: 01000
Description: ConnectionWrite(send())
I have looked up on the Microsoft web pages and have found:
http://support.microsoft.com/kb/q303120/
The description on this page states that this bug was fixed with SQL
Server 2000, service pack 2, so I asked the customer about the server
version number of his SQL Server 2000.
He has 8.00.818 (and lightweight pooling to default, which is off).
Accorind to the SQL Server 2000, service pack 3 description, an
installed SP3 has number 8.00.760.
Due to this circumstances I suppose our customer has a fixed version of
SQL Server 2000 and the problem is located somewhere else. Am I right?
Thanks for your help and best regards
Andreas
--
Andreas Tscharner andreas.tscharner@.metromec.ch
---
Das Denken eines Programmierers ist stets logisch (IF 1=2 THEN CALL
MainProgram), immer strukturiert und von keinerlei Vorurteilen
beeinträchtigt (ON Hunger GOSUB Aldi ELSE RETURN).
-- aus Murphy's Computergesetzen8.00.818 is the version number for the MS03-031 security patch. It was released after SP3a.
/risun
>--Original Message--
>Hello World,
>One of our customers keeps getting the following error:
>ODBC error code: -1
>Net library error code: 2746x (10054)
>SQLState: 01000
>Description: ConnectionWrite(send())
>I have looked up on the Microsoft web pages and have found:
>http://support.microsoft.com/kb/q303120/
>The description on this page states that this bug was fixed with SQL >Server 2000, service pack 2, so I asked the customer about the server >version number of his SQL Server 2000.
>He has 8.00.818 (and lightweight pooling to default, which is off). >Accorind to the SQL Server 2000, service pack 3 description, an >installed SP3 has number 8.00.760.
>Due to this circumstances I suppose our customer has a fixed version of >SQL Server 2000 and the problem is located somewhere else. Am I right?
>Thanks for your help and best regards
> Andreas
>-- >Andreas Tscharner andreas.tscharner@.metromec.ch
>----
--
>Das Denken eines Programmierers ist stets logisch (IF 1=3D2 THEN CALL
>MainProgram), immer strukturiert und von keinerlei Vorurteilen
>beeintr=E4chtigt (ON Hunger GOSUB Aldi ELSE RETURN).
> -- aus Murphy's Computergesetzen
>.
>|||Anthony,
Please stop confusing people by referring to build 817 (or 818 or 819
or MS03-031) as the "Slammer Worm build." This has nothing to do with
Slammer. As I've already pointed out, and as you can verify by reading
the security bulletins, MS03-031 addresses three post-Slammer
vulnerabilities. Like all Microsoft hotfixes, it is cumulative, but it
is definitely not the "Slammer Worm build," and it was released long
after the patch and service pack addressing the Slammer vulnerability
were released.
SK
AnthonyThomas wrote:
>Actually, 817 is the MS03-031 Slammer Worm build. 818 fixes an error MS03-031 introduced into the DTSGUI.dll and build 819 fixes a SQLEM password error introduced by the 818 fix. You should have build 819 to have all the tools fixed.
>Also, there have been three other publicly available hot fixes since then, 839, 859, and the latest, 879.
>Sincerely,
>
>Anthony Thomas
>
>|||Thanks for clearing this up, Anthony!
SK
AnthonyThomas wrote:
>My apologies to everyone. You, of course, are absolutely right. The Sapphire/Slammer Worm attacked Jan. 25, 2003, but the patches were available the prior summer but had not been applied by many. Obviously, MS03-031 was deployed until later 2003. Both deal with protocol hijacking and buffer overrun issues and, since we had been applying SP3, then shortly thereafter, SP3a, this seemed like the proactive release.
>The confusion was entirely my own.
>Sincerely,
>
>Anthony Thomas
>
>

request advice on judging memory usage/allocation

Hello,
I'm relatively new to SQL Server, and have 'inherited' a SQL Server box
with the following specs:
Windows 2003 SP1, SQL Server 2000 SP 3 (or 3a?), single-processor
license
2.8 GHz Xeon, 2 GB RAM, about 2 years old
Great Plains 7.5 company DBs, about 8-9 users during the day, total DB
size < 5 GB? I don't know exactly.
Other apps are the OS, some Access MDBs accessed by Access front ends
via Citrix, and an Abra Suite DB (FoxPro tables, eventually to be
migrated to SQL Server, the Abra client is on Citrix servers.
We have a monitoring system through our support consultant. This system
tells us now and then that SQL has used up all its physical memory, but
these alerts occur at odd times like midnight on a Sunday (to be fair,
this is around the time when SQL does its maintenance, backup, etc), or
540 pm when the main GP users have all gone home and are not doing
anything in GP. I don't know yet if SQL is paging a lot, but no
specific end user complaints have appeared yet, so we have time to be
pro-active.
I've recently found some information on which PerfMon items to check,
and will try these.
My questions:
1. If we install 4 GB of RAM do I need to learn about doing anything
special like set PAE or AWE parameters or boot.ini parameters or
anything' Most of the MS links I saw on the list are for Windows 2000
Server, not Windows 2003 Server.
2. If we put in 4 GB of RAM, it seems to me that setting SQL to 2.5 GB
max and leaving the remainder for the OS and Abra Suite would work
until Abra Suite's DB is upgraded to SQL 2005, in which case I would
change it to 3 GB for SQL and the remaining 1 GB for the OS and IIS,
which is our most likely upgrade path. Does this make sense'
Right now SQL is set to dynamic memory allocation and I would like to
leave it this way if possible but I want to learn about preventing
future issues down the road related to virtual or physical memory,
especially to prevent paging, this server has to last a while!!
3. Any other forum threads or websites or advice would be most welcome.
Thank you for reading this,
Tom"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1151518715.642430.142110@.x69g2000cwx.googlegroups.com...
> Hello,
> I'm relatively new to SQL Server, and have 'inherited' a SQL Server box
> with the following specs:
> Windows 2003 SP1, SQL Server 2000 SP 3 (or 3a?), single-processor
> license
> 2.8 GHz Xeon, 2 GB RAM, about 2 years old
> Great Plains 7.5 company DBs, about 8-9 users during the day, total DB
> size < 5 GB? I don't know exactly.
> Other apps are the OS, some Access MDBs accessed by Access front ends
> via Citrix, and an Abra Suite DB (FoxPro tables, eventually to be
> migrated to SQL Server, the Abra client is on Citrix servers.
> We have a monitoring system through our support consultant. This system
> tells us now and then that SQL has used up all its physical memory, but
> these alerts occur at odd times like midnight on a Sunday (to be fair,
> this is around the time when SQL does its maintenance, backup, etc), or
> 540 pm when the main GP users have all gone home and are not doing
> anything in GP. I don't know yet if SQL is paging a lot, but no
> specific end user complaints have appeared yet, so we have time to be
> pro-active.
> I've recently found some information on which PerfMon items to check,
> and will try these.
> My questions:
> 1. If we install 4 GB of RAM do I need to learn about doing anything
> special like set PAE or AWE parameters or boot.ini parameters or
> anything' Most of the MS links I saw on the list are for Windows 2000
> Server, not Windows 2003 Server.
No. In a small setup like this SQL Server will use < 2GB of ram (that's SQL
2000 Standard Ed.'s limit).
If you install more ram, the additional ram will be available for the other
applications, and they won't have to fight with SQL Server for memory.
SQL Server is designed to use up all the available memory for data cache,
which is appropriate only for a dedicated SQL Server. If you don't install
more ram, you should change SQL Server's max memory setting to leave enough
memory for the other applications to run..SQL Server will run just fine with
1G or 1.5G of ram. It will just use a smaller data cache and have to go to
disk more often.
David|||Thank you for responding...I put in two more short questions below.
David Browne wrote:
> No. In a small setup like this SQL Server will use < 2GB of ram (that's SQL
> 2000 Standard Ed.'s limit).
> If you install more ram, the additional ram will be available for the other
> applications, and they won't have to fight with SQL Server for memory.
Adding more RAM will not make any difference' Sigh. Thank you.
Does SQL Server 2005 Standard have the same limitation' One book I
read states that SQL Server 2005 Standard has no maximum RAM limit,
please correct me if I am wrong, so that seems like a good reason to
upgrade when we can do so, at which point it will only have SQL Server,
IIS, and the OS.
> SQL Server is designed to use up all the available memory for data cache,
> which is appropriate only for a dedicated SQL Server. If you don't install
> more ram, you should change SQL Server's max memory setting to leave enough
> memory for the other applications to run..SQL Server will run just fine with
> 1G or 1.5G of ram. It will just use a smaller data cache and have to go to
> disk more often.
Are there any *negative* consequences to SQL Server 2000 paging to disk
more often other than things possibly being "slower" and whatever wear
and tear could happen to the disk drives'
So far our server may not be paging very much at all, the alerts we
receive state that the server is using ~2% of virtual memory (paging).
Is any information available about judging how much RAM the OS (Windows
2003) should have available'
The pagefile BTW on this server I believe is 4 GB.
Thank you for your help so far.
Thank you, Tom

request advice on judging memory usage/allocation

Hello,
I'm relatively new to SQL Server, and have 'inherited' a SQL Server box
with the following specs:
Windows 2003 SP1, SQL Server 2000 SP 3 (or 3a?), single-processor
license
2.8 GHz Xeon, 2 GB RAM, about 2 years old
Great Plains 7.5 company DBs, about 8-9 users during the day, total DB
size < 5 GB? I don't know exactly.
Other apps are the OS, some Access MDBs accessed by Access front ends
via Citrix, and an Abra Suite DB (FoxPro tables, eventually to be
migrated to SQL Server, the Abra client is on Citrix servers.
We have a monitoring system through our support consultant. This system
tells us now and then that SQL has used up all its physical memory, but
these alerts occur at odd times like midnight on a Sunday (to be fair,
this is around the time when SQL does its maintenance, backup, etc), or
540 pm when the main GP users have all gone home and are not doing
anything in GP. I don't know yet if SQL is paging a lot, but no
specific end user complaints have appeared yet, so we have time to be
pro-active.
I've recently found some information on which PerfMon items to check,
and will try these.
My questions:
1. If we install 4 GB of RAM do I need to learn about doing anything
special like set PAE or AWE parameters or boot.ini parameters or
anything' Most of the MS links I saw on the list are for Windows 2000
Server, not Windows 2003 Server.
2. If we put in 4 GB of RAM, it seems to me that setting SQL to 2.5 GB
max and leaving the remainder for the OS and Abra Suite would work
until Abra Suite's DB is upgraded to SQL 2005, in which case I would
change it to 3 GB for SQL and the remaining 1 GB for the OS and IIS,
which is our most likely upgrade path. Does this make sense'
Right now SQL is set to dynamic memory allocation and I would like to
leave it this way if possible but I want to learn about preventing
future issues down the road related to virtual or physical memory,
especially to prevent paging, this server has to last a while!!
3. Any other forum threads or websites or advice would be most welcome.
Thank you for reading this,
Tom"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1151518715.642430.142110@.x69g2000cwx.googlegroups.com...
> Hello,
> I'm relatively new to SQL Server, and have 'inherited' a SQL Server box
> with the following specs:
> Windows 2003 SP1, SQL Server 2000 SP 3 (or 3a?), single-processor
> license
> 2.8 GHz Xeon, 2 GB RAM, about 2 years old
> Great Plains 7.5 company DBs, about 8-9 users during the day, total DB
> size < 5 GB? I don't know exactly.
> Other apps are the OS, some Access MDBs accessed by Access front ends
> via Citrix, and an Abra Suite DB (FoxPro tables, eventually to be
> migrated to SQL Server, the Abra client is on Citrix servers.
> We have a monitoring system through our support consultant. This system
> tells us now and then that SQL has used up all its physical memory, but
> these alerts occur at odd times like midnight on a Sunday (to be fair,
> this is around the time when SQL does its maintenance, backup, etc), or
> 540 pm when the main GP users have all gone home and are not doing
> anything in GP. I don't know yet if SQL is paging a lot, but no
> specific end user complaints have appeared yet, so we have time to be
> pro-active.
> I've recently found some information on which PerfMon items to check,
> and will try these.
> My questions:
> 1. If we install 4 GB of RAM do I need to learn about doing anything
> special like set PAE or AWE parameters or boot.ini parameters or
> anything' Most of the MS links I saw on the list are for Windows 2000
> Server, not Windows 2003 Server.
No. In a small setup like this SQL Server will use < 2GB of ram (that's SQL
2000 Standard Ed.'s limit).
If you install more ram, the additional ram will be available for the other
applications, and they won't have to fight with SQL Server for memory.
SQL Server is designed to use up all the available memory for data cache,
which is appropriate only for a dedicated SQL Server. If you don't install
more ram, you should change SQL Server's max memory setting to leave enough
memory for the other applications to run..SQL Server will run just fine with
1G or 1.5G of ram. It will just use a smaller data cache and have to go to
disk more often.
David|||"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1151518715.642430.142110@.x69g2000cwx.googlegroups.com...
> Hello,
> I'm relatively new to SQL Server, and have 'inherited' a SQL Server box
> with the following specs:
> Windows 2003 SP1, SQL Server 2000 SP 3 (or 3a?), single-processor
> license
> 2.8 GHz Xeon, 2 GB RAM, about 2 years old
> Great Plains 7.5 company DBs, about 8-9 users during the day, total DB
> size < 5 GB? I don't know exactly.
> Other apps are the OS, some Access MDBs accessed by Access front ends
> via Citrix, and an Abra Suite DB (FoxPro tables, eventually to be
> migrated to SQL Server, the Abra client is on Citrix servers.
> We have a monitoring system through our support consultant. This system
> tells us now and then that SQL has used up all its physical memory, but
> these alerts occur at odd times like midnight on a Sunday (to be fair,
> this is around the time when SQL does its maintenance, backup, etc), or
> 540 pm when the main GP users have all gone home and are not doing
> anything in GP. I don't know yet if SQL is paging a lot, but no
> specific end user complaints have appeared yet, so we have time to be
> pro-active.
> I've recently found some information on which PerfMon items to check,
> and will try these.
> My questions:
> 1. If we install 4 GB of RAM do I need to learn about doing anything
> special like set PAE or AWE parameters or boot.ini parameters or
> anything' Most of the MS links I saw on the list are for Windows 2000
> Server, not Windows 2003 Server.
No. In a small setup like this SQL Server will use < 2GB of ram (that's SQL
2000 Standard Ed.'s limit).
If you install more ram, the additional ram will be available for the other
applications, and they won't have to fight with SQL Server for memory.
SQL Server is designed to use up all the available memory for data cache,
which is appropriate only for a dedicated SQL Server. If you don't install
more ram, you should change SQL Server's max memory setting to leave enough
memory for the other applications to run..SQL Server will run just fine with
1G or 1.5G of ram. It will just use a smaller data cache and have to go to
disk more often.
David|||Thank you for responding...I put in two more short questions below.
David Browne wrote:

> No. In a small setup like this SQL Server will use < 2GB of ram (that's S
QL
> 2000 Standard Ed.'s limit).
> If you install more ram, the additional ram will be available for the othe
r
> applications, and they won't have to fight with SQL Server for memory.
Adding more RAM will not make any difference' Sigh. Thank you.
Does SQL Server 2005 Standard have the same limitation' One book I
read states that SQL Server 2005 Standard has no maximum RAM limit,
please correct me if I am wrong, so that seems like a good reason to
upgrade when we can do so, at which point it will only have SQL Server,
IIS, and the OS.

> SQL Server is designed to use up all the available memory for data cache,
> which is appropriate only for a dedicated SQL Server. If you don't instal
l
> more ram, you should change SQL Server's max memory setting to leave enoug
h
> memory for the other applications to run..SQL Server will run just fine wi
th
> 1G or 1.5G of ram. It will just use a smaller data cache and have to go t
o
> disk more often.
Are there any *negative* consequences to SQL Server 2000 paging to disk
more often other than things possibly being "slower" and whatever wear
and tear could happen to the disk drives'
So far our server may not be paging very much at all, the alerts we
receive state that the server is using ~2% of virtual memory (paging).
Is any information available about judging how much RAM the OS (Windows
2003) should have available'
The pagefile BTW on this server I believe is 4 GB.
Thank you for your help so far.
Thank you, Tom|||Thank you for responding...I put in two more short questions below.
David Browne wrote:

> No. In a small setup like this SQL Server will use < 2GB of ram (that's S
QL
> 2000 Standard Ed.'s limit).
> If you install more ram, the additional ram will be available for the othe
r
> applications, and they won't have to fight with SQL Server for memory.
Adding more RAM will not make any difference' Sigh. Thank you.
Does SQL Server 2005 Standard have the same limitation' One book I
read states that SQL Server 2005 Standard has no maximum RAM limit,
please correct me if I am wrong, so that seems like a good reason to
upgrade when we can do so, at which point it will only have SQL Server,
IIS, and the OS.

> SQL Server is designed to use up all the available memory for data cache,
> which is appropriate only for a dedicated SQL Server. If you don't instal
l
> more ram, you should change SQL Server's max memory setting to leave enoug
h
> memory for the other applications to run..SQL Server will run just fine wi
th
> 1G or 1.5G of ram. It will just use a smaller data cache and have to go t
o
> disk more often.
Are there any *negative* consequences to SQL Server 2000 paging to disk
more often other than things possibly being "slower" and whatever wear
and tear could happen to the disk drives'
So far our server may not be paging very much at all, the alerts we
receive state that the server is using ~2% of virtual memory (paging).
Is any information available about judging how much RAM the OS (Windows
2003) should have available'
The pagefile BTW on this server I believe is 4 GB.
Thank you for your help so far.
Thank you, Tom

Reprocessing Errors after using the migrationwizard

Hello,

I have converted a AS2000 project to AS2005 using the migrationwizard. All went well, unfortunately I get the following errors when I try to reprocess in AS2005 and I have no idea how to fix them. Does anybody have an idea what I can do ? The first error seems like there is something wrong in my DB with type matching, but it doesn't say where.

Errors in the high-level relational engine. The following exception occurred while an operation was being performed on a data source view: Parent Columns and Child Columns don't have type-matching columns..

Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Taak', Name of 'Taak' was being processed.

Errors in the OLAP storage engine: An error occurred while the 'Subtaak attribute' attribute of the 'Taak' dimension from the 'DIMSCUBE1' database was being processed.

Are any of your keys TinyInts with IDENTITY clauses on them?
If so, this is a known restriction of SQLXML (which we are using under the covers). It converts all IDENTITY columns to full integers (and thus you are getting a datatype mismatch. Using either a VIEW or a DSV named query (or computed column) convert the keys (both the PK and the FK parent column) to integers and see what happens.

_-_-_ Dave

Representing rows as columns

Hi
I have a table in SQL Server 2000 that has following data:

PunchTime PunchType
11:45:00 In
12:45:00 Out
1:45:00 In
3:15:00 Out

Is there a way in SQL to represent this in the following format:
In Out In Out
11:45:00 12:45:00 1:45:00 3:15:00

ThanksYou specification is unclear in several respects. What is the datatype of
the PunchTime column (DATETIME or CHAR maybe)? What is the primary key of
this table? Do we know whether the times are AM or PM? Why is 1:45 shown
after 12:45 in your required result?

The best answer will be to do it in your client application. What you want
is purely presentational and presentational functionality belongs
client-side.

--
David Portas
SQL Server MVP
--|||[posted and mailed, please reply in news]

Rajeev (navvyus@.yahoo.com) writes:
> I have a table in SQL Server 2000 that has following data:
> PunchTime PunchType
> 11:45:00 In
> 12:45:00 Out
> 1:45:00 In
> 3:15:00 Out
> Is there a way in SQL to represent this in the following format:
> In Out In Out
> 11:45:00 12:45:00 1:45:00 3:15:00

There is no built-in construct, but there are a couple of possibilities
to depending on your requirements.

For this particular case, you could to this, under the assumption that
you have at most four rows per day:

SELECT In = in1.PunchTime, Out = out1.PunchTime,
In = in2.PunchTime, Out = out2.PunchTime
FROM tbl in1
JOIN tbl out1 ON in1.PunchDate = out1.PunchDate
LEFT JOIN tbl in2 ON in1.Punchdate = in2.PunchDate
AND in1.PunchType = in2.PunchType
AND in1.PunchType < in2.PunchType
LEFT JOIN tbl out2 ON out1.Punchdate = out2.PunchDate
AND out1.PunchType = out2.PunchType
AND out1.PunchType < out2.PunchType
WHERE in1.PunchType = 'In'
AND out1.PunchType = 'Out'

Here I have assumed there is a date column in the table, since that
would make sense. I have also been lazy and assumed that there is
always one In and one Out each day.

In a more general columns where you want dynamic column names etc,
you have to build dynamic SQL. But before you do that, check out
the third-party tool RAC, http://www.rac4sql.net/ which aspires to
be the ultimate tool for crosstab queries.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Reposting: Database Version Issue

I just installed SP2 for 2005 standard edition and am getting the following
error when trying to use report server:
"The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase)"
When I go into Reporting service configuration tool, the update button
returns the following:
"The database version matches your Reporting services installation"
and the database version is reported as 'C.0.8.54'.
this is critical and I need to get this up and running again. Any ideas?
--
John Cleveland
Network Manager
Urban systems LtdHave you installed any SQL service packs BEFORE adding other parts
like 'reporting services'
Also, there was a critical patch sent through windows update that
updates SQL server. Not sure if that is causing you problems.
On Apr 13, 1:16 am, John Cleveland
<JohnClevel...@.discussions.microsoft.com> wrote:
> I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
> --
> John Cleveland
> Network Manager
> Urban systems Ltd|||SP1 was already installed. reporting services was installed pre sp1.
I've narrowed down the sequence of events that lead to this issue. It seems
there was a reporting services update that was installed without my knowledge
that was intended for sp2 installs. SP2 wasn't installed yet. even though
sp2 is now installed, i still get the error message listed previously.
--
John Cleveland
Network Manager
Urban systems Ltd
"gommo" wrote:
> Have you installed any SQL service packs BEFORE adding other parts
> like 'reporting services'
> Also, there was a critical patch sent through windows update that
> updates SQL server. Not sure if that is causing you problems.
> On Apr 13, 1:16 am, John Cleveland
> <JohnClevel...@.discussions.microsoft.com> wrote:
> > I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
>
>|||Is there a possibility that you actually have two different db's and your
reportserver instance is pointed at the "wrong" one frm the POV of the one
that your web application thinks it should connect to?
This might have happened if the person applying the update is not the
administrator of the box. See
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
It can also happen if you apply the update in the wrong identity, even if
you are an administrator (I know that from personal experience <sigh> FWIW
the ReportServer database has a sprocwhere this is hard coded. I kid you
not. I think it gets adjusted during upgrades with a file called
catalog.sql. )
Short version of the fix described in that thread: you have to stop IIS and
RS and copy the files that were truly upgraded to the correct location --
but you should probably read the thread.
HTH,
>L<
"John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
>I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is
> not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report
> server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
>
> --
> John Cleveland
> Network Manager
> Urban systems Ltd
>|||I actually have this fixed now, it was caused by the sp2 upgrade. I
uninstalled rs, reinstalled and applied sp2 once again and all is fine.
Reports cam back properly, but the data sources had to be reconfigured. No
biggie.
Thanks for your suggestions though.
--
John Cleveland
Network Manager
Urban systems Ltd
"Lisa Slater Nicholls" wrote:
> Is there a possibility that you actually have two different db's and your
> reportserver instance is pointed at the "wrong" one frm the POV of the one
> that your web application thinks it should connect to?
> This might have happened if the person applying the update is not the
> administrator of the box. See
> http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
> It can also happen if you apply the update in the wrong identity, even if
> you are an administrator (I know that from personal experience <sigh> FWIW
> the ReportServer database has a sprocwhere this is hard coded. I kid you
> not. I think it gets adjusted during upgrades with a file called
> catalog.sql. )
> Short version of the fix described in that thread: you have to stop IIS and
> RS and copy the files that were truly upgraded to the correct location --
> but you should probably read the thread.
> HTH,
> >L<
>
> "John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
> news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
> >I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is
> > not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report
> > server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
> >
>

Repost:The processing of filter expression for the chart "MyChart" cannot be performed. Th

I got the following error when I try to luanch the report ,it is working on
another server with SP1 installed on it .Could it be the problem?(Not havinf
Sp1)
The processing of filter expression for the chart "MyChart" cannot be
performed. The comparison failed
I removed the filter and it works,why this filter is working in the other
server and not in this server.
here is the filters that I use:
=Fields!monthName.Value
!= Total
ThanksDoes installing SP1 resolve it on the other server too?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"ALI-R" <newbie@.microsoft.com> wrote in message
news:OkIHP4KCFHA.1392@.tk2msftngp13.phx.gbl...
> I got the following error when I try to luanch the report ,it is working
on
> another server with SP1 installed on it .Could it be the problem?(Not
havinf
> Sp1)
> The processing of filter expression for the chart "MyChart" cannot be
> performed. The comparison failed
> I removed the filter and it works,why this filter is working in the other
> server and not in this server.
> here is the filters that I use:
>
> =Fields!monthName.Value
> !=> Total
> Thanks
>|||I haven't had the chance to install SP1 yet,Do you think it might be
relevant?
Thanks
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:%23vIDaCOCFHA.268@.TK2MSFTNGP10.phx.gbl...
> Does installing SP1 resolve it on the other server too?
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "ALI-R" <newbie@.microsoft.com> wrote in message
> news:OkIHP4KCFHA.1392@.tk2msftngp13.phx.gbl...
> > I got the following error when I try to luanch the report ,it is working
> on
> > another server with SP1 installed on it .Could it be the problem?(Not
> havinf
> > Sp1)
> >
> > The processing of filter expression for the chart "MyChart" cannot
be
> > performed. The comparison failed
> > I removed the filter and it works,why this filter is working in the
other
> > server and not in this server.
> > here is the filters that I use:
> >
> >
> > =Fields!monthName.Value
> > !=> > Total
> >
> > Thanks
> >
> >
>|||While there is no specific change for chart filters in SP1, there are some
improvements to make chart processing more efficient. Also from your
description, the same report with the same data works fine on the SP1
server.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"ALI-R" <newbie@.microsoft.com> wrote in message
news:exH0YqUCFHA.2960@.TK2MSFTNGP14.phx.gbl...
> I haven't had the chance to install SP1 yet,Do you think it might be
> relevant?
> Thanks
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:%23vIDaCOCFHA.268@.TK2MSFTNGP10.phx.gbl...
> > Does installing SP1 resolve it on the other server too?
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "ALI-R" <newbie@.microsoft.com> wrote in message
> > news:OkIHP4KCFHA.1392@.tk2msftngp13.phx.gbl...
> > > I got the following error when I try to luanch the report ,it is
working
> > on
> > > another server with SP1 installed on it .Could it be the problem?(Not
> > havinf
> > > Sp1)
> > >
> > > The processing of filter expression for the chart "MyChart" cannot
> be
> > > performed. The comparison failed
> > > I removed the filter and it works,why this filter is working in the
> other
> > > server and not in this server.
> > > here is the filters that I use:
> > >
> > >
> > > =Fields!monthName.Value
> > > !=> > > Total
> > >
> > > Thanks
> > >
> > >
> >
> >
>|||Yes,It's working fine in the server with SP1.I willl let you know as soon as
I install SP1 and should the problem is solved.
Thanks
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:e9QjDfaCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> While there is no specific change for chart filters in SP1, there are some
> improvements to make chart processing more efficient. Also from your
> description, the same report with the same data works fine on the SP1
> server.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "ALI-R" <newbie@.microsoft.com> wrote in message
> news:exH0YqUCFHA.2960@.TK2MSFTNGP14.phx.gbl...
> > I haven't had the chance to install SP1 yet,Do you think it might be
> > relevant?
> > Thanks
> > "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> > news:%23vIDaCOCFHA.268@.TK2MSFTNGP10.phx.gbl...
> > > Does installing SP1 resolve it on the other server too?
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "ALI-R" <newbie@.microsoft.com> wrote in message
> > > news:OkIHP4KCFHA.1392@.tk2msftngp13.phx.gbl...
> > > > I got the following error when I try to luanch the report ,it is
> working
> > > on
> > > > another server with SP1 installed on it .Could it be the
problem?(Not
> > > havinf
> > > > Sp1)
> > > >
> > > > The processing of filter expression for the chart "MyChart"
cannot
> > be
> > > > performed. The comparison failed
> > > > I removed the filter and it works,why this filter is working in the
> > other
> > > > server and not in this server.
> > > > here is the filters that I use:
> > > >
> > > >
> > > > =Fields!monthName.Value
> > > > !=> > > > Total
> > > >
> > > > Thanks
> > > >
> > > >
> > >
> > >
> >
> >
>

REPOST:Cannot find Snapshot 2005

Last week I made the following post...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Running Win 2003 & SQL 2005 on both machines.
I created a publication on serverA. I subscribed to it on serverB. I
received the error...
Command attempted:
E:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\REPLDATA\unc\unc\R99S-SQLA_DBMOTO_AS400 MASTER
FILES\20061206113840\APVENDP_2.sch
(Transaction sequence number: 0x000049A200000088002A00000000, Command
ID: 16)
Error messages:
The device is not ready.
Thinking that replication was attempting to access the snapshot
locally, I changed to the location of the snapshot in the subscription
to \\serverA\E$\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\REPLDATA\unc\unc\R99S-SQLA_DBMOTO_AS400 MASTER
FILES\20061206113840\APVENDP_2.sch
Note that the location of the snapshot is ....repldata\unc\unc\... in
the error message. I browsed to serverA & there is no
....repldata\unc\unc folder, just a ...repldata\unc folder, then the
folder R99S-SQLA_DBMOTO_AS400 MASTER FILES.
Next I changed the location of the snapshot to reflect where the
subscription was looking ...repldata\unc\unc & now the subscription is
initialized & receiving transactions from the publisher.
With all that said....does anyone know why I had to jump through these
back flips to get replication to work when I did not deviate from the
defaults?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hilary posted the following
It sounds like your default snapshot share location was not specified
correctly. I think it was the double unc which gave you this error
message.
I take it this is a pull, if that is the case you don't need to use a
UNC.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This tells me what the problem is but does not give me any directing in
resolution.
How do I fix this? I do not want to have to do this for every
publication/subscription I create.
AHIA,
Larry...
Larry, you can change the default snapshot location for your publisher from
SSMS by Right-click Replication folder->Distributor Properties->Select the
Publishers page on the left pane->Clink on the ... button for the publisher
you want to change on the right pane->Modify the Default Snapshot Folder
field in the pop-up dialogue box and hit Ok->Hit Ok *again* on the
Distributor Properties dialog box to commit the change. Note that the change
will not be picked up until the next snapshot being generated.
Hope that helps,
-Raymond
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1166644241.462462.124840@.73g2000cwn.googlegro ups.com...
> Last week I made the following post...
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Running Win 2003 & SQL 2005 on both machines.
>
> I created a publication on serverA. I subscribed to it on serverB. I
> received the error...
> Command attempted:
> E:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\REPLDATA\unc\unc\R99S-SQLA_DBMOTO_AS400 MASTER
> FILES\20061206113840\APVENDP_2.sch
> (Transaction sequence number: 0x000049A200000088002A00000000, Command
> ID: 16)
>
> Error messages:
> The device is not ready.
>
> Thinking that replication was attempting to access the snapshot
> locally, I changed to the location of the snapshot in the subscription
> to \\serverA\E$\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\REPLDATA\unc\unc\R99S-SQLA_DBMOTO_AS400 MASTER
> FILES\20061206113840\APVENDP_2.sch
>
> Note that the location of the snapshot is ....repldata\unc\unc\... in
>
> the error message. I browsed to serverA & there is no
> ...repldata\unc\unc folder, just a ...repldata\unc folder, then the
> folder R99S-SQLA_DBMOTO_AS400 MASTER FILES.
>
> Next I changed the location of the snapshot to reflect where the
> subscription was looking ...repldata\unc\unc & now the subscription is
>
> initialized & receiving transactions from the publisher.
>
> With all that said....does anyone know why I had to jump through these
>
> back flips to get replication to work when I did not deviate from the
> defaults?
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Hilary posted the following
> It sounds like your default snapshot share location was not specified
> correctly. I think it was the double unc which gave you this error
> message.
> I take it this is a pull, if that is the case you don't need to use a
> UNC.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> This tells me what the problem is but does not give me any directing in
> resolution.
>
> How do I fix this? I do not want to have to do this for every
> publication/subscription I create.
>
> AHIA,
> Larry...
>

Repost: sql7 maintenance jobs hang

Hi group,
the following has been posted and did not receive any response. In hope to
get some leads I am reposting it here.
we have a sql7 server,
Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86)
May 29 2003 15:21:25
Copyright (c) 1988-2002 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
For a while now, it has been seeing hanging db maintenance jobs. The jobs
are initiated, but never goes beyond that -- the maintenance task is not
done before the hanging of the job. EM shows that the jobs are running but
loses the ability of managing them. One needs to end the processes with the
windows task manager. When manually initiated, the jobs can run through.
The jobs are not necessarily the same(different days can have different jobs
experiencing the problem, some can be the same), but all came from db
maintenance plan. A job hung yesterday may not hang today. Recreating the
db maint plan does not solve the problem.
Any suggestions are appreciated.
QuentinQuentin
Are you using the repair minor errors option? That tends
to cause problems in maint plans.
Any other problems on the server, I had a similar problem
and it was being caused by another process clashing with
the checkpoint process, but that eventually killed the
whole system.
Regards
John|||John,
thanks for the response.
The repair minor errors option is not being used. We are aware of that
problem.
We are trying to identify other problems on the server but came out empty
handed so far.
Quentin
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message
news:003201c3a86e$ccafad40$a301280a@.phx.gbl...
> Quentin
> Are you using the repair minor errors option? That tends
> to cause problems in maint plans.
> Any other problems on the server, I had a similar problem
> and it was being caused by another process clashing with
> the checkpoint process, but that eventually killed the
> whole system.
> Regards
> John

Repost for discussion on the error of SQLNCLI.1

Hi There,

I still got the following error:

OLE DB error: OLE DB or ODBC error: Could not locate registry entry for OLE DB provider 'SQLNCLI.1'.; 42000; OLE DB error trace [Non-interface error: Provider not registered.].; 01000.

I am running sql 2005 sp2, and the error happens when I try to drop one of attribute in my dimension table to the cube browser inside AS 2005, for example, I have one dimension call Customer with two attribute customercode and customername, along with fact table with sales amount, and I can drop customercode attribute into the cube browser without any problem, display cross join correctly with customercode as rows and sales amount.

But when I drop customername attribute into it, it gave me the above error, is this the bug? I did the .udl file to test the SNAC and everything works, I can connect to the data source using SNAC.

Running sql profiler againist AS 2005 showing same error. I did have mutiple data sources, but one DSV in the project.

Any other advice?

Thanks

Don

Are you using a ROLAP dimension? If so do you have the SQL native client installed on the server?|||

Hi Darren,

Thanks for the reply, no, I am not using rolap, everything is molap. sql native client is installed since other attribute works fine when dropping to the cube browser. This just drives me nuts.

Thanks for any pointer.

Don

|||Sorry, but that was really the only reason I could think of that browsing a cube would try to access the SQLNCLI.1 (SQL Native client) provider. If you are only using MOLAP storage it should only need the MSOLAP OLE DB provider.|||

Thanks Darren for your help.

All my data sources connect to SQL 2000 databases in another server, is this going to be the issue?

|||

Also here is the MDX query I capture from Profiler for the error message, notcie OPENROWSET(N'SQLNCLI.1',N'',N'SELECT is used:

SELECT SUM ( [FactPhysicianProcedure].[FactPhysicianProcedureTotalCharge0_0] ) AS [FactPhysicianProcedureTotalCharge0_0],
SUM ( [FactPhysicianProcedure].[FactPhysicianProcedureBalance0_6] ) AS [FactPhysicianProcedureBalance0_6],COUNT_BIG ( [FactPhysicianProcedure].[FactPhysicianProcedure0_7] )
AS [FactPhysicianProcedure0_7],[dbo_MisService_6].[dbo_MisServiceName1_0] AS [dbo_MisServiceName1_0] FROM
(SELECT [TotalCharge] AS [FactPhysicianProcedureTotalCharge0_0],[Balance] AS
[FactPhysicianProcedureBalance0_6],1 AS [FactPhysicianProcedure0_7],[InptService] AS [FactPhysicianProcedureInptService0_8] FROM
(SELECT w.OperSurgeon, u.AccountNumber, w.OperProcSeqNoAbsPat AS OperProcSeqNo, w.OperProc, CAST(o.Drg AS varchar(4)) AS Drg, u.Age, u.DisMonth,
u.Sex, u.Zip_PostalCode, g.InptService, u.FinancialClass, v.AdmitPhysMnemonic, g.PtStatus, u.DisDate, u.DisYear, u.DisQuarter,u.DisMonth AS Month, DATEPART(day, u.DisDate) AS DisDay,
g.TotalCharge, u.LOS, g.TotalInsExpReimb, g.TotalInsRcpt, g.TotalCost, g.TotalInsAdj, g.Balance FROM dbo.TSG_PatientInformation AS u INNER JOIN
dbo.TSG_Procedures AS w ON u.UrnABS = w.UrnABS INNER JOIN dbo.TSG_Physicians AS v ON u.UrnABS = v.UrnABS INNER JOIN dbo.TSG_DrgData AS o ON u.UrnABS = o.UrnABS INNER JOIN dbo.TSG_BarAccountData AS g ON u.UrnABS = g.UrnABS) AS [FactPhysicianProcedure]) AS [FactPhysicianProcedure],

OPENROWSET(N'SQLNCLI.1',N'',N'SELECT [Name] AS [dbo_MisServiceName1_0],[MnemonicMISSVCDICT]
AS [dbo_MisServiceMnemonicMISSVCDICT1_1]
FROM [dbo].[MisService]') AS [dbo_MisService_6] WHERE (([FactPhysicianProcedure].[FactPhysicianProcedureInptService0_8]
=[dbo_MisService_6].[dbo_MisServiceMnemonicMISSVCDICT1_1]))
GROUP BY [dbo_MisService_6].[dbo_MisServiceName1_0]

Repost for discussion on the error of SQLNCLI.1

Hi There,

I still got the following error:

OLE DB error: OLE DB or ODBC error: Could not locate registry entry for OLE DB provider 'SQLNCLI.1'.; 42000; OLE DB error trace [Non-interface error: Provider not registered.].; 01000.

I am running sql 2005 sp2, and the error happens when I try to drop one of attribute in my dimension table to the cube browser inside AS 2005, for example, I have one dimension call Customer with two attribute customercode and customername, along with fact table with sales amount, and I can drop customercode attribute into the cube browser without any problem, display cross join correctly with customercode as rows and sales amount.

But when I drop customername attribute into it, it gave me the above error, is this the bug? I did the .udl file to test the SNAC and everything works, I can connect to the data source using SNAC.

Running sql profiler againist AS 2005 showing same error. I did have mutiple data sources, but one DSV in the project.

Any other advice?

Thanks

Don

Are you using a ROLAP dimension? If so do you have the SQL native client installed on the server?|||

Hi Darren,

Thanks for the reply, no, I am not using rolap, everything is molap. sql native client is installed since other attribute works fine when dropping to the cube browser. This just drives me nuts.

Thanks for any pointer.

Don

|||Sorry, but that was really the only reason I could think of that browsing a cube would try to access the SQLNCLI.1 (SQL Native client) provider. If you are only using MOLAP storage it should only need the MSOLAP OLE DB provider.|||

Thanks Darren for your help.

All my data sources connect to SQL 2000 databases in another server, is this going to be the issue?

|||

Also here is the MDX query I capture from Profiler for the error message, notcie OPENROWSET(N'SQLNCLI.1',N'',N'SELECT is used:

SELECT SUM ( [FactPhysicianProcedure].[FactPhysicianProcedureTotalCharge0_0] ) AS [FactPhysicianProcedureTotalCharge0_0],
SUM ( [FactPhysicianProcedure].[FactPhysicianProcedureBalance0_6] ) AS [FactPhysicianProcedureBalance0_6],COUNT_BIG ( [FactPhysicianProcedure].[FactPhysicianProcedure0_7] )
AS [FactPhysicianProcedure0_7],[dbo_MisService_6].[dbo_MisServiceName1_0] AS [dbo_MisServiceName1_0] FROM
(SELECT [TotalCharge] AS [FactPhysicianProcedureTotalCharge0_0],[Balance] AS
[FactPhysicianProcedureBalance0_6],1 AS [FactPhysicianProcedure0_7],[InptService] AS [FactPhysicianProcedureInptService0_8] FROM
(SELECT w.OperSurgeon, u.AccountNumber, w.OperProcSeqNoAbsPat AS OperProcSeqNo, w.OperProc, CAST(o.Drg AS varchar(4)) AS Drg, u.Age, u.DisMonth,
u.Sex, u.Zip_PostalCode, g.InptService, u.FinancialClass, v.AdmitPhysMnemonic, g.PtStatus, u.DisDate, u.DisYear, u.DisQuarter,u.DisMonth AS Month, DATEPART(day, u.DisDate) AS DisDay,
g.TotalCharge, u.LOS, g.TotalInsExpReimb, g.TotalInsRcpt, g.TotalCost, g.TotalInsAdj, g.Balance FROM dbo.TSG_PatientInformation AS u INNER JOIN
dbo.TSG_Procedures AS w ON u.UrnABS = w.UrnABS INNER JOIN dbo.TSG_Physicians AS v ON u.UrnABS = v.UrnABS INNER JOIN dbo.TSG_DrgData AS o ON u.UrnABS = o.UrnABS INNER JOIN dbo.TSG_BarAccountData AS g ON u.UrnABS = g.UrnABS) AS [FactPhysicianProcedure]) AS [FactPhysicianProcedure],

OPENROWSET(N'SQLNCLI.1',N'',N'SELECT [Name] AS [dbo_MisServiceName1_0],[MnemonicMISSVCDICT]
AS [dbo_MisServiceMnemonicMISSVCDICT1_1]
FROM [dbo].[MisService]') AS [dbo_MisService_6] WHERE (([FactPhysicianProcedure].[FactPhysicianProcedureInptService0_8]
=[dbo_MisService_6].[dbo_MisServiceMnemonicMISSVCDICT1_1]))
GROUP BY [dbo_MisService_6].[dbo_MisServiceName1_0]