ASE ODBC 12.5 Driver has problem with SQLServer 8.0 DTS: HELP!

Hi,

On one side, I have a Sybase 12.5 32 bits Server running on AIX 5.1
(maintenance level 3). On the other, I've got W2000 5.00.2195 (SP2)
with SQL Server Standard Edition, Product Version 8.00.534 (SP2),
having installed MDAC 2.6.

I connect to the Sybase 12.5 database using Merant ASE ODBC driver for
Sybase 12.5, and using the Microsoft OLE DB Provider for SQL Server
that comes with this SQLServer version.

I try to pump over data from Sybase to SQLServer to one table at a
SQLServer user database, using a package containing a select statement
on a View on the Sybase Server side, using an ODBC 12.5 System DSN
pointing to the Sybase server. All privileges are set correctly on
either side and the ODBC datasource test gives an 'OK' on trying to
reach the Sybase Server.

When I do PREVIEW, I get a resultset alright, however, when I actually
run the package as a scheduled job, its keeps on running infinitely
until manually killed. No data at all is inserted in the the SQLServer
table.

Strange thing is, the same processes is running without any
complications on a W2000 5.00.2195 (SP3), MDAC 2.7 system, with the
same SQLServer connecting to the same Sybase Server but using Merant
ASE ODBC 12.0 instead of ODBC 12.5.

How come?

Any help will be greatly appreciated.

Martijn RutteSame permissions for the SQL Server Agent account ?

http://support.microsoft.com/?kbid=269074

--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Martijn Rutte" <opales@.zonnet.nl> wrote in message
news:80634782.0311110348.6e386e95@.posting.google.c om...
> Hi,
> On one side, I have a Sybase 12.5 32 bits Server running on AIX 5.1
> (maintenance level 3). On the other, I've got W2000 5.00.2195 (SP2)
> with SQL Server Standard Edition, Product Version 8.00.534 (SP2),
> having installed MDAC 2.6.
> I connect to the Sybase 12.5 database using Merant ASE ODBC driver for
> Sybase 12.5, and using the Microsoft OLE DB Provider for SQL Server
> that comes with this SQLServer version.
> I try to pump over data from Sybase to SQLServer to one table at a
> SQLServer user database, using a package containing a select statement
> on a View on the Sybase Server side, using an ODBC 12.5 System DSN
> pointing to the Sybase server. All privileges are set correctly on
> either side and the ODBC datasource test gives an 'OK' on trying to
> reach the Sybase Server.
> When I do PREVIEW, I get a resultset alright, however, when I actually
> run the package as a scheduled job, its keeps on running infinitely
> until manually killed. No data at all is inserted in the the SQLServer
> table.
> Strange thing is, the same processes is running without any
> complications on a W2000 5.00.2195 (SP3), MDAC 2.7 system, with the
> same SQLServer connecting to the same Sybase Server but using Merant
> ASE ODBC 12.0 instead of ODBC 12.5.
> How come?
> Any help will be greatly appreciated.
> Martijn Rutte|||Hi Allan,

Exactly the same permissions.

Martijn

"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message news:<uQQgTvEqDHA.360@.TK2MSFTNGP12.phx.gbl>...
> Same permissions for the SQL Server Agent account ?
> http://support.microsoft.com/?kbid=269074

'AS IS' Upgrade from SQL 2K to SQL 2K5

