Queries regarding ADO and OLEDB

Hi,
I have few queries for MS SQL Server
a) What is the difference in terms of ADO / OLEDB between Windows
Server 2003 and normal Windows XP Professional?
b) Is there a parameter which regulates the number of bytes in a result
set?
c) Is it possible to install the windows xp ole db drivers on server
2003 parallel to the MSSQL server 2005
Regards
Pankaj Jain
> a) What is the difference in terms of ADO / OLEDB between Windows
> Server 2003 and normal Windows XP Professional?
I'd be surprised if there is a difference.
Linchi
"Pankaj Jain" wrote:

> Hi,
> I have few queries for MS SQL Server
> a) What is the difference in terms of ADO / OLEDB between Windows
> Server 2003 and normal Windows XP Professional?
> b) Is there a parameter which regulates the number of bytes in a result
> set?
> c) Is it possible to install the windows xp ole db drivers on server
> 2003 parallel to the MSSQL server 2005
> Regards
> Pankaj Jain
>
>

Queries regarding ADO and OLEDB

Hi,
I have few queries for MS SQL Server
a) What is the difference in terms of ADO / OLEDB between Windows
Server 2003 and normal Windows XP Professional?
b) Is there a parameter which regulates the number of bytes in a result
set?
c) Is it possible to install the windows xp ole db drivers on server
2003 parallel to the MSSQL server 2005
Regards
Pankaj Jain> a) What is the difference in terms of ADO / OLEDB between Windows
> Server 2003 and normal Windows XP Professional?
I'd be surprised if there is a difference.
Linchi
"Pankaj Jain" wrote:
> Hi,
> I have few queries for MS SQL Server
> a) What is the difference in terms of ADO / OLEDB between Windows
> Server 2003 and normal Windows XP Professional?
> b) Is there a parameter which regulates the number of bytes in a result
> set?
> c) Is it possible to install the windows xp ole db drivers on server
> 2003 parallel to the MSSQL server 2005
> Regards
> Pankaj Jain
>
>

queries longer than 5 mins

Hi I have set up a windows group for our Crystal reporters as they sometimes
have code that runs for way to long is there a cmd I can issue that will cut
of any queries going on longer then 5 minutes just for this particular group
.
Not sure if possible
Thanks
for any help
SammySammy
Use SQL Server Profiler to see what is going on. Look at Duration column.
"Sammy" <Sammy@.discussions.microsoft.com> wrote in message
news:8A577E59-8C2D-48B3-8E77-C410FC41C308@.microsoft.com...
> Hi I have set up a windows group for our Crystal reporters as they
> sometimes
> have code that runs for way to long is there a cmd I can issue that will
> cut
> of any queries going on longer then 5 minutes just for this particular
> group.
> Not sure if possible
>
> Thanks
> for any help
> Sammy

QP is missing and it is required to evaluate default expressions?

Hi everyone

I have a really odd problem that has manifested its self. I have a Windows Mobile 6 device that I debugging my application on, the application uses a local Sql Compact sdf file, if I just run the app, when it comes to executing some ado.net against the database I get the following error:-

QP is missing and it is required to evaluate default expressions. Ensure that sqlceqp30.dll is in the same directory as the storage engine (sqlcese30.dll)

If however I open the the database using query analyzer first on the device then everything is ok until I next soft reset the device

Has anyone else come across this?

Thanks in advance

Dan

Could be some out-of-memory issue. Are both the mentioned files present in the \Windows folder on the device. (use the device File manager to check, remember to select "Show All Files" from the menu.)|||

Hi

Yeah all the files are present and correct. Its really odd, it seems once the connection has been made by something else its happy.

|||I'm having the same issue...|||Did you find the solution for this problem? We are getting this problem too.

Rajesh

q; using RAISERROR

In my Windows application I use sqlCmd.ExecuteNonQuery() to execute the
stored procedure, In case of an error in the stored procedure I need to
return an exception to application, will RAISERROR in stored procedure
accomplish that?JIM.H.,
Yes.
Implementing Error Handling with Stored Procedures
http://www.sommarskog.se/error-handling-II.html
Error Handling in SQL Server – a Background
http://www.sommarskog.se/error-handling-I.html
AMB
"JIM.H." wrote:

