"SQL Everywhere" is a Sybase trademark

It's all well and good that Microsoft has finally entered the well-established mobile database market (the market that iAnywhere Solution's SQL Anywhere product current *owns* by a wide margin). However, it should be noted that "SQL Everywhere" is a Sybase trademark. For confirmation of this fact, see http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.mro12.6.mro126ig/html/mro126ig/legal.htm

For confirmation of the fact that SQL Anywhere owns the mobile database market, note that it is the database of choice for the 500,000 mobile devices that will be used in the 2010 US Census; see http://www.internetadsales.com/modules/news/article.php?storyid=7347

Breck

The full name of the new mobile db is SQL Server Everywhere Edition, and I don't see that in the list you're linking.

Plus, wouldn't you think that a company like Microsoft has done some research before they decide on their product names?

|||

"Plus, wouldn't you think that a company like Microsoft has done some research before they decide on their product names?"

http://seattletimes.nwsource.com/html/businesstechnology/2002397450_microvista23.html

By naming the next version of Windows "Vista," Microsoft may have stepped on the toes of another software company just down the road in Redmond.

So, no, or: When an 800-lb gorilla has got to go, he doesn't ask where's the restroom, he just goes!

Whois vista.com?

Registrant:
CommunityIQ
11241 Willows Road
Redmond, WA 98052
US
Registrar: DOMAINBANK
Domain Name: VISTA.COM
Created on: 02-NOV-94
Expires on: 01-NOV-14
Last Updated on: 27-OCT-05
Administrative, Technical Contact:
Admin, Domain ***@.VISTA.COM
vista.com
11241 Willows Road
Redmond, WA 98052
US
3609208478

'She said the company filed for trademark protection of the words "Windows" and "Vista" used together. ..."The name Vista is commonly used by a variety of companies in a variety of industries," she said. "We are only using the word Vista paired with our trademark Windows so the two together - 'Windows Vista' - ...

If that's MS's stance, then it should have no problem with "Linux Windows". After all,
Windows is used by a variety of ... (yada-yada-yada).

"Attempted to read or write protected memory error" in SSIS

I'm trying to import data from a Sybase ASE 12.0 database called "OurTestDatabase" into MS SQL Server 2005. I started SSIS Wizard and indicated "Sybase ASE OLEDB Provider" as a source and SQL Native Client as the target. I'm gettign the following error message:

--

Cannot get supported data types from the database connection

"Provider=Sybase.ASEOLDEDBProvider;Password=;Persist Security Info=True;User ID=sa;Data Source=sybase;Initial Catalog=OurTestDatabase"

Additional information

|_ Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Data)

--

The same data source worked with DTS when we thought we'd convert to MS SQL Server 2000. Is this a bug in SSIS? What can be done? Using ".Net Framework Provider for ODBC" is not a good option because this doesn't allow me to choose any tables from the Sybase source.

Any help is greatly appreciated.

Hi,

Did you get the chance ti figure out what was the problem. I do get the similar error while accessing AS400 database.

its fail in :

// Summary:

// Fixes any errors identified during design-time validation that result in

// the component returning Microsoft.SqlServer.Dts.Pipeline.Wrapper.DTSValidationStatus.VS_NEEDSNEWMETADATA.

void ReinitializeMetaData();

where its suppose to identify the errors in metadata it seems.

I still am investigating my metadata for AS400 tables.

Hope This helps you.

|||

I'm not sure that we can help debug in detail - we have not tested the Sybase drivers and don't know what behaviour they typically report.

However, most likely the issue arises because the Sybase provider does not support methods we are calling to get data types for columns. I have seen similar issues with the Sybase provider and linked servers. You may want to check with Sybase to see if they have tested their provider with SSIS.

The .Net provider for ODBC may be a workaround in terms of getting column level metadata. You are right that in the present version you cannot browse tables or views. However, although the provider does not list tables, it is still possible to access them, but you need to write the query yourself.

Donald

|||The same error came up when I used the ODBC drivers to access Sybase ASE|||

That sounds like a Sybase issue, then. Have you checked with them, or tested the same calls to the driver with other clients?

Donald

"Attempted to read or write protected memory error" in SSIS

I'm trying to import data from a Sybase ASE 12.0 database called "OurTestDatabase" into MS SQL Server 2005. I started SSIS Wizard and indicated "Sybase ASE OLEDB Provider" as a source and SQL Native Client as the target. I'm gettign the following error message:

--

Cannot get supported data types from the database connection

"Provider=Sybase.ASEOLDEDBProvider;Password=;Persist Security Info=True;User ID=sa;Data Source=sybase;Initial Catalog=OurTestDatabase"

Additional information

|_ Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Data)

--

The same data source worked with DTS when we thought we'd convert to MS SQL Server 2000. Is this a bug in SSIS? What can be done? Using ".Net Framework Provider for ODBC" is not a good option because this doesn't allow me to choose any tables from the Sybase source.

Any help is greatly appreciated.

Hi,

Did you get the chance ti figure out what was the problem. I do get the similar error while accessing AS400 database.

its fail in :

// Summary:

// Fixes any errors identified during design-time validation that result in

// the component returning Microsoft.SqlServer.Dts.Pipeline.Wrapper.DTSValidationStatus.VS_NEEDSNEWMETADATA.

void ReinitializeMetaData();

where its suppose to identify the errors in metadata it seems.

I still am investigating my metadata for AS400 tables.

Hope This helps you.

|||

I'm not sure that we can help debug in detail - we have not tested the Sybase drivers and don't know what behaviour they typically report.

However, most likely the issue arises because the Sybase provider does not support methods we are calling to get data types for columns. I have seen similar issues with the Sybase provider and linked servers. You may want to check with Sybase to see if they have tested their provider with SSIS.

The .Net provider for ODBC may be a workaround in terms of getting column level metadata. You are right that in the present version you cannot browse tables or views. However, although the provider does not list tables, it is still possible to access them, but you need to write the query yourself.

Donald

|||The same error came up when I used the ODBC drivers to access Sybase ASE|||

That sounds like a Sybase issue, then. Have you checked with them, or tested the same calls to the driver with other clients?

Donald