Hi ,
We are planning for â'in placeâ' SQL Upgrade from SQL 2000(Ent. Edition with
SP4) to SQL 2005 Ent.Edition with SP2 for
1)Replication Distribution Server that serves to PULL subscriptions.
2)One for the Subscriber Cluster (Active Passive)Server (its distribution
server already upgraded to SQL 2005)
We have gone through the requirements from Microsoft Technical Resource
Guide but looking if somebody had any issues or any advice other than Upgrade
Advisor reported before we move for Upgrade for both of above cases as some
people indicated they had issue with Password Policy , Appreciate your replyâ?¦My advice is to do functionality or, preferably, load testing in a dev\test
environment. As well as create a detailed project plan. I have run into a
lot of issues with upgrades but the clients that did throrough testing made
the fixes a part of the project plan instead of a Monday morning fire fight.
--
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"sacgar" <sacgar@.discussions.microsoft.com> wrote in message
news:8D9F1A4F-B591-4E8D-8F63-0ACF2D0ED91C@.microsoft.com...
> Hi ,
> We are planning for â'in placeâ' SQL Upgrade from SQL 2000(Ent. Edition with
> SP4) to SQL 2005 Ent.Edition with SP2 for
> 1)Replication Distribution Server that serves to PULL subscriptions.
> 2)One for the Subscriber Cluster (Active Passive)Server (its distribution
> server already upgraded to SQL 2005)
> We have gone through the requirements from Microsoft Technical Resource
> Guide but looking if somebody had any issues or any advice other than
> Upgrade
> Advisor reported before we move for Upgrade for both of above cases as
> some
> people indicated they had issue with Password Policy , Appreciate your
> replyâ?¦
>|||Please go through the below article as I have faced this issue , check if
applicable in your scenario...
Thanks
Ajay
"jason" <jason-r3move@.statisticsio.com> wrote in message
news:26E92972-53B2-4063-8D68-24B72C69FB94@.microsoft.com...
> My advice is to do functionality or, preferably, load testing in a
> dev\test environment. As well as create a detailed project plan. I have
> run into a lot of issues with upgrades but the clients that did throrough
> testing made the fixes a part of the project plan instead of a Monday
> morning fire fight.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
>
> "sacgar" <sacgar@.discussions.microsoft.com> wrote in message
> news:8D9F1A4F-B591-4E8D-8F63-0ACF2D0ED91C@.microsoft.com...
>> Hi ,
>> We are planning for 'in place' SQL Upgrade from SQL 2000(Ent. Edition
>> with
>> SP4) to SQL 2005 Ent.Edition with SP2 for
>> 1)Replication Distribution Server that serves to PULL subscriptions.
>> 2)One for the Subscriber Cluster (Active Passive)Server (its distribution
>> server already upgraded to SQL 2005)
>> We have gone through the requirements from Microsoft Technical Resource
>> Guide but looking if somebody had any issues or any advice other than
>> Upgrade
>> Advisor reported before we move for Upgrade for both of above cases as
>> some
>> people indicated they had issue with Password Policy , Appreciate your
>> reply.
>|||Sorry Missed this link earlier
Please go through this link for DB Move
http://support.microsoft.com/kb/314546/
Thanks
Ajay
"Ajay" <ajudba@.gmail.com> wrote in message
news:OsXeYk0ZIHA.4272@.TK2MSFTNGP05.phx.gbl...
> Please go through the below article as I have faced this issue , check if
> applicable in your scenario...
> Thanks
> Ajay
> "jason" <jason-r3move@.statisticsio.com> wrote in message
> news:26E92972-53B2-4063-8D68-24B72C69FB94@.microsoft.com...
>> My advice is to do functionality or, preferably, load testing in a
>> dev\test environment. As well as create a detailed project plan. I have
>> run into a lot of issues with upgrades but the clients that did throrough
>> testing made the fixes a part of the project plan instead of a Monday
>> morning fire fight.
>> --
>> Jason Massie
>> www: http://statisticsio.com
>> rss: http://feeds.feedburner.com/statisticsio
>>
>> "sacgar" <sacgar@.discussions.microsoft.com> wrote in message
>> news:8D9F1A4F-B591-4E8D-8F63-0ACF2D0ED91C@.microsoft.com...
>> Hi ,
>> We are planning for 'in place' SQL Upgrade from SQL 2000(Ent. Edition
>> with
>> SP4) to SQL 2005 Ent.Edition with SP2 for
>> 1)Replication Distribution Server that serves to PULL subscriptions.
>> 2)One for the Subscriber Cluster (Active Passive)Server (its
>> distribution
>> server already upgraded to SQL 2005)
>> We have gone through the requirements from Microsoft Technical Resource
>> Guide but looking if somebody had any issues or any advice other than
>> Upgrade
>> Advisor reported before we move for Upgrade for both of above cases as
>> some
>> people indicated they had issue with Password Policy , Appreciate your
>> reply.
>>
>

AS connection problems from Excel

I have problems to create connections to some of my cubes from Excel.

Configuration

Client- XP professional with Excel (2007, B2TR) and SQL 2005 SP2 TR client part's installed.

Server - Windows 2003 R2 with SQL AS 2005 SP2 TR.

Logged in as administrator with same password on client as server.

There are no rules configured for any of my databases.

When I try to create a new Analysis connection from Excel there is no cubes in the list of available cubes for some of my databases.