> In my Windows application I use sqlCmd.ExecuteNonQuery() to execute the
> stored procedure, In case of an error in the stored procedure I need to
> return an exception to application, will RAISERROR in stored procedure
> accomplish that?|||For a full discussion of RAISERROR, refer to Books on Line.
You can use RAISERROR to 'thow' an error condition to the calling process.
Normally, you would have a condition to check, then use a BEGIN-END block to
both RAISERROR and then RETURN to the calling process. Without the RETURN,
any code after the RAISERROR will also execute.
i.e.,
IF {condition to check}
BEGIN
RAISERROR ("Error Occurred", 16, 1)
RETURN
END
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:116D7CFD-FE3D-432B-B5DA-9A0CD93F744A@.microsoft.com...
> In my Windows application I use sqlCmd.ExecuteNonQuery() to execute the
> stored procedure, In case of an error in the stored procedure I need to
> return an exception to application, will RAISERROR in stored procedure
> accomplish that?

q; using RAISERROR

In my Windows application I use sqlCmd.ExecuteNonQuery() to execute the
stored procedure, In case of an error in the stored procedure I need to
return an exception to application, will RAISERROR in stored procedure
accomplish that?JIM.H.,
Yes.
Implementing Error Handling with Stored Procedures
http://www.sommarskog.se/error-handling-II.html
Error Handling in SQL Server â' a Background
http://www.sommarskog.se/error-handling-I.html
AMB
"JIM.H." wrote:
> In my Windows application I use sqlCmd.ExecuteNonQuery() to execute the
> stored procedure, In case of an error in the stored procedure I need to
> return an exception to application, will RAISERROR in stored procedure
> accomplish that?|||For a full discussion of RAISERROR, refer to Books on Line.
You can use RAISERROR to 'thow' an error condition to the calling process.
Normally, you would have a condition to check, then use a BEGIN-END block to
both RAISERROR and then RETURN to the calling process. Without the RETURN,
any code after the RAISERROR will also execute.
i.e.,
IF {condition to check}
BEGIN
RAISERROR ("Error Occurred", 16, 1)
RETURN
END
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:116D7CFD-FE3D-432B-B5DA-9A0CD93F744A@.microsoft.com...
> In my Windows application I use sqlCmd.ExecuteNonQuery() to execute the
> stored procedure, In case of an error in the stored procedure I need to
> return an exception to application, will RAISERROR in stored procedure
> accomplish that?

q; two difefrent database

Hello,
I have two application running on two different database, and I have only
one Windows 2003 server. Which way is best to go: two instances on the same
server or two different databases under one instance?JIM.H. wrote:
> Hello,
> I have two application running on two different database, and I have only
> one Windows 2003 server. Which way is best to go: two instances on the same
> server or two different databases under one instance?
Two different database under one instance.
Regards
Amish Shah

q; two difefrent database

Hello,
I have two application running on two different database, and I have only
one Windows 2003 server. Which way is best to go: two instances on the same
server or two different databases under one instance?JIM.H. wrote:

> Hello,
> I have two application running on two different database, and I have only
> one Windows 2003 server. Which way is best to go: two instances on the sam
e
> server or two different databases under one instance?
Two different database under one instance.
Regards
Amish Shah

Q: Windows Authentication

Is Windows Authentication possible without a domain controller?
I am running a testbed with two Win2K machines without firewalls. One
computer contains the MSDE 2000A, set for Windows Authentication
only. Running MS Access on the other computer under the Administrator
account causes a connection failure error message:
Microsoft SQL Server Login
Connection failed:
SQLState: '01000'
SQL Server Error: 87
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Specified SQL server not
found.
Lou Arnold,
Ottawa, Canada
PS...This is a peer-to peer network...no domain controller.
On Sun, 18 Jul 2004 03:53:19 GMT, Lou_Arnold@.nospam.com (Lou Arnold)
wrote:

