Ok, this is a broad question. Our system is going to receive xml files from vendors that contain background check results for individuals. We want to capture the xml results in the db for historical purposes and to have a copy of what the vendor sent before we translated the results and updated our system. I was going to store the xml in a table with a text column but wasn't sure if there was a better way to do this. Anyone have any suggestions?
ThanksI think there have a couple of posts recently on this very subject. I think the general consensus is to store the XML in an NText or Text column. Individual contributors have cautioned that these column types require additional "attention" in the form of more frequently scheduled DBCC CHECKDB statements. That has not been my experience, but others have suggested it.
Certainly in your case, since you want to keep a copy of the data received prior to manipulating it, storing it "as-is" is probably a good idea. An alternative might be to store the filename (as a pointer) in the database while saving the XML to a file on either the database server or some other location.
Regards,
hmscott|||Well, you're going to need to use the data too, right?
DECLARE @.xml varchar(1000)
SET @.xml = '<?xml version="1.0" encoding="ISO-8859-1"?>
<InsertSessionData>
<Input>
<SessionID>6F9619FF-8B86-D011-B42D-0C04FC964FF</SessionID>
<Last_Accessed>20030101</Last_Accessed>
<State><somexml></somexml></State>
</Input>
</InsertSessionData>'
DECLARE @.idoc int
EXEC sp_xml_preparedocument @.idoc OUTPUT, @.xml
SELECT * FROM OPENXML(@.idoc, '/InsertSessionData/Input', 2)
WITH(
SessionID varchar(8000),
Last_Accessed Datetime,
State Text
)|||Brett,
Your point is well taken. However, there are other ways of getting at the data in the documents. We use a VBScript and the MS DOM to strip out the necessary data and store it in the relational tables. We don't keep a copy of the XML docs (no requirement to do so), but if I did, I could simply add a line to insert the text into an archive table for historical purposes.
But I don't use OPENXML to parse the XML itself.
Regards,
hmscott|||Thanks for the ideas. We're going to extract the data we need through java code. The table is strictly for archiving. Kind of an insurance policy if we have problems with our interface application.
Showing posts with label system. Show all posts
Showing posts with label system. Show all posts
Saturday, February 25, 2012
Thursday, February 16, 2012
Capacity Planning
We are going to install a call centre application.
According to end user, there will be around 500 request
has to be inputted into the system.
We will use SQL Server 2000 as the DB. We would like to
know what factors we have to consider - Like recovery
model, database maintenance plan, fill factors ? Is it
necessary for us to archive some old data to an archive
datbase ?
Thanks"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:1cb701c4b569$d40000a0$a401280a@.phx.gbl...
> We are going to install a call centre application.
> According to end user, there will be around 500 request
> has to be inputted into the system.
>
500 requests over what time period?
> We will use SQL Server 2000 as the DB. We would like to
> know what factors we have to consider - Like recovery
> model, database maintenance plan, fill factors ? Is it
> necessary for us to archive some old data to an archive
> datbase ?
>
Those are really business decisions.
i.e. if you need to run 24x7 vs 9-5x5, your decisions will be different.
If you can do with downtime, you may go with a different decisions on
architecture.
As for archiving, again, that's a business decision. Do you want to archive
data or not?
> Thanks|||Dear Greg,
It should be 500 requests between 9:00am to 5:00pm from
Monday to Friday.
We will make full database backup daily. What is the
difference between full database backup and archive then ?
Thanks|||"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:0fba01c4b574$0e2f4830$a501280a@.phx.gbl...
> Dear Greg,
> It should be 500 requests between 9:00am to 5:00pm from
> Monday to Friday.
500 a day? That's about one a minute. You can run this thing on a desktop
machine.
> We will make full database backup daily. What is the
> difference between full database backup and archive then ?
Generally a backup is for disaster recovery. An archive is for storing data
for later analysis or for other reasons.
For example, I keep backups of only a few days (my databases generally have
enough churn that in a few days the bulk of the data has changed anyway.)
But there's certain data I archive to tape (in a different schema etc) that
I may keep for much longer.
Now, as for once a day backups, that may or may not work. Your database
sounds like it will probably be fairly small to start, so recovery time will
be about the same as backup. i.e. if it takes 10 minutes to backup, it'll
take about 10 minutes to restore. Plus any time to fix up minor issues.
However, let's say you start a backup at 5:01 PM.
What happens if your DB crashes at 5:00 PM. Can you afford to lose a day's
worth of data?
> Thanks
>
According to end user, there will be around 500 request
has to be inputted into the system.
We will use SQL Server 2000 as the DB. We would like to
know what factors we have to consider - Like recovery
model, database maintenance plan, fill factors ? Is it
necessary for us to archive some old data to an archive
datbase ?
Thanks"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:1cb701c4b569$d40000a0$a401280a@.phx.gbl...
> We are going to install a call centre application.
> According to end user, there will be around 500 request
> has to be inputted into the system.
>
500 requests over what time period?
> We will use SQL Server 2000 as the DB. We would like to
> know what factors we have to consider - Like recovery
> model, database maintenance plan, fill factors ? Is it
> necessary for us to archive some old data to an archive
> datbase ?
>
Those are really business decisions.
i.e. if you need to run 24x7 vs 9-5x5, your decisions will be different.
If you can do with downtime, you may go with a different decisions on
architecture.
As for archiving, again, that's a business decision. Do you want to archive
data or not?
> Thanks|||Dear Greg,
It should be 500 requests between 9:00am to 5:00pm from
Monday to Friday.
We will make full database backup daily. What is the
difference between full database backup and archive then ?
Thanks|||"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:0fba01c4b574$0e2f4830$a501280a@.phx.gbl...
> Dear Greg,
> It should be 500 requests between 9:00am to 5:00pm from
> Monday to Friday.
500 a day? That's about one a minute. You can run this thing on a desktop
machine.
> We will make full database backup daily. What is the
> difference between full database backup and archive then ?
Generally a backup is for disaster recovery. An archive is for storing data
for later analysis or for other reasons.
For example, I keep backups of only a few days (my databases generally have
enough churn that in a few days the bulk of the data has changed anyway.)
But there's certain data I archive to tape (in a different schema etc) that
I may keep for much longer.
Now, as for once a day backups, that may or may not work. Your database
sounds like it will probably be fairly small to start, so recovery time will
be about the same as backup. i.e. if it takes 10 minutes to backup, it'll
take about 10 minutes to restore. Plus any time to fix up minor issues.
However, let's say you start a backup at 5:01 PM.
What happens if your DB crashes at 5:00 PM. Can you afford to lose a day's
worth of data?
> Thanks
>
Capacity Planning
We are going to install a call centre application.
According to end user, there will be around 500 request
has to be inputted into the system.
We will use SQL Server 2000 as the DB. We would like to
know what factors we have to consider - Like recovery
model, database maintenance plan, fill factors ? Is it
necessary for us to archive some old data to an archive
datbase ?
Thanks"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:1cb701c4b569$d40000a0$a401280a@.phx.gbl...
> We are going to install a call centre application.
> According to end user, there will be around 500 request
> has to be inputted into the system.
>
500 requests over what time period?
> We will use SQL Server 2000 as the DB. We would like to
> know what factors we have to consider - Like recovery
> model, database maintenance plan, fill factors ? Is it
> necessary for us to archive some old data to an archive
> datbase ?
>
Those are really business decisions.
i.e. if you need to run 24x7 vs 9-5x5, your decisions will be different.
If you can do with downtime, you may go with a different decisions on
architecture.
As for archiving, again, that's a business decision. Do you want to archive
data or not?
> Thanks|||Dear Greg,
It should be 500 requests between 9:00am to 5:00pm from
Monday to Friday.
We will make full database backup daily. What is the
difference between full database backup and archive then ?
Thanks|||"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:0fba01c4b574$0e2f4830$a501280a@.phx.gbl...
> Dear Greg,
> It should be 500 requests between 9:00am to 5:00pm from
> Monday to Friday.
500 a day? That's about one a minute. You can run this thing on a desktop
machine.
> We will make full database backup daily. What is the
> difference between full database backup and archive then ?
Generally a backup is for disaster recovery. An archive is for storing data
for later analysis or for other reasons.
For example, I keep backups of only a few days (my databases generally have
enough churn that in a few days the bulk of the data has changed anyway.)
But there's certain data I archive to tape (in a different schema etc) that
I may keep for much longer.
Now, as for once a day backups, that may or may not work. Your database
sounds like it will probably be fairly small to start, so recovery time will
be about the same as backup. i.e. if it takes 10 minutes to backup, it'll
take about 10 minutes to restore. Plus any time to fix up minor issues.
However, let's say you start a backup at 5:01 PM.
What happens if your DB crashes at 5:00 PM. Can you afford to lose a day's
worth of data?
> Thanks
>
According to end user, there will be around 500 request
has to be inputted into the system.
We will use SQL Server 2000 as the DB. We would like to
know what factors we have to consider - Like recovery
model, database maintenance plan, fill factors ? Is it
necessary for us to archive some old data to an archive
datbase ?
Thanks"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:1cb701c4b569$d40000a0$a401280a@.phx.gbl...
> We are going to install a call centre application.
> According to end user, there will be around 500 request
> has to be inputted into the system.
>
500 requests over what time period?
> We will use SQL Server 2000 as the DB. We would like to
> know what factors we have to consider - Like recovery
> model, database maintenance plan, fill factors ? Is it
> necessary for us to archive some old data to an archive
> datbase ?
>
Those are really business decisions.
i.e. if you need to run 24x7 vs 9-5x5, your decisions will be different.
If you can do with downtime, you may go with a different decisions on
architecture.
As for archiving, again, that's a business decision. Do you want to archive
data or not?
> Thanks|||Dear Greg,
It should be 500 requests between 9:00am to 5:00pm from
Monday to Friday.
We will make full database backup daily. What is the
difference between full database backup and archive then ?
Thanks|||"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:0fba01c4b574$0e2f4830$a501280a@.phx.gbl...
> Dear Greg,
> It should be 500 requests between 9:00am to 5:00pm from
> Monday to Friday.
500 a day? That's about one a minute. You can run this thing on a desktop
machine.
> We will make full database backup daily. What is the
> difference between full database backup and archive then ?
Generally a backup is for disaster recovery. An archive is for storing data
for later analysis or for other reasons.
For example, I keep backups of only a few days (my databases generally have
enough churn that in a few days the bulk of the data has changed anyway.)
But there's certain data I archive to tape (in a different schema etc) that
I may keep for much longer.
Now, as for once a day backups, that may or may not work. Your database
sounds like it will probably be fairly small to start, so recovery time will
be about the same as backup. i.e. if it takes 10 minutes to backup, it'll
take about 10 minutes to restore. Plus any time to fix up minor issues.
However, let's say you start a backup at 5:01 PM.
What happens if your DB crashes at 5:00 PM. Can you afford to lose a day's
worth of data?
> Thanks
>
Capacity Planning
We are going to install a call centre application.
According to end user, there will be around 500 request
has to be inputted into the system.
We will use SQL Server 2000 as the DB. We would like to
know what factors we have to consider - Like recovery
model, database maintenance plan, fill factors ? Is it
necessary for us to archive some old data to an archive
datbase ?
Thanks
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:1cb701c4b569$d40000a0$a401280a@.phx.gbl...
> We are going to install a call centre application.
> According to end user, there will be around 500 request
> has to be inputted into the system.
>
500 requests over what time period?
> We will use SQL Server 2000 as the DB. We would like to
> know what factors we have to consider - Like recovery
> model, database maintenance plan, fill factors ? Is it
> necessary for us to archive some old data to an archive
> datbase ?
>
Those are really business decisions.
i.e. if you need to run 24x7 vs 9-5x5, your decisions will be different.
If you can do with downtime, you may go with a different decisions on
architecture.
As for archiving, again, that's a business decision. Do you want to archive
data or not?
> Thanks
|||Dear Greg,
It should be 500 requests between 9:00am to 5:00pm from
Monday to Friday.
We will make full database backup daily. What is the
difference between full database backup and archive then ?
Thanks
|||"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:0fba01c4b574$0e2f4830$a501280a@.phx.gbl...
> Dear Greg,
> It should be 500 requests between 9:00am to 5:00pm from
> Monday to Friday.
500 a day? That's about one a minute. You can run this thing on a desktop
machine.
> We will make full database backup daily. What is the
> difference between full database backup and archive then ?
Generally a backup is for disaster recovery. An archive is for storing data
for later analysis or for other reasons.
For example, I keep backups of only a few days (my databases generally have
enough churn that in a few days the bulk of the data has changed anyway.)
But there's certain data I archive to tape (in a different schema etc) that
I may keep for much longer.
Now, as for once a day backups, that may or may not work. Your database
sounds like it will probably be fairly small to start, so recovery time will
be about the same as backup. i.e. if it takes 10 minutes to backup, it'll
take about 10 minutes to restore. Plus any time to fix up minor issues.
However, let's say you start a backup at 5:01 PM.
What happens if your DB crashes at 5:00 PM. Can you afford to lose a day's
worth of data?
> Thanks
>
According to end user, there will be around 500 request
has to be inputted into the system.
We will use SQL Server 2000 as the DB. We would like to
know what factors we have to consider - Like recovery
model, database maintenance plan, fill factors ? Is it
necessary for us to archive some old data to an archive
datbase ?
Thanks
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:1cb701c4b569$d40000a0$a401280a@.phx.gbl...
> We are going to install a call centre application.
> According to end user, there will be around 500 request
> has to be inputted into the system.
>
500 requests over what time period?
> We will use SQL Server 2000 as the DB. We would like to
> know what factors we have to consider - Like recovery
> model, database maintenance plan, fill factors ? Is it
> necessary for us to archive some old data to an archive
> datbase ?
>
Those are really business decisions.
i.e. if you need to run 24x7 vs 9-5x5, your decisions will be different.
If you can do with downtime, you may go with a different decisions on
architecture.
As for archiving, again, that's a business decision. Do you want to archive
data or not?
> Thanks
|||Dear Greg,
It should be 500 requests between 9:00am to 5:00pm from
Monday to Friday.
We will make full database backup daily. What is the
difference between full database backup and archive then ?
Thanks
|||"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:0fba01c4b574$0e2f4830$a501280a@.phx.gbl...
> Dear Greg,
> It should be 500 requests between 9:00am to 5:00pm from
> Monday to Friday.
500 a day? That's about one a minute. You can run this thing on a desktop
machine.
> We will make full database backup daily. What is the
> difference between full database backup and archive then ?
Generally a backup is for disaster recovery. An archive is for storing data
for later analysis or for other reasons.
For example, I keep backups of only a few days (my databases generally have
enough churn that in a few days the bulk of the data has changed anyway.)
But there's certain data I archive to tape (in a different schema etc) that
I may keep for much longer.
Now, as for once a day backups, that may or may not work. Your database
sounds like it will probably be fairly small to start, so recovery time will
be about the same as backup. i.e. if it takes 10 minutes to backup, it'll
take about 10 minutes to restore. Plus any time to fix up minor issues.
However, let's say you start a backup at 5:01 PM.
What happens if your DB crashes at 5:00 PM. Can you afford to lose a day's
worth of data?
> Thanks
>
Cant't see the database
When I create a database with the administrator acount on the server in SQL 2005, it adds and I can see it (and the system databases too).
Then I added a user accout (Windows Auth), and connect to the database from the new accout, but I can't see the database I just created myself with the administrator accout (on the server) just the 'System Databases'.
I even tried to make a database with the new user account but get permission denied, even if I set dbcreator permission on the user. I get the error
"CREATE DATABASE permission denied in database 'master'".
Any ides?
Oh, i solved it by Connect, then choose the Options>> button,
And then in "Connect to database:" I choose my database.
Tuesday, February 14, 2012
Can't use system DSN to log user on
HI,
I have attempted to connect a user to a SQL 2000 server, running on a
Windows 2000 server using Windows Authentication and always get the
follwoing error message:
Connection failed
SQLstate:'28000'
sql server error: 18456
[microsoft][odbc sql server driver][sql server] login
failed for user "Domain\user1"
Can anyone explain to me why this is happening? I've looked at the
SQL Server Agent Properties and on the Connection tab it specifies use
Windows Authentication, but yet I can't get any Domain user to connect
to the server?!
Thanks,
Art
Hi,
You have to give that domain user to authenticate to SQL Server.
1. Login to SQL Server using Query analyzer with a user with sysadmin role
2. Execute the below commmands:-
sp_grantlogin '[domainname\Groupname]'
eg:
EXEC sp_grantlogin '[Finance\RPTGROUP]'
Command to give access previlage to the user to database.
sp_grantdbaccess '[domainname\Groupname]','user_name_in_database'
Eg:
use dbname
go
EXEC sp_grantdbaccess '[Finance\RPTGROUP]','RPTGROUP'
After this login to domain user and tr to create the system DSN.
Thanks
Hari
MCDBA
"Art Billings" <abillings@.principle-tech.com> wrote in message
news:8c11e0tjdn66knipdut4te4vnb92e8gbtj@.4ax.com...
> HI,
> I have attempted to connect a user to a SQL 2000 server, running on a
> Windows 2000 server using Windows Authentication and always get the
> follwoing error message:
> Connection failed
> SQLstate:'28000'
> sql server error: 18456
> [microsoft][odbc sql server driver][sql server] login
> failed for user "Domain\user1"
> Can anyone explain to me why this is happening? I've looked at the
> SQL Server Agent Properties and on the Connection tab it specifies use
> Windows Authentication, but yet I can't get any Domain user to connect
> to the server?!
> Thanks,
> Art
|||Thanks for the response to my query. Didn't expect one, so that was a
pleasant surprise. We worked it out, turns out that the Domain Users
group had not been given expicit access to any of the databases. Once
we configured that, then allowed them public access and execute rights
on the stored procedure we were developing, everything worked as smooth
as silk. Imagine that!!
Thanks again!
Art
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
I have attempted to connect a user to a SQL 2000 server, running on a
Windows 2000 server using Windows Authentication and always get the
follwoing error message:
Connection failed
SQLstate:'28000'
sql server error: 18456
[microsoft][odbc sql server driver][sql server] login
failed for user "Domain\user1"
Can anyone explain to me why this is happening? I've looked at the
SQL Server Agent Properties and on the Connection tab it specifies use
Windows Authentication, but yet I can't get any Domain user to connect
to the server?!
Thanks,
Art
Hi,
You have to give that domain user to authenticate to SQL Server.
1. Login to SQL Server using Query analyzer with a user with sysadmin role
2. Execute the below commmands:-
sp_grantlogin '[domainname\Groupname]'
eg:
EXEC sp_grantlogin '[Finance\RPTGROUP]'
Command to give access previlage to the user to database.
sp_grantdbaccess '[domainname\Groupname]','user_name_in_database'
Eg:
use dbname
go
EXEC sp_grantdbaccess '[Finance\RPTGROUP]','RPTGROUP'
After this login to domain user and tr to create the system DSN.
Thanks
Hari
MCDBA
"Art Billings" <abillings@.principle-tech.com> wrote in message
news:8c11e0tjdn66knipdut4te4vnb92e8gbtj@.4ax.com...
> HI,
> I have attempted to connect a user to a SQL 2000 server, running on a
> Windows 2000 server using Windows Authentication and always get the
> follwoing error message:
> Connection failed
> SQLstate:'28000'
> sql server error: 18456
> [microsoft][odbc sql server driver][sql server] login
> failed for user "Domain\user1"
> Can anyone explain to me why this is happening? I've looked at the
> SQL Server Agent Properties and on the Connection tab it specifies use
> Windows Authentication, but yet I can't get any Domain user to connect
> to the server?!
> Thanks,
> Art
|||Thanks for the response to my query. Didn't expect one, so that was a
pleasant surprise. We worked it out, turns out that the Domain Users
group had not been given expicit access to any of the databases. Once
we configured that, then allowed them public access and execute rights
on the stored procedure we were developing, everything worked as smooth
as silk. Imagine that!!
Thanks again!
Art
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
Can't use system DSN to log user on
HI,
I have attempted to connect a user to a SQL 2000 server, running on a
Windows 2000 server using Windows Authentication and always get the
follwoing error message:
Connection failed
SQLstate:'28000'
sql server error: 18456
[microsoft][odbc sql server driver][sql server] login
failed for user "Domain\user1"
Can anyone explain to me why this is happening? I've looked at the
SQL Server Agent Properties and on the Connection tab it specifies use
Windows Authentication, but yet I can't get any Domain user to connect
to the server'!
Thanks,
ArtHi,
You have to give that domain user to authenticate to SQL Server.
1. Login to SQL Server using Query analyzer with a user with sysadmin role
2. Execute the below commmands:-
sp_grantlogin '[domainname\Groupname]'
eg:
EXEC sp_grantlogin '[Finance\RPTGROUP]'
Command to give access previlage to the user to database.
sp_grantdbaccess '& #91;domainname\Groupname]','user_name_in
_database'
Eg:
use dbname
go
EXEC sp_grantdbaccess '[Finance\RPTGROUP]','RPTGROUP'
After this login to domain user and tr to create the system DSN.
Thanks
Hari
MCDBA
"Art Billings" <abillings@.principle-tech.com> wrote in message
news:8c11e0tjdn66knipdut4te4vnb92e8gbtj@.
4ax.com...
> HI,
> I have attempted to connect a user to a SQL 2000 server, running on a
> Windows 2000 server using Windows Authentication and always get the
> follwoing error message:
> Connection failed
> SQLstate:'28000'
> sql server error: 18456
> [microsoft][odbc sql server driver][sql server] login
> failed for user "Domain\user1"
> Can anyone explain to me why this is happening? I've looked at the
> SQL Server Agent Properties and on the Connection tab it specifies use
> Windows Authentication, but yet I can't get any Domain user to connect
> to the server'!
> Thanks,
> Art|||Thanks for the response to my query. Didn't expect one, so that was a
pleasant surprise. We worked it out, turns out that the Domain Users
group had not been given expicit access to any of the databases. Once
we configured that, then allowed them public access and execute rights
on the stored procedure we were developing, everything worked as smooth
as silk. Imagine that!!
Thanks again!
Art
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
I have attempted to connect a user to a SQL 2000 server, running on a
Windows 2000 server using Windows Authentication and always get the
follwoing error message:
Connection failed
SQLstate:'28000'
sql server error: 18456
[microsoft][odbc sql server driver][sql server] login
failed for user "Domain\user1"
Can anyone explain to me why this is happening? I've looked at the
SQL Server Agent Properties and on the Connection tab it specifies use
Windows Authentication, but yet I can't get any Domain user to connect
to the server'!
Thanks,
ArtHi,
You have to give that domain user to authenticate to SQL Server.
1. Login to SQL Server using Query analyzer with a user with sysadmin role
2. Execute the below commmands:-
sp_grantlogin '[domainname\Groupname]'
eg:
EXEC sp_grantlogin '[Finance\RPTGROUP]'
Command to give access previlage to the user to database.
sp_grantdbaccess '& #91;domainname\Groupname]','user_name_in
_database'
Eg:
use dbname
go
EXEC sp_grantdbaccess '[Finance\RPTGROUP]','RPTGROUP'
After this login to domain user and tr to create the system DSN.
Thanks
Hari
MCDBA
"Art Billings" <abillings@.principle-tech.com> wrote in message
news:8c11e0tjdn66knipdut4te4vnb92e8gbtj@.
4ax.com...
> HI,
> I have attempted to connect a user to a SQL 2000 server, running on a
> Windows 2000 server using Windows Authentication and always get the
> follwoing error message:
> Connection failed
> SQLstate:'28000'
> sql server error: 18456
> [microsoft][odbc sql server driver][sql server] login
> failed for user "Domain\user1"
> Can anyone explain to me why this is happening? I've looked at the
> SQL Server Agent Properties and on the Connection tab it specifies use
> Windows Authentication, but yet I can't get any Domain user to connect
> to the server'!
> Thanks,
> Art|||Thanks for the response to my query. Didn't expect one, so that was a
pleasant surprise. We worked it out, turns out that the Domain Users
group had not been given expicit access to any of the databases. Once
we configured that, then allowed them public access and execute rights
on the stored procedure we were developing, everything worked as smooth
as silk. Imagine that!!
Thanks again!
Art
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
Subscribe to:
Posts (Atom)