It works great for two om my databes but not for the others. I have compared my databases but I can't find anything that is different. And it works great to browse all my cubes from SQl Server BI Development Studio from my client.

Any idea?

Thanks,
Christer

If the cubes are deployed and processed, then you suppose to see it in the Excel 2007 beta 2. Can you be more specific in your question, I might can help as I am using the same configuration you have.

IMRAN

Arithmetic overflow error converting expression to data type int.

Hello, I'm using SQL Server 7.0 (SP2) for my distributor and many subscribers. It seems that when I replicate using my subscribers, some of them hit the error "Arithmetic overflow error converting expression to data type int". However, I realised that after waiting for a while before replicating now, it seems okay. Anybody can advice how I can prevent this from happening? Thanks!Refer to this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307533&gssnb=1) to fix the issue.

Arithmetic overflow

Hello.
On one my box (Win2k + SP2, MSSQL 2000 EE + SP2) I have some problem.
Suddenly i became to recive error "Arithmetic overflow occurred." Even if i
run "use db".
I haven't any error in logs.
I will be glad any suggestions.
--
Dmitry Burtsev [burtsev@.removethis.km.ru]Hi,Dima
Let's start with why don't you apply SP3 yet?
What are you doing when you get the error? Please show us your query,table
structutre.
"Burtsev Dmitry" <burtsev@.removethispart.km.ru> wrote in message
news:eC4sbqT0EHA.1188@.tk2msftngp13.phx.gbl...
> Hello.
> On one my box (Win2k + SP2, MSSQL 2000 EE + SP2) I have some problem.
> Suddenly i became to recive error "Arithmetic overflow occurred." Even if
i
> run "use db".
> I haven't any error in logs.
> I will be glad any suggestions.
>
> --
> Dmitry Burtsev [burtsev@.removethis.km.ru]
>
>

Arithmetic overflow

Hello.
On one my box (Win2k + SP2, MSSQL 2000 EE + SP2) I have some problem.
Suddenly i became to recive error "Arithmetic overflow occurred." Even if i
run "use db".
I haven't any error in logs.
I will be glad any suggestions.
Dmitry Burtsev [burtsev@.removethis.km.ru]
Hi,Dima
Let's start with why don't you apply SP3 yet?
What are you doing when you get the error? Please show us your query,table
structutre.
"Burtsev Dmitry" <burtsev@.removethispart.km.ru> wrote in message
news:eC4sbqT0EHA.1188@.tk2msftngp13.phx.gbl...
> Hello.
> On one my box (Win2k + SP2, MSSQL 2000 EE + SP2) I have some problem.
> Suddenly i became to recive error "Arithmetic overflow occurred." Even if
i
> run "use db".
> I haven't any error in logs.
> I will be glad any suggestions.
>
> --
> Dmitry Burtsev [burtsev@.removethis.km.ru]
>
>

Arithmetic overflow

Hello.
On one my box (Win2k + SP2, MSSQL 2000 EE + SP2) I have some problem.
Suddenly i became to recive error "Arithmetic overflow occurred." Even if i
run "use db".
I haven't any error in logs.
I will be glad any suggestions.
Dmitry Burtsev [burtsev@.removethis.km.ru]Hi,Dima
Let's start with why don't you apply SP3 yet?
What are you doing when you get the error? Please show us your query,table
structutre.
"Burtsev Dmitry" <burtsev@.removethispart.km.ru> wrote in message
news:eC4sbqT0EHA.1188@.tk2msftngp13.phx.gbl...
> Hello.
> On one my box (Win2k + SP2, MSSQL 2000 EE + SP2) I have some problem.
> Suddenly i became to recive error "Arithmetic overflow occurred." Even if
i
> run "use db".
> I haven't any error in logs.
> I will be glad any suggestions.
>
> --
> Dmitry Burtsev [burtsev@.removethis.km.ru]
>
>

Are there limitations to OLAP in Excel?

Hi,

Now, I use Analysis Services 2005 and Excel 2003 SP2 to deploy my OLAP model.

In Excel sheet, when creating a pivot table based on a Cube in Analysis Services, everything appears to work until I add a fourth dimension to the pivot table. Once I do that, I get a message that says "Running OLAP Query...(Press Esc to cancel)" so I must wait for a long time (about 5 minutes) to get the result. But while browsing the same data dimensions in Analysis Services Window, everything appears immediately.

Any ideas?

Best Regards!