>Is Windows Authentication possible without a domain controller?
>I am running a testbed with two Win2K machines without firewalls. One
>computer contains the MSDE 2000A, set for Windows Authentication
>only. Running MS Access on the other computer under the Administrator
>account causes a connection failure error message:
>Microsoft SQL Server Login
>--
>Connection failed:
>SQLState: '01000'
>SQL Server Error: 87
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
>(Connect()).
>Connection failed:
>SQLState: '08001'
>SQL Server Error: 6
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]Specified SQL server not
>found.
>Lou Arnold,
>Ottawa, Canada
|||Try substituting WORKGROUP\USERNAME for DOMAIN\USERNAME. Your error looks
like something other than authentication, however. The two machines can see
each other? Are they in the same workgroup? Maybe try connecting by IP
address instead of machine name and make sure your SQL Server service is
running.
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40f9f68a.19289767@.nntp.flfrd.phub.net.cable.r ogers.com...
> PS...This is a peer-to peer network...no domain controller.
> On Sun, 18 Jul 2004 03:53:19 GMT, Lou_Arnold@.nospam.com (Lou Arnold)
> wrote:
>
|||Michael, Pls see my replies below.
On Sun, 18 Jul 2004 05:18:01 GMT, "Michael C" <nospam@.lol.net> wrote:

>Try substituting WORKGROUP\USERNAME for DOMAIN\USERNAME.
I don't understand where to specify this. There is no domain name as
there is no domain controller.

>Your error looks
>like something other than authentication, however.
> The two machines can see
>each other? Are they in the same workgroup? Maybe try connecting by IP
>address instead of machine name and make sure your SQL Server service is
>running.
Yes, the machines can see each other. File and Printer sharing is
enabled and i can see shares on each computer from the other.
Yes, The work group name WORKGROUP for each computer.
Yes, the SQL server instance is running. (it is a named instance)
Yes, I tried using <ipaddr>\<instancename> and got the same error
message.
Lou Arnold
Ottawa, Canada
|||"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40fa18ff.473050@.nntp.flfrd.phub.net.cable.rog ers.com...
> Michael, Pls see my replies below.
> On Sun, 18 Jul 2004 05:18:01 GMT, "Michael C" <nospam@.lol.net> wrote:
> I don't understand where to specify this. There is no domain name as
> there is no domain controller.
If you were connected to a Domain Controller, you would specify
DOMAIN\USERNAME. If you are working on a small LAN with no domain
controller, you can specify WORKGROUP\USERNAME instead; or possibly
MACHINENAME\USERNAME (like this: "MSHOME\BOB" or "COMPUTER1\BOB"). You
might also try connecting using the sa username/password.

> Yes, the machines can see each other. File and Printer sharing is
> enabled and i can see shares on each computer from the other.
> Yes, The work group name WORKGROUP for each computer.
> Yes, the SQL server instance is running. (it is a named instance)
> Yes, I tried using <ipaddr>\<instancename> and got the same error
> message.
>
Do you have a default instance running, or just a named instance? Try
connecting to just <ipaddr> if it's the default instance.
Cheers,
Michael C.
|||In reply:
The instance is a single named instance.
I tried connecting with the SA username and password, but it failed
with the same error message. This was expected since the server is set
up for Windows Authentication only.
Re the Workgroup/Domain name: I understand your explanation, but I
still don't know where (or how) to enter the
workgroup-name/computer-name. Can you be specific about the window
and field that this info should be entered? I am still using the
ipaddr/instance-name in the MIcrosoft SQL Server Database Wizard
Dialog box. This box is the first box displayed when, in MS Access,
you try to create a new Access project. The field has the text label:
"What SQL Server would you like to use for this database?"
Lou
On Sun, 18 Jul 2004 17:42:49 GMT, "Michael C" <nospam@.lol.net> wrote:

