Cursor type changed?

Hi,
I just posted this on sqlserver.connect since I'm not sure where it belongs.
So here goes.
We've recently began migrating to SQL 2005 from SQL 7 and have had a few
issues.
Right now we have an issue when trying to logon to the server through our
application.
'sa' login works from our application but when we try to logon as a user we
get:
"[ODBC SQL Server Driver]Cursor type changed"
I have tried logging on through Query Analyzer and that works fine for all
users so it should not be a permission issue.
I've tried to search the web high and low without really finding a solution
or cause for this error. I've seen a few a reports of people having the
same- or similar problems but no solutions.
I'd be greatful for any tips you guys and girls might have.
Thanks in advance and have a great wend.
Regards,
Tony HolopainenThis message is informational, not an error. Perhaps the application code
is treating the message as an error simply because it's unexpected.
Are you using ADO or calling ODBC directly? Do the get this message during
login or when you run a query? I wouldn't expect this to be security
related unless different results are returned depending on the user logging
in.
Hope this helps.
Dan Guzman
SQL Server MVP
"TonyH" <tony@.nospam.com> wrote in message
news:e8OWomAnGHA.4604@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I just posted this on sqlserver.connect since I'm not sure where it
> belongs. So here goes.
> We've recently began migrating to SQL 2005 from SQL 7 and have had a few
> issues.
> Right now we have an issue when trying to logon to the server through our
> application.
> 'sa' login works from our application but when we try to logon as a user
> we get:
> "[ODBC SQL Server Driver]Cursor type changed"
> I have tried logging on through Query Analyzer and that works fine for all
> users so it should not be a permission issue.
> I've tried to search the web high and low without really finding a
> solution or cause for this error. I've seen a few a reports of people
> having the same- or similar problems but no solutions.
> I'd be greatful for any tips you guys and girls might have.
> Thanks in advance and have a great wend.
> Regards,
> Tony Holopainen
>

cube cretion & report accessing it

Hi,

I’m new with SSAS but I had know how to create a cube and I could able to connect to SSAS database and view the cube I had created. But I do not understand if some Reporting tool wanted to access the data from cube, will it connect cube and do the manipulation as per the report requirement or I have to do create a cube specific to the each report.

Another clarification if I create a cube on show flick schema will that be any problem in accessing the data.

This are the very basic questions but I need to get more clarity

Thank you

Regarding cubes & reports, you should be able to create a single cube and use it across your reports. Each report would have one or more MDX queries associated with it to provide the data for the report. Depending on the tool you use, the MDX may or may not be easily accessible as the interface may provide a means of assembling the query without exposing the MDX to you.

Regarding the other, I'm not sure what "show flick shema" is.

Thanks,
Bryan

|||Thank you for this information !!!!!!!!!!!!!

Cube always shows the current time under "Processed".

I have an issue in Analysis Manager with regard to the "last time the cube
was processed". When I open Analysis Manager, connect to my Server, and
click on my database. I click on metadata and see under "Cubes" that one of
my cubes always shows the current time under "Processed".
I have three other cubes that show the correct time as to when they were
processed. My database and the cube in question have the same name...I
don't know if this is an issue.
Can anybody help?
Eric
Message posted via http://www.droptable.com"My database and the cube in question have the same name...I don't know
if this is an issue"
In a test AS 2000 database, I created a copy of an existing cube, giving
it the same name as the database. The "last processed time" of this cube
is correctly reported, and does not change with the current time. So
this doesn't seem to be an issue in all cases (may be in your case?).
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

CTRL-Z usage in SSRS

I have opened a connect issue for the CTRL Z handling in SSRS.

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=299431

Please vote on it so it get's fixed in 2008, I am tired of losing random changes because I hit CTRL-Z.

Thanks

BobP

I voted. Thanks Bob! |||

You got my vote!

|||I lost a dataset once after trying to undo a change in a single script line.

j00 got my vote.

CTP June Dev.Edition:TCP/IP protocol is disabled at default

I have tested Developer Edition CTP June but when I connect to remote SQL Server, "A connection was successfully established with the server, but then an error occurred during the pre-login handshake." error occured.
I find out TCP/IP protocol is disabled at default at CTP June. When you meet with same situation, try enable TCP/IP protocol being enabled on "SQL Server Configration Manager"

It's bug or by design?

Regards

Hajime GondoThis is in fact by design. As part of only making available services that you need we are defaulting the Developer Edition to not listen on TCP/IP.

-Euan|||Thanks Euan! I found topic "Network Protocols and Network Libraries".