You might qualify the question to read: "Are there limitations to using AS 2005 cubes in Excel 2003?"

Choosing client for SSAS 2005: Excel 2003 or Excel 2007

By Ramunas Balukonis

After we migrated Analysis Services from 2000 to 2005 we discovered that the same (or analogous) queries against SSAS 2005 runs even slower than AS 2000. Our users used MS Excel 2003 as front end on AS 2005. After some time I installed MS Excel 2007. Then I tried to do the same Pivot Table actions on both Excel versions (2003 and 2007): make Pivot Table from Advenure Works database placing days of [Date].[Calendar] [July 2003] and [August 2003] on rows, [Mountain-200 Silver, 38] and [Mountain-200 Silver, 42] from product [Product].[categories] on columns and [Sales Amount] as facts

Excel 2003 generates cumbersome MDX wits lots of except:

...

Excel 2007 generates elegant MDX:

...

The 1’st query from Excel 2003 runs 5 times longer!

After some time I gathered statistics from profiler and querylog. The results are as follows:

Avg MDX text length (Excel 2003): 2403
Avg MDX text length (Excel 2007): 1567
Avg query duration (Excel 2003): 507 ms
Avg query duration (Excel 2007): 96 ms

|||Thanks Ramunas!
Did you try to use the browser in Analysis Services or the Reporting Services to query your OLAP data . In my opinion, the queried time of using two ways above is better than the time of using Excel pivot table.
Could you explain me the reason why?

|||

Yeah, Excel 2003 is horrible with OLAP. It's the MDX issue, it does tons of EXCEPTS(), etc. Instead of scripting what it wants in the pivottable, it scripts what it doesn't want. Not sure how this ever got passed.

For your last reply, you will be hitting cache if you run from Excel, then run the same query somewhere else. You would have to execute the ClearCache command after every MDX statement for a true test. Or could be a network slowup if your using Excel externally (off the server) and running Management Studio on the server directly, for example.

Are there limitations to OLAP in Excel?

Hi,

Now, I use Analysis Services 2005 and Excel 2003 SP2 to deploy my OLAP model.

In Excel sheet, when creating a pivot table based on a Cube in Analysis Services, everything appears to work until I add a fourth dimension to the pivot table. Once I do that, I get a message that says "Running OLAP Query...(Press Esc to cancel)" so I must wait for a long time (about 5 minutes) to get the result. But while browsing the same data dimensions in Analysis Services Window, everything appears immediately.

Any ideas?

Best Regards!

You might qualify the question to read: "Are there limitations to using AS 2005 cubes in Excel 2003?"

Choosing client for SSAS 2005: Excel 2003 or Excel 2007

By Ramunas Balukonis

After we migrated Analysis Services from 2000 to 2005 we discovered that the same (or analogous) queries against SSAS 2005 runs even slower than AS 2000. Our users used MS Excel 2003 as front end on AS 2005. After some time I installed MS Excel 2007. Then I tried to do the same Pivot Table actions on both Excel versions (2003 and 2007): make Pivot Table from Advenure Works database placing days of [Date].[Calendar] [July 2003] and [August 2003] on rows, [Mountain-200 Silver, 38] and [Mountain-200 Silver, 42] from product [Product].[categories] on columns and [Sales Amount] as facts

Excel 2003 generates cumbersome MDX wits lots of except:

...

Excel 2007 generates elegant MDX:

...

The 1’st query from Excel 2003 runs 5 times longer!

After some time I gathered statistics from profiler and querylog. The results are as follows:

Avg MDX text length (Excel 2003): 2403
Avg MDX text length (Excel 2007): 1567
Avg query duration (Excel 2003): 507 ms
Avg query duration (Excel 2007): 96 ms

|||Thanks Ramunas!
Did you try to use the browser in Analysis Services or the Reporting Services to query your OLAP data . In my opinion, the queried time of using two ways above is better than the time of using Excel pivot table.
Could you explain me the reason why?

|||

Yeah, Excel 2003 is horrible with OLAP. It's the MDX issue, it does tons of EXCEPTS(), etc. Instead of scripting what it wants in the pivottable, it scripts what it doesn't want. Not sure how this ever got passed.

For your last reply, you will be hitting cache if you run from Excel, then run the same query somewhere else. You would have to execute the ClearCache command after every MDX statement for a true test. Or could be a network slowup if your using Excel externally (off the server) and running Management Studio on the server directly, for example.