>"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
>news:40fa18ff.473050@.nntp.flfrd.phub.net.cable.ro gers.com...
>If you were connected to a Domain Controller, you would specify
>DOMAIN\USERNAME. If you are working on a small LAN with no domain
>controller, you can specify WORKGROUP\USERNAME instead; or possibly
>MACHINENAME\USERNAME (like this: "MSHOME\BOB" or "COMPUTER1\BOB"). You
>might also try connecting using the sa username/password.
>
>Do you have a default instance running, or just a named instance? Try
>connecting to just <ipaddr> if it's the default instance.
>Cheers,
>Michael C.
>
|||Michael...here are a few more details:
On the server computer, I have used the SQL Server Network Utility to
disable all but TCP/IP connections. Also, the server is set to use
port 1433. Is this appropriate?
On the client computer, I have used the SQL Server Client Network
Utility to disable all but TCP/IP, and to set the default port value
for TCP/IP to use 1433. Is this appropriate?
Lou.
|||Michael...Sorry I was in error. I enabled File and Printer Sharing and
Client for MS Network on the server computer. Doing this got me past
the connect error I gave in the initial post. However, no database was
created, and no error message was generated. Again, I wonder if this a
Windows Authentication problem.
The symptom is now tthis:
The MS SQL Server Database Wizard apparently connects to the server,
after which a dialog box appears saying that it has all the info it
needs. When I Click Finish, a dialog box appears for a split second.
This dialog box is a progress bar that shows the progress of creating
the new database on the server. This bar shows no progress and quickly
disappears. Why does this happen?
Why is Client for MS Networks and File and Printer Sharing required to
make the connection to the server?
Lou Arnold
|||OK, I'm a little lost now. I was under the assumption that you were trying
to connect to your SQL Server via SQL Enterprise Manager and set up
permissions on an account using that. Now I'm not so sure. Just a couple
of questions so I can try to help you a little better:
1. What exactly are you trying to do?
2. Do you have SQL Server 2K on one computer or both?
3. Are both computers in the same Workgroup (right-click on My Computer >
Properties > Computer Name)?
4. Are both computers set up in the same IP range with the same Subnet
(TCP/IP settings)?
5. Are you running any firewall software?
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40fbcf8b.2586869@.nntp.flfrd.phub.net.cable.ro gers.com...
> Michael...Sorry I was in error. I enabled File and Printer Sharing and
> Client for MS Network on the server computer. Doing this got me past
> the connect error I gave in the initial post. However, no database was
> created, and no error message was generated. Again, I wonder if this a
> Windows Authentication problem.
> The symptom is now tthis:
> The MS SQL Server Database Wizard apparently connects to the server,
> after which a dialog box appears saying that it has all the info it
> needs. When I Click Finish, a dialog box appears for a split second.
> This dialog box is a progress bar that shows the progress of creating
> the new database on the server. This bar shows no progress and quickly
> disappears. Why does this happen?
> Why is Client for MS Networks and File and Printer Sharing required to
> make the connection to the server?
> Lou Arnold
|||Michael...see my replies below.
On Tue, 20 Jul 2004 00:36:08 GMT, "Michael C" <nospam@.lol.net> wrote:

>OK, I'm a little lost now. I was under the assumption that you were trying
>to connect to your SQL Server via SQL Enterprise Manager and set up
>permissions on an account using that. Now I'm not so sure. Just a couple
>of questions so I can try to help you a little better:
Don't blame you for being lost.

>1. What exactly are you trying to do?
The objective is to establish a testbed of two Win2K computers. This
is to be a peer network without a domain controller. The intent is to
establish a configuration whereby these two computers can be used for
development. The server is to be used with Windows Authentication
security only unless this proves impossible. We can play with settings
such as TCP/IP, File and Printer sharing and internet port numbers as
long as we establish a minimum configuration and the reason for each
setting.
>2. Do you have SQL Server 2K on one computer or both?
Only one computer (I'll call it the server computer) has the SQL
Server installed. Only one server is installed and this is a named
instance. The server is set to use port 1433. The other computer (the
client computer) has MS Access installed. This is a requirement for
this testbed. No other computers are connected to these computers.
Both computers are run only under the Windows Administrator account to
avoid the cofiguration of permissions.

>3. Are both computers in the same Workgroup (right-click on My Computer >
>Properties > Computer Name)?
Yes, both are in the same workgroup.

>4. Are both computers set up in the same IP range with the same Subnet
>(TCP/IP settings)?
Yes. they run thru a router and so have adjacent addresses, and the
subnet mask of 255.255.255.0. The router's internet connection is
disabled.
BTW: both TCP/IP and Named Pipes are enabled on both client and server
machines using the client and server network utilities.

>5. Are you running any firewall software?
No. No firewalls have been installed.
More info:
In my initial post, MS Access generated a connection error. After some
trials, it was found that networking components "File and Printer
Sharing" and "Client for MS Networks" had to be enabled on both
computers for the connection to work (why is unclear and must be
investigated). After enabling these two networking components, the
connection appears to succeed, but creation of the database fails and
no error message is generated.
In my mind are the following possible causes:
1) Windows Authentication cannot work because there is no domain
controller. Therefore SQL Server authentication must be used. We must
be sure that this is the only recourse before we abandon Windows
Authentication.
Or
2) Somehow the client's Windows Administrator account is not
recognized by the Server as having permission to create a database,
despite the fact that Windows Administrators should have that
permission by default.
Lou.