But I can't accept this design. Bacause developer edition "must" (I think) functionaly works same as enterprise edition. If not, developer must search what is deffernt between Dev. and Ent.(such as me) This causes needless confusion.|||It does work the same as Ent and Std, the defaults are just different(this is the case with SSE as well). We provide a tool to flip the defaults.

-Euan|||It's nice that you will provide the tools. Question is, WHEN, we are waiting....|||There are 2 tools, the commandline version of setup allows much of this to be overriden and the surface area config tool allows you to flip al;l of these things asll, both have been in since the product RTM'd last year.|||

To install via the command line and turn TCP/IP on, specify the DISABLENETWORKPROTOCOLS command line parameter:

;--
; The DISABLENETWORKPROTOCOLS switch is used to disable network protocol for SQL Server instance.
; Set DISABLENETWORKPROTOCOLS = 0; for Shared Memory= On, Named Pipe= On, TCP= On
; Set DISABLENETWORKPROTOCOLS = 1; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= Off
; Set DISABLENETWORKPROTOCOLS = 2; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= On

; Note: DISABLENETWORKPROTOCOLS if not specified has the following defaults.
; Default value for SQL Server Express/Evaluation/Developer: DISABLENETWORKPROTOCOLS =1
; Default value for Enterprise/Standard /Workgroup: DISABLENETWORKPROTOCOLS =2

DISABLENETWORKPROTOCOLS=

To configure the TCP/IP after installation, you need to use the Surface Area Configuration tool that Euan mentioned. This blog entry describes it pretty well for SQLExpress - it applies equally well to other skus. ttp://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Hope this helps.

-Jeffrey

CTP June Dev.Edition:TCP/IP protocol is disabled at default

I have tested Developer Edition CTP June but when I connect to remote SQL Server, "A connection was successfully established with the server, but then an error occurred during the pre-login handshake." error occured.
I find out TCP/IP protocol is disabled at default at CTP June. When you meet with same situation, try enable TCP/IP protocol being enabled on "SQL Server Configration Manager"

It's bug or by design?

Regards

Hajime GondoThis is in fact by design. As part of only making available services that you need we are defaulting the Developer Edition to not listen on TCP/IP.

-Euan|||Thanks Euan! I found topic "Network Protocols and Network Libraries".

But I can't accept this design. Bacause developer edition "must" (I think) functionaly works same as enterprise edition. If not, developer must search what is deffernt between Dev. and Ent.(such as me) This causes needless confusion.|||It does work the same as Ent and Std, the defaults are just different(this is the case with SSE as well). We provide a tool to flip the defaults.

-Euan|||It's nice that you will provide the tools. Question is, WHEN, we are waiting....|||There are 2 tools, the commandline version of setup allows much of this to be overriden and the surface area config tool allows you to flip al;l of these things asll, both have been in since the product RTM'd last year.|||

To install via the command line and turn TCP/IP on, specify the DISABLENETWORKPROTOCOLS command line parameter:

;--
; The DISABLENETWORKPROTOCOLS switch is used to disable network protocol for SQL Server instance.
; Set DISABLENETWORKPROTOCOLS = 0; for Shared Memory= On, Named Pipe= On, TCP= On
; Set DISABLENETWORKPROTOCOLS = 1; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= Off
; Set DISABLENETWORKPROTOCOLS = 2; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= On

; Note: DISABLENETWORKPROTOCOLS if not specified has the following defaults.
; Default value for SQL Server Express/Evaluation/Developer: DISABLENETWORKPROTOCOLS =1
; Default value for Enterprise/Standard /Workgroup: DISABLENETWORKPROTOCOLS =2

DISABLENETWORKPROTOCOLS=

To configure the TCP/IP after installation, you need to use the Surface Area Configuration tool that Euan mentioned. This blog entry describes it pretty well for SQLExpress - it applies equally well to other skus. ttp://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Hope this helps.

-Jeffrey

csv file

how to set the connection string to connect a csv file with reporting
service.
TIA.
DonaldI have not used csv files, but you should be able to setup an ODBC datasource
with the text driver. You can then use this source to use your csv file as
table. I have successfully done this with txt files. You might need to
rename the files to be .txt versus .csv.
Good Luck
Stan
"Donald" wrote:
> how to set the connection string to connect a csv file with reporting
> service.
> TIA.
> Donald
>
>

CSV Exporting SSMSE (Text Identifier)

I just updated to SQL Express SP2 per this Feedback item:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=132806

But I don't see an option to use quoted identifiers. Is it not included in the Express version?

I thinnk that is set on a database level. (And the 'default' condition is [ ON ].)

To change:

ALTER DATABASE MyDatabase

SET QUOTED_IDENTIFIER ON