MS SQL Server 2005 64 bit CTP:[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o

I am facing a problem with SQL Server 2005 64-bit CTP June 2005 on Windows 2003 64 Bit.

When i try to connect to the SQL Server Instance using any of Windows/SQL Server Authentication from My Application using SQLOLEDB interfaces (From Win32 Code) it is not able to connect and throws following error:

"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."

When in the same code I use SQL Native Client (SQLNCLI), it is able to Create and Initialize the interfaces.

When i tried to research on this issue, i found out in Books Online SQL Server 2005 CTP June 2005. That this release only supports SQLNCLI and MDAC support has been removed for this release on 64 bit Windows.

The article says:
"SQL Native Client (SNAC) is available on the 64-bit platform. MDAC has been removed for this release."

Reference:
Books Online Microsoft SQL Server 2005 CTP June 2005
See Topic: "Differences Between 32-bit and 64-bit Editions of SQL Server 2005"

(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/e0556daa-19cb-4c08-af02-f542641365a5.htm)

Please let me know if any of you have similar problem. Is there any solution to this other than using SQLNCLI.

I did have similar issue that could not register several Yukon servers from one big brother server. After a little research, solution to the issue was Windows 2003 SP1.

Now, I am facing another issue which is deal with MDAC in 64 bit environment. I've got Win 2003 SP1 64bit and Yukon April CTP i64. One of developer trying to deal with distribute query against to an excel file, it returns an error

"The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered. "

I looked around and realized that we don't have much ODBC driver available from that 64 bit box. Only available drivers are SQL Native Client and SQL server.

I ran Component checker and it found MDAC2.8 SP2. I also tried to install Jet40 SP8 64 bit, but it say no install needed because there is a newer verion found on system. When I try to create a new data source, I don't have much selections but only two.

As you stated that we don't have much control on MDAC nor Jet40 at this stage. And I've been look for a workaround but no luck yet last two days.

I am keep looking and will post here to imform you if I find some thing.

Thanks
Sunny

|||Hi, Deepak,

Thank you for reporting the problem. Can you tell us:

- is your SQL Server 2005 a default instance or a named instance?
- How do you specify the server in your connection string (the server name, ".", "(local)", etc.)?
- What protocols are enabled on your SQL Server 2005 (TCP/IP, Named Pipes, Shared Memory)?

Thank you,
Peter|||

iam facing this error message kindly assit

Thank you

MS SQL Server 2005 64 bit CTP:[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o

I am facing a problem with SQL Server 2005 64-bit CTP June 2005 on Windows 2003 64 Bit.

When i try to connect to the SQL Server Instance using any of Windows/SQL Server Authentication from My Application using SQLOLEDB interfaces (From Win32 Code) it is not able to connect and throws following error:

"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."

When in the same code I use SQL Native Client (SQLNCLI), it is able to Create and Initialize the interfaces.

When i tried to research on this issue, i found out in Books Online SQL Server 2005 CTP June 2005. That this release only supports SQLNCLI and MDAC support has been removed for this release on 64 bit Windows.

The article says:
"SQL Native Client (SNAC) is available on the 64-bit platform. MDAC has been removed for this release."

Reference:
Books Online Microsoft SQL Server 2005 CTP June 2005
See Topic: "Differences Between 32-bit and 64-bit Editions of SQL Server 2005"

(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/e0556daa-19cb-4c08-af02-f542641365a5.htm)

Please let me know if any of you have similar problem. Is there any solution to this other than using SQLNCLI.

I did have similar issue that could not register several Yukon servers from one big brother server. After a little research, solution to the issue was Windows 2003 SP1.

Now, I am facing another issue which is deal with MDAC in 64 bit environment. I've got Win 2003 SP1 64bit and Yukon April CTP i64. One of developer trying to deal with distribute query against to an excel file, it returns an error

"The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered. "

I looked around and realized that we don't have much ODBC driver available from that 64 bit box. Only available drivers are SQL Native Client and SQL server.

I ran Component checker and it found MDAC2.8 SP2. I also tried to install Jet40 SP8 64 bit, but it say no install needed because there is a newer verion found on system. When I try to create a new data source, I don't have much selections but only two.

As you stated that we don't have much control on MDAC nor Jet40 at this stage. And I've been look for a workaround but no luck yet last two days.

I am keep looking and will post here to imform you if I find some thing.

Thanks
Sunny

|||Hi, Deepak,

Thank you for reporting the problem. Can you tell us:

- is your SQL Server 2005 a default instance or a named instance?
- How do you specify the server in your connection string (the server name, ".", "(local)", etc.)?
- What protocols are enabled on your SQL Server 2005 (TCP/IP, Named Pipes, Shared Memory)?

Thank you,
Peter|||

iam facing this error message kindly assit

Thank you

sql

MS SQL Server 2005 64 bit CTP:[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o

I am facing a problem with SQL Server 2005 64-bit CTP June 2005 on Windows 2003 64 Bit.

When i try to connect to the SQL Server Instance using any of Windows/SQL Server Authentication from My Application using SQLOLEDB interfaces (From Win32 Code) it is not able to connect and throws following error:

"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."

When in the same code I use SQL Native Client (SQLNCLI), it is able to Create and Initialize the interfaces.

When i tried to research on this issue, i found out in Books Online SQL Server 2005 CTP June 2005. That this release only supports SQLNCLI and MDAC support has been removed for this release on 64 bit Windows.

The article says:
"SQL Native Client (SNAC) is available on the 64-bit platform. MDAC has been removed for this release."

Reference:
Books Online Microsoft SQL Server 2005 CTP June 2005
See Topic: "Differences Between 32-bit and 64-bit Editions of SQL Server 2005"

(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/e0556daa-19cb-4c08-af02-f542641365a5.htm)

Please let me know if any of you have similar problem. Is there any solution to this other than using SQLNCLI.

I did have similar issue that could not register several Yukon servers from one big brother server. After a little research, solution to the issue was Windows 2003 SP1.

Now, I am facing another issue which is deal with MDAC in 64 bit environment. I've got Win 2003 SP1 64bit and Yukon April CTP i64. One of developer trying to deal with distribute query against to an excel file, it returns an error

"The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered. "

I looked around and realized that we don't have much ODBC driver available from that 64 bit box. Only available drivers are SQL Native Client and SQL server.

I ran Component checker and it found MDAC2.8 SP2. I also tried to install Jet40 SP8 64 bit, but it say no install needed because there is a newer verion found on system. When I try to create a new data source, I don't have much selections but only two.

As you stated that we don't have much control on MDAC nor Jet40 at this stage. And I've been look for a workaround but no luck yet last two days.

I am keep looking and will post here to imform you if I find some thing.

Thanks
Sunny

|||Hi, Deepak,

Thank you for reporting the problem. Can you tell us:

- is your SQL Server 2005 a default instance or a named instance?
- How do you specify the server in your connection string (the server name, ".", "(local)", etc.)?
- What protocols are enabled on your SQL Server 2005 (TCP/IP, Named Pipes, Shared Memory)?

Thank you,
Peter|||

iam facing this error message kindly assit

Thank you

MS SQL Script Optimisation

Still a bit of a newbie to SQL, I've written a solution to a problem but I'm sure there is a neater fix.

I have two tables,

Table 1 (sales) which indexes product_id, customers and the date when the customer bought the product.
contains the columns Prod_Id (int), Customers (char), DateNo (int)

Table 2 (products) contains a list of all products in the system
contains the columns Prod_Id(int), ProductDescription(char) and Price (int)

I want to display a list to the top 10 most popular products.
Listing their description, price and the number of times they have been purchased in 2006. Does not matter who bought them.

My current approach is:
----------------------

CREATE TABLE #temptable
(
Prod_IdINTNOT NULL,
CounterINTNOT NULL
)

INSERT INTO #temptable
SELECT TOP 10 WITH TIES Prod_Id, Count(*)
FROM Sales
WHERE DateNo >= '20060101'
AND DateNo < '20060516'
GROUP BY Prod_Id
ORDER BY COUNT(*) DESC;

SELECT t.Counter, p.ProductDescription, p.Price
FROM Products AS p, #temptable AS t
WHERE t.Prod_Id = p.Prod_Id;

DROP TABLE #temptable

---------------

Any help would be appriciated.
Thank you.I havent tested this, as I'm lasy, but it should give the same result but a bit faster as its not creating and dropping tables

SELECT TOP 10 WITH TIES p.ProductDescription, p.Price ,Count(s.Prod_Id)
FROM Sales as s
INNER JOIN Products AS p
ON s.Prod_Id = p.Prod_Id
WHERE s.DateNo >= '20060101'
AND s.DateNo < '20060516'
GROUP BY p.ProductDescription, p.Price
ORDER BY Count(s.Prod_Id) DESC

Hope it works

MS SQL 2005: DB Mirroring and Log Shipping

I am setting up a HA solution which incorporates both the DB Mirroring and Log Shipping with SQL Server 2005.

However I am running into a bit of a snag in configuring the mirror as the primary/inactive log shipped database.

From what I can tell one should be able to configure the mirror DB separately as a logged shipped database and when a mirror failover event happens the Log Shipping jobs should be able to come from whichever is the active DB.

According to all the documentation I have it is possible, however it is a bit fuzzy on the details. Is this a MS pipedream or Reality? Has anyone accomplished this?

Your input?I was able to figure it out.

Here is my solution. I welcome your comments.
Prerequistes: Mirroring Endpoints, 3/4 servers (primary/mirror/logship/Logship backup servers), SQL Server 2005

1. create a backup of the database to be mirrored logshipped
2. copy backup to both mirror server and log ship server
3. recover backup fully on mirror server
4. set up log shipping on the mirror server (initially disable backup job)
5. re-recover database in NORecovery mode
6. point mirror database at primary database
7. set up log shipping on the primary server (initially disable backup job)
8. re-recover database on primary database (Key! - I'm not sure why however)
9. point primary database to mirror database to initalize DB mirroring (also may setup a witness at this point)
10. setup log shipping on log ship server (initially disable copy and restore jobs)
11. ensure that all settings are working correctly and DB Mirroring is fully functional
12. Enable backup jobs and then copy and restore jobs for Log Shipping

What this accomplishes is a Mirrored database which also log ships from two locations (both the primary and the mirror db). Upon a mirror failover event the Mirror DB will continue logshipping

I am still testing this solution. Hopefull you can make some use of this information.

MS SQL 2005 Workgroup licensing question

Hi,
I am a bit confused about the licensing schemes for MS SQL.
There is a "Processor" licnese (about $4000) and a "Server +
User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
It says:
Processor Licensing Model. Under this model, a license is required for
each physical or virtual processor accessed by an operating system
environment running SQL Server. This license does not require any
device or user client access licenses (CALs).
Server plus Device CALs. Under this model, a server license is required
for each operating system environment running an instance of SQL
Server, as well as a CAL for each client device that accesses a system
running SQL Server.
Server plus User CALs. Under this model, a server license is required
for each operating system environment running an instance of SQL
Server, as well as a CAL for each user that accesses a system running
SQL Server.
If I am installing the MS SQL on one web server running Windows 2003
Server, accessible by corporate users over Internet, which licensing
model is suitable?
TIA.Calculate how many different users access the server. Not at once,
all together over time. Calculate the cost of that many CALs compared
to the per-processor price. You probably will end up with
per-processor pricing.
Roy Harvey
Beacon Falls, CT
On 26 Jul 2006 10:03:32 -0700, ashkaan57@.hotmail.com wrote:

>Hi,
>I am a bit confused about the licensing schemes for MS SQL.
>There is a "Processor" licnese (about $4000) and a "Server +
>User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
>It says:
>Processor Licensing Model. Under this model, a license is required for
>each physical or virtual processor accessed by an operating system
>environment running SQL Server. This license does not require any
>device or user client access licenses (CALs).
>Server plus Device CALs. Under this model, a server license is required
>for each operating system environment running an instance of SQL
>Server, as well as a CAL for each client device that accesses a system
>running SQL Server.
>Server plus User CALs. Under this model, a server license is required
>for each operating system environment running an instance of SQL
>Server, as well as a CAL for each user that accesses a system running
>SQL Server.
>If I am installing the MS SQL on one web server running Windows 2003
>Server, accessible by corporate users over Internet, which licensing
>model is suitable?
>TIA.|||The definitive answers to licensing questions are at:
http://www.microsoft.com/licensing/default.mspx
My take:
You may recall, that the processor license is required for
internet/intranet/extranet usage UNLESS all users will have a proper CAL.
(That even includes a single small query populating a small list box on a
web page.)
If your web site is restricted to company users only, and if all company
users that will be accessing SQL Server have an existing SQL Server CAL,
then I believe that you are covered. (Subject to verification with VL.) If
all company users do not have SQL Server CALs, then you most likely need a
processor license -or additional CALs.
I do not think that any non-company (or extranet) users would be included
without the processor license -unless, upon software audit, you can prove
the existence of CALs.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<ashkaan57@.hotmail.com> wrote in message
news:1153933412.130178.59290@.s13g2000cwa.googlegroups.com...
> Hi,
> I am a bit confused about the licensing schemes for MS SQL.
> There is a "Processor" licnese (about $4000) and a "Server +
> User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
> It says:
> Processor Licensing Model. Under this model, a license is required for
> each physical or virtual processor accessed by an operating system
> environment running SQL Server. This license does not require any
> device or user client access licenses (CALs).
> Server plus Device CALs. Under this model, a server license is required
> for each operating system environment running an instance of SQL
> Server, as well as a CAL for each client device that accesses a system
> running SQL Server.
> Server plus User CALs. Under this model, a server license is required
> for each operating system environment running an instance of SQL
> Server, as well as a CAL for each user that accesses a system running
> SQL Server.
> If I am installing the MS SQL on one web server running Windows 2003
> Server, accessible by corporate users over Internet, which licensing
> model is suitable?
> TIA.
>

MS SQL 2005 Workgroup licensing question

Hi,
I am a bit confused about the licensing schemes for MS SQL.
There is a "Processor" licnese (about $4000) and a "Server +
User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
It says:
Processor Licensing Model. Under this model, a license is required for
each physical or virtual processor accessed by an operating system
environment running SQL Server. This license does not require any
device or user client access licenses (CALs).
Server plus Device CALs. Under this model, a server license is required
for each operating system environment running an instance of SQL
Server, as well as a CAL for each client device that accesses a system
running SQL Server.
Server plus User CALs. Under this model, a server license is required
for each operating system environment running an instance of SQL
Server, as well as a CAL for each user that accesses a system running
SQL Server.
If I am installing the MS SQL on one web server running Windows 2003
Server, accessible by corporate users over Internet, which licensing
model is suitable?
TIA.Calculate how many different users access the server. Not at once,
all together over time. Calculate the cost of that many CALs compared
to the per-processor price. You probably will end up with
per-processor pricing.
Roy Harvey
Beacon Falls, CT
On 26 Jul 2006 10:03:32 -0700, ashkaan57@.hotmail.com wrote:
>Hi,
>I am a bit confused about the licensing schemes for MS SQL.
>There is a "Processor" licnese (about $4000) and a "Server +
>User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
>It says:
>Processor Licensing Model. Under this model, a license is required for
>each physical or virtual processor accessed by an operating system
>environment running SQL Server. This license does not require any
>device or user client access licenses (CALs).
>Server plus Device CALs. Under this model, a server license is required
>for each operating system environment running an instance of SQL
>Server, as well as a CAL for each client device that accesses a system
>running SQL Server.
>Server plus User CALs. Under this model, a server license is required
>for each operating system environment running an instance of SQL
>Server, as well as a CAL for each user that accesses a system running
>SQL Server.
>If I am installing the MS SQL on one web server running Windows 2003
>Server, accessible by corporate users over Internet, which licensing
>model is suitable?
>TIA.|||The definitive answers to licensing questions are at:
http://www.microsoft.com/licensing/default.mspx
My take:
You may recall, that the processor license is required for
internet/intranet/extranet usage UNLESS all users will have a proper CAL.
(That even includes a single small query populating a small list box on a
web page.)
If your web site is restricted to company users only, and if all company
users that will be accessing SQL Server have an existing SQL Server CAL,
then I believe that you are covered. (Subject to verification with VL.) If
all company users do not have SQL Server CALs, then you most likely need a
processor license -or additional CALs.
I do not think that any non-company (or extranet) users would be included
without the processor license -unless, upon software audit, you can prove
the existence of CALs.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<ashkaan57@.hotmail.com> wrote in message
news:1153933412.130178.59290@.s13g2000cwa.googlegroups.com...
> Hi,
> I am a bit confused about the licensing schemes for MS SQL.
> There is a "Processor" licnese (about $4000) and a "Server +
> User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
> It says:
> Processor Licensing Model. Under this model, a license is required for
> each physical or virtual processor accessed by an operating system
> environment running SQL Server. This license does not require any
> device or user client access licenses (CALs).
> Server plus Device CALs. Under this model, a server license is required
> for each operating system environment running an instance of SQL
> Server, as well as a CAL for each client device that accesses a system
> running SQL Server.
> Server plus User CALs. Under this model, a server license is required
> for each operating system environment running an instance of SQL
> Server, as well as a CAL for each user that accesses a system running
> SQL Server.
> If I am installing the MS SQL on one web server running Windows 2003
> Server, accessible by corporate users over Internet, which licensing
> model is suitable?
> TIA.
>