Q: Windows Authentication

Is Windows Authentication possible without a domain controller?
I am running a testbed with two Win2K machines without firewalls. One
computer contains the MSDE 2000A, set for Windows Authentication
only. Running MS Access on the other computer under the Administrator
account causes a connection failure error message:
Microsoft SQL Server Login
--
Connection failed:
SQLState: '01000'
SQL Server Error: 87
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Specified SQL serve
r not
found.
Lou Arnold,
Ottawa, CanadaPS...This is a peer-to peer network...no domain controller.
On Sun, 18 Jul 2004 03:53:19 GMT, Lou_Arnold@.nospam.com (Lou Arnold)
wrote:

>Is Windows Authentication possible without a domain controller?
>I am running a testbed with two Win2K machines without firewalls. One
>computer contains the MSDE 2000A, set for Windows Authentication
>only. Running MS Access on the other computer under the Administrator
>account causes a connection failure error message:
>Microsoft SQL Server Login
>--
>Connection failed:
>SQLState: '01000'
>SQL Server Error: 87
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
>(Connect()).
>Connection failed:
>SQLState: '08001'
>SQL Server Error: 6
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]Specified SQL serv
er not
>found.
>Lou Arnold,
>Ottawa, Canada|||Try substituting WORKGROUP\USERNAME for DOMAIN\USERNAME. Your error looks
like something other than authentication, however. The two machines can see
each other? Are they in the same workgroup? Maybe try connecting by IP
address instead of machine name and make sure your SQL Server service is
running.
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40f9f68a.19289767@.nntp.flfrd.phub.net.cable.rogers.com...
> PS...This is a peer-to peer network...no domain controller.
> On Sun, 18 Jul 2004 03:53:19 GMT, Lou_Arnold@.nospam.com (Lou Arnold)
> wrote:
>
>|||Michael, Pls see my replies below.
On Sun, 18 Jul 2004 05:18:01 GMT, "Michael C" <nospam@.lol.net> wrote:

>Try substituting WORKGROUP\USERNAME for DOMAIN\USERNAME.
I don't understand where to specify this. There is no domain name as
there is no domain controller.

>Your error looks
>like something other than authentication, however.
> The two machines can see
>each other? Are they in the same workgroup? Maybe try connecting by IP
>address instead of machine name and make sure your SQL Server service is
>running.
Yes, the machines can see each other. File and Printer sharing is
enabled and i can see shares on each computer from the other.
Yes, The work group name WORKGROUP for each computer.
Yes, the SQL server instance is running. (it is a named instance)
Yes, I tried using <ipaddr>\<instancename> and got the same error
message.
Lou Arnold
Ottawa, Canada|||"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40fa18ff.473050@.nntp.flfrd.phub.net.cable.rogers.com...
> Michael, Pls see my replies below.
> On Sun, 18 Jul 2004 05:18:01 GMT, "Michael C" <nospam@.lol.net> wrote:
>
> I don't understand where to specify this. There is no domain name as
> there is no domain controller.
If you were connected to a Domain Controller, you would specify
DOMAIN\USERNAME. If you are working on a small LAN with no domain
controller, you can specify WORKGROUP\USERNAME instead; or possibly
MACHINENAME\USERNAME (like this: "MSHOME\BOB" or "COMPUTER1\BOB"). You
might also try connecting using the sa username/password.

