Showing posts with label environment. Show all posts
Showing posts with label environment. Show all posts

Friday, March 30, 2012

Network Connection

I installed MSDE on a 2003 server machine in an AD environment. During the
setup I used the disablenetworkprotocols=0 switch to enable network
connections. I also enable mixed mode authentication. However, I still
cannot connect to the server from a XP sp2 machine on the network. (firewall
is disabled) The error returned is sqlserver does not exist or access denied.
I tried connecting via windows autehntication and specifying a SQL account.
Does anyone know why I cannot connect or maybe a site that will help diagnose
the problem?
hi Joe,
Joe Kiaser wrote:
> I installed MSDE on a 2003 server machine in an AD environment.
> During the setup I used the disablenetworkprotocols=0 switch to
> enable network connections. I also enable mixed mode authentication.
> However, I still cannot connect to the server from a XP sp2 machine
> on the network. (firewall is disabled) The error returned is
> sqlserver does not exist or access denied.
>
please have a look at
http://support.microsoft.com/default...06&Product=sql
for some potential causes of this kind of problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I discoverd it was problem with DNS. <Webserver> was pointing to the wrong
IP so when we tried to connect using <webserver> it would fail. I
discovered this after pinging <webserver> and it returned 120.0.0.21...our
WSUS server. I just updated the DNS to point <webserver> to 120.0.0.23 and
it works flawlessly.
"Andrea Montanari" wrote:

> hi Joe,
> Joe Kiaser wrote:
> please have a look at
> http://support.microsoft.com/default...06&Product=sql
> for some potential causes of this kind of problem..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql

Wednesday, March 28, 2012

Netware, MS SQL Server , Logins

Posted in Sql Server Setup Newsgroup as well.
I have a MS Sql Server 2000 application. The LAN environment is Novell Netw
are 5.x. with NO Windows domain. The network layer is TCP/IP and IPX/SPX. L
arge network with many users (500+), thus slow to change.
The client workstation OS that is going to attach to the Sql Server app are
Windows NT 4.0. The workstations load the Novell Netware client as the prim
ary client and authenicate there. The Novell Netware client is "checked" t
o logon to Windows Workstat
ion locally.
Here is the delimma. No Windows domain seems to rule out NT Authenicated se
curity on Sql Server. Sql Server authenication will be tough to maintain du
e to number of users.
1. Can the Novell login name/ psw be used in any way?
2. Can the Sql Server and the Novell LAN be intergrated in a way that would
help in this situation?
3. What would you do?
Thanks,
BrianPrevious Post:
Here is the delimma. No Windows domain seems to rule out NT Authenicated
security on Sql Server. Sql Server authenication will be tough to maintain
due to number of users.
1. Can the Novell login name/ psw be used in any way?
2. Can the Sql Server and the Novell LAN be intergrated in a way that would
help in this situation?
3. What would you do?
Reply:
1. No. You'd have to login to both Novell and a Windows DC.
2. Without a domain. You can only use SQL Standard Security with TCP or
IPX/SPX.
3. Use TCP/IP. Enable Protocol Encryption to encrypt the traffic and the
logins. Just putting a server certificate on the SQL machine will encrypt
the logins. Enabling protocol encryption will encrypt all the traffic as
well.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Saturday, February 25, 2012

Need tools to Convert Access to SQL environment

I got a big Access file (1 400 tables) to convert to SQL and I would
like to be provided with some automated tools, except upsizing wizard
and DTS, to convert it on my own.

I got a lot of forms and query to convert too.

Can someday provide me with at least one tool name ?

Thanks,

GuyHi
AFAIK the upsizing wizard is about your only option. SQL Server does not
have forms, these will remain in the access database/project.

Have you tried the wizard? If yes does it produce any errors?

John

"Guy" <guy@.graphic-designer.com> wrote in message
news:e04bda98.0311280614.523730ea@.posting.google.c om...
> I got a big Access file (1 400 tables) to convert to SQL and I would
> like to be provided with some automated tools, except upsizing wizard
> and DTS, to convert it on my own.
> I got a lot of forms and query to convert too.
> Can someday provide me with at least one tool name ?
> Thanks,
> Guy|||Also...

You may want to post to the access news group!

John

"Guy" <guy@.graphic-designer.com> wrote in message
news:e04bda98.0311280614.523730ea@.posting.google.c om...
> I got a big Access file (1 400 tables) to convert to SQL and I would
> like to be provided with some automated tools, except upsizing wizard
> and DTS, to convert it on my own.
> I got a lot of forms and query to convert too.
> Can someday provide me with at least one tool name ?
> Thanks,
> Guy|||John,

The wizard did a little bit of the job (a lot to complete), but nothing
is available to help me finish conversion, moreover with forms and
query.

What' the Access newsgroup URL ?

Thanks,

Guy

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||Hi

Either:

comp.databases.ms-access
microsoft.public.access.*

Your forms will need to remain in the access database or an access project,
they is no equivalent in SQL server.

John

"Guy Yug" <guy@.graphic-designer.com> wrote in message
news:3fc76a10$0$88386$75868355@.news.frii.net...
> John,
> The wizard did a little bit of the job (a lot to complete), but nothing
> is available to help me finish conversion, moreover with forms and
> query.
> What' the Access newsgroup URL ?
> Thanks,
> Guy
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||On Fri, 28 Nov 2003 17:10:42 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:

>Hi
>Either:
>comp.databases.ms-access
>microsoft.public.access.*
>Your forms will need to remain in the access database or an access project,
>they is no equivalent in SQL server.
>John
>
>"Guy Yug" <guy@.graphic-designer.com> wrote in message
>news:3fc76a10$0$88386$75868355@.news.frii.net...
>>
>> John,
>>
>> The wizard did a little bit of the job (a lot to complete), but nothing
>> is available to help me finish conversion, moreover with forms and
>> query.
>>
>> What' the Access newsgroup URL ?
>>
>> Thanks,
>>
>> Guy
>>
>>
>> *** Sent via Developersdex http://www.developersdex.com ***
>> Don't just participate in USENET...get rewarded for it!
Do you mean you want the forms / queries to remain in access but use
sql server as a source of tables, or do you want to convert them to
something else? Either way you might find this link helpful

http://www.microtools.us/

It's a tool that purports to convert an access application to an
asp.net one.|||Guy,

www.upsizewizard.com has the tool to convert Access Queries(even with
form parameters) to SQL stored procedures.

wizard|||Thanks for your time and info.,

I'll have a tour of this tool soon.

Guy

wizard@.upsizewizard.com (upsizewizard) wrote in message news:<c63ed6cf.0311281820.7f97e654@.posting.google.com>...
> Guy,
> www.upsizewizard.com has the tool to convert Access Queries(even with
> form parameters) to SQL stored procedures.
> wizard|||On 30 Nov 2003 08:57:53 -0800, guy@.graphic-designer.com (Guy) wrote:

>Thanks for your time and info.,
>I'll have a tour of this tool soon.
>Guy
>wizard@.upsizewizard.com (upsizewizard) wrote in message news:<c63ed6cf.0311281820.7f97e654@.posting.google.com>...
>> Guy,
>>
>> www.upsizewizard.com has the tool to convert Access Queries(even with
>> form parameters) to SQL stored procedures.
>>
>> wizard

Hmmmm $10.000 dollars to convert a Access Database to SQL kinda pricey
isnt it?|||Lyndon Hills <lyndon@.nospam.tenegi.com> wrote in message news:<66dfsvsdabl8u0k4baobg71df0p4fhurjs@.4ax.com>...
> Do you mean you want the forms / queries to remain in access but use
> sql server as a source of tables, or do you want to convert them to
> something else? Either way you might find this link helpful
> http://www.microtools.us/
> It's a tool that purports to convert an access application to an
> asp.net one.
Has anyone actually use this Microtools converter? Is it good?

Regards,
Michael Freidgeim|||Hi Guy,

My application generator for MS SQL Server can do the entire job for
you
The benefits of this system are as follows:
1. The system generates true Client Server and Multi Tier
applications.
2. There is zero coding for common functionality, i.e. Adds, Updates,
Deletes, Audit trail, Security, Rolling Down Data, Cascading Deletes,
Posting to General ledger etc.
3. There is zero work of any kind for generation of data entry
screens and their lookups.
4. The back end is completely independent from the front end. You can
hit the database with any application or user interface and still be
sure that you have complete security and valid data.
5. Easy navigation through out the application. The generated user
interface is a familiar modern metaphor with a navigation tree on top
or at the side and data entry screens at the bottom. Also, the
generated user interface remembers customizations to each data entry
screen. This allows you to make sweeping changes to the interface, and
regenerate all data entry screens, without loosing your
customizations.
6. Consistent look and feel via OOP Inheritance and code generators.
7. Major changes in look and functionality are made in one place
only, and ripple down to all affected parts of the system without
programmer intervention. Again, this was accomplished with OOP
inheritance and also with code generators.
8. Users to have the ability to create queries and reports on the
fly. And the ability to save and reload those queries and reports in
many formats including Excel and HTML.
9. Users to have complete flexibility in customizing the look and
feel of the system. The extent to which each user can customize the
interface must be seen to be believed. This high level of
customizability creates a high degree of user acceptance.
10. Logical use of hot keys and local popup menus allow for easy mouse
free operation, permitting the user to keep his or her hands on the
keyboard, if the user so desires.
11. All custom code added to generated data entry screens and
generated backend code persists after regeneration.
12. Comes with a business rule generator
13. Comes with a data import utility
14. Comes with a data revalidation utility to use when you change your
business rules.
Get all this without programming.
If you need to quickly build feature rich, bug free business
applications for MS SQL Server, then please call (201 665 8906) or
write to johnshearing@.aol.com|||guy@.graphic-designer.com (Guy) wrote in message news:<e04bda98.0311280614.523730ea@.posting.google.com>...
> I got a big Access file (1 400 tables) to convert to SQL and I would
> like to be provided with some automated tools, except upsizing wizard
> and DTS, to convert it on my own.
> I got a lot of forms and query to convert too.
> Can someday provide me with at least one tool name ?
> Thanks,
> Guy

1400 tables? Yikes. Is this thing set up properly? I'd make sure it
was before converting anything... Then you could use access as the
front and and SQL server as the back... but you might want to read
some of Chipman & Baron's book on the subject...|||Yo JohnShear -

You still out there?

Still offering this software?
If so please advise

BobAlston9 AT aol D O T com