> Yes, the machines can see each other. File and Printer sharing is
> enabled and i can see shares on each computer from the other.
> Yes, The work group name WORKGROUP for each computer.
> Yes, the SQL server instance is running. (it is a named instance)
> Yes, I tried using <ipaddr>\<instancename> and got the same error
> message.
>
Do you have a default instance running, or just a named instance? Try
connecting to just <ipaddr> if it's the default instance.
Cheers,
Michael C.|||In reply:
The instance is a single named instance.
I tried connecting with the SA username and password, but it failed
with the same error message. This was expected since the server is set
up for Windows Authentication only.
Re the Workgroup/Domain name: I understand your explanation, but I
still don't know where (or how) to enter the
workgroup-name/computer-name. Can you be specific about the window
and field that this info should be entered? I am still using the
ipaddr/instance-name in the MIcrosoft SQL Server Database Wizard
Dialog box. This box is the first box displayed when, in MS Access,
you try to create a new Access project. The field has the text label:
"What SQL Server would you like to use for this database?"
Lou
On Sun, 18 Jul 2004 17:42:49 GMT, "Michael C" <nospam@.lol.net> wrote:

>"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
>news:40fa18ff.473050@.nntp.flfrd.phub.net.cable.rogers.com...
>If you were connected to a Domain Controller, you would specify
>DOMAIN\USERNAME. If you are working on a small LAN with no domain
>controller, you can specify WORKGROUP\USERNAME instead; or possibly
>MACHINENAME\USERNAME (like this: "MSHOME\BOB" or "COMPUTER1\BOB"). You
>might also try connecting using the sa username/password.
>
>Do you have a default instance running, or just a named instance? Try
>connecting to just <ipaddr> if it's the default instance.
>Cheers,
>Michael C.
>|||Michael...here are a few more details:
On the server computer, I have used the SQL Server Network Utility to
disable all but TCP/IP connections. Also, the server is set to use
port 1433. Is this appropriate?
On the client computer, I have used the SQL Server Client Network
Utility to disable all but TCP/IP, and to set the default port value
for TCP/IP to use 1433. Is this appropriate?
Lou.|||Michael...Sorry I was in error. I enabled File and Printer Sharing and
Client for MS Network on the server computer. Doing this got me past
the connect error I gave in the initial post. However, no database was
created, and no error message was generated. Again, I wonder if this a
Windows Authentication problem.
The symptom is now tthis:
The MS SQL Server Database Wizard apparently connects to the server,
after which a dialog box appears saying that it has all the info it
needs. When I Click Finish, a dialog box appears for a split second.
This dialog box is a progress bar that shows the progress of creating
the new database on the server. This bar shows no progress and quickly
disappears. Why does this happen?
Why is Client for MS Networks and File and Printer Sharing required to
make the connection to the server'
Lou Arnold|||OK, I'm a little lost now. I was under the assumption that you were trying
to connect to your SQL Server via SQL Enterprise Manager and set up
permissions on an account using that. Now I'm not so sure. Just a couple
of questions so I can try to help you a little better:
1. What exactly are you trying to do?
2. Do you have SQL Server 2K on one computer or both?
3. Are both computers in the same Workgroup (right-click on My Computer >
Properties > Computer Name)?
4. Are both computers set up in the same IP range with the same Subnet
(TCP/IP settings)?
5. Are you running any firewall software?
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40fbcf8b.2586869@.nntp.flfrd.phub.net.cable.rogers.com...
> Michael...Sorry I was in error. I enabled File and Printer Sharing and
> Client for MS Network on the server computer. Doing this got me past
> the connect error I gave in the initial post. However, no database was
> created, and no error message was generated. Again, I wonder if this a
> Windows Authentication problem.
> The symptom is now tthis:
> The MS SQL Server Database Wizard apparently connects to the server,
> after which a dialog box appears saying that it has all the info it
> needs. When I Click Finish, a dialog box appears for a split second.
> This dialog box is a progress bar that shows the progress of creating
> the new database on the server. This bar shows no progress and quickly
> disappears. Why does this happen?
> Why is Client for MS Networks and File and Printer Sharing required to
> make the connection to the server'
> Lou Arnold|||Michael...see my replies below.
On Tue, 20 Jul 2004 00:36:08 GMT, "Michael C" <nospam@.lol.net> wrote:

>OK, I'm a little lost now. I was under the assumption that you were trying
>to connect to your SQL Server via SQL Enterprise Manager and set up
>permissions on an account using that. Now I'm not so sure. Just a couple
>of questions so I can try to help you a little better:
Don't blame you for being lost.

>1. What exactly are you trying to do?
The objective is to establish a testbed of two Win2K computers. This
is to be a peer network without a domain controller. The intent is to
establish a configuration whereby these two computers can be used for
development. The server is to be used with Windows Authentication
security only unless this proves impossible. We can play with settings
such as TCP/IP, File and Printer sharing and internet port numbers as
long as we establish a minimum configuration and the reason for each
setting.
>2. Do you have SQL Server 2K on one computer or both?
Only one computer (I'll call it the server computer) has the SQL
Server installed. Only one server is installed and this is a named
instance. The server is set to use port 1433. The other computer (the
client computer) has MS Access installed. This is a requirement for
this testbed. No other computers are connected to these computers.
Both computers are run only under the Windows Administrator account to
avoid the cofiguration of permissions.

>3. Are both computers in the same Workgroup (right-click on My Computer >
>Properties > Computer Name)?
Yes, both are in the same workgroup.

>4. Are both computers set up in the same IP range with the same Subnet
>(TCP/IP settings)?
Yes. they run thru a router and so have adjacent addresses, and the
subnet mask of 255.255.255.0. The router's internet connection is
disabled.
BTW: both TCP/IP and Named Pipes are enabled on both client and server
machines using the client and server network utilities.

>5. Are you running any firewall software?
No. No firewalls have been installed.
More info:
In my initial post, MS Access generated a connection error. After some
trials, it was found that networking components "File and Printer
Sharing" and "Client for MS Networks" had to be enabled on both
computers for the connection to work (why is unclear and must be
investigated). After enabling these two networking components, the
connection appears to succeed, but creation of the database fails and
no error message is generated.
In my mind are the following possible causes:
1) Windows Authentication cannot work because there is no domain
controller. Therefore SQL Server authentication must be used. We must
be sure that this is the only recourse before we abandon Windows
Authentication.
Or
2) Somehow the client's Windows Administrator account is not
recognized by the Server as having permission to create a database,
despite the fact that Windows Administrators should have that
permission by default.
--
Lou.

Q: RS2000 what OS?

Hello,
Can I install reporting services in a XP Pro, or windows 2000. We have SQL
Server 2000 installed on XP Pro, I was trying to install RS2000 and I got a
message it sais OS should be a server. Does that mean RS2000 can only be
installed on a server? Can I install RS2000 on a windows 2000 machine?PiBDYW4gSSBpbnN0YWxsIHJlcG9ydGluZyBzZXJ2aWNlcyBpbiBhIFhQIFBybywgb3Igd2luZG93
cyAyMDAwLiBXZSBoYXZlIFNRTCANCj4gU2VydmVyIDIwMDAgaW5zdGFsbGVkIG9uIFhQIFBybywg
SSB3YXMgdHJ5aW5nIHRvIGluc3RhbGwgUlMyMDAwIGFuZCBJIGdvdCBhIA0KPiBtZXNzYWdlIGl0
IHNhaXMgT1Mgc2hvdWxkIGJlIGEgc2VydmVyLiBEb2VzIHRoYXQgbWVhbiBSUzIwMDAgY2FuIG9u
bHkgYmUgDQo+IGluc3RhbGxlZCBvbiBhIHNlcnZlcj8gQ2FuIEkgaW5zdGFsbCBSUzIwMDAgb24g
YSB3aW5kb3dzIDIwMDAgbWFjaGluZT8NCg0KaHR0cDovL21zZG4ubWljcm9zb2Z0LmNvbS9saWJy
YXJ5L2VuLXVzL1JTaW5zdGFsbC9odG0vZ3NfaW5zdGFsbGluZ3JzX3YxXzhqb20uYXNw

Q: RS on XP

Hello,

I have SQL Server 2000 installed on my Windows XP, can I install Reporting Services to this machine? If yes, where can I get it?

Thanks,

No you can't install SRS Server on an XP machine. You could fiind more info onhttp://www.microsoft.com/sql/reporting/default.mspx
|||

Thank you for the reply. I could not really locate it, can you tell me the exact URL that tells we can not install it to XP. I need to send it to my manager.

Thanks,

|||http://www.microsoft.com/sql/reporting/productinfo/sysreqs.mspx
The above url won't show you how to install SRS it will just show your manager that you can't install the server componets on an XP box. You can only install the development edition as per the URL above.|||

Is there anyway I can download the developer edition on the internet? I think the trial RS version is Enterprise, I have SQL Server license what should I do to get RS Developer if it is not in the internet?
Thanks for your help.

|||

Unfortuneatly I don't know of any site where you can download developer edition of RS. You should be able to install the development part of Enterprise SRS on your XP machine. However you won't be able to host SRS reports, for this you'll need a server OS.

q: reporting service in SQL 2005

Hello,
I installed SQL Server 2005 into a Windows 2005 Pro machine, will I be able
to use Reporting service to deploy the reports here? Is there any web site
that show step by step how I can do that?
Thanks,On Sun, 21 May 2006 04:59:02 -0700, JIM.H.
<JIMH@.discussions.microsoft.com> wrote:

>Hello,
>I installed SQL Server 2005 into a Windows 2005 Pro machine, will I be able
>to use Reporting service to deploy the reports here? Is there any web site
>that show step by step how I can do that?
>Thanks,
Jim,
There is no Windows 2005. I guess you mean Windows XP Pro.
XP Pro is really appropriate only for a development machine for SQL
Server 2005.There are technical and potential licensing issues.
Questions on Reporting Services are better directed to the
microsoft.public.sqlserver.reportingsvcs newsgroup.
There is series of webcasts under way on Reporting Services 2005 at
http://www.microsoft.com/events.
Andrew Watt MVP

q: reporting service in SQL 2005

Hello,
I installed SQL Server 2005 into a Windows 2005 Pro machine, will I be able
to use Reporting service to deploy the reports here? Is there any web site
that show step by step how I can do that?
Thanks,On Sun, 21 May 2006 04:59:02 -0700, JIM.H.
<JIMH@.discussions.microsoft.com> wrote:
>Hello,
>I installed SQL Server 2005 into a Windows 2005 Pro machine, will I be able
>to use Reporting service to deploy the reports here? Is there any web site
>that show step by step how I can do that?
>Thanks,
Jim,
There is no Windows 2005. I guess you mean Windows XP Pro.
XP Pro is really appropriate only for a development machine for SQL
Server 2005.There are technical and potential licensing issues.
Questions on Reporting Services are better directed to the
microsoft.public.sqlserver.reportingsvcs newsgroup.
There is series of webcasts under way on Reporting Services 2005 at
http://www.microsoft.com/events.
Andrew Watt MVP

q: reporting service 2005

Hello,
I installed SQL Server 2005 into a Windows 2000 Pro machine, I have
following question:
1. will I be able to use Reporting services to deploy the reports to the
same machine as a report server?
2. Can I modify and deploy mo old reports written in RS2000
3. Is there any web site that show step by step how I can work with RS2005?
Thanks,On Sun, 21 May 2006 09:36:01 -0700, JIM.H.
<JIMH@.discussions.microsoft.com> wrote:
>Hello,
>I installed SQL Server 2005 into a Windows 2000 Pro machine, I have
>following question:
>1. will I be able to use Reporting services to deploy the reports to the
>same machine as a report server?
Yes, you should be able to do that. Consider performance implications
if the server is anything but lightly loaded.
>2. Can I modify and deploy mo old reports written in RS2000
Yes, but it's a one way process (for most practical purposes). Once
you have opened an RS2000 report in BIDS and deployed it on RS2005 you
won't be able (without some hand editing) to deploy the report at a
future date on an RS2000 server.
If you have a possible need to return/use RS2000 make a backup in the
old format before deploying on RS2005.
>3. Is there any web site that show step by step how I can work with RS2005?
Books Online has a lot of useful information.
Also take a look at http://www.microsoft.com/events. There is a series
of RS2005 webcasts underway.
Andrew Watt MVP
>Thanks,