Auto Data Extraction through ODBC

Hi,

Could you please help me to find easiest way to schedule daily auto data extraction time in SQL Server Express 2005 Edition (I need to put time to load data every day).

Thanks

Amir

hi Amir,

please excuse my poor english, but can you please rephrase your question?

thank you and regards

|||

For SQL Express, you would most likely need to do the following:

1. Create a script file using bcp to unload the data.

2. Use SQLCmd.exe to run the script file

3. Use Windows Scheduler to execute SQLCmd.exe on a time schedule.

Look up using [ bcp ] in books Online

Look up using SQLCmd.exe in Books Online.

Look up using Windows Scheduler in Windows Help.

|||

Hi,

Thanks for your reply, I have gone through BCP link http://msdn2.microsoft.com/en-us/library/ms162802.aspx, I am wondering if you can provide a link of Sample "Sample Script of BCP to import" it would be great help for me.

Thanks

Amir

|||

Perhaps this will help you.

http://msdn2.microsoft.com/en-us/library/aa173839(SQL.80).aspx

|||

Thanks for info.

It might be a silly question for you but I am using first time and I have no idea could you please define below also

a) Should I creat Batch file OR Text File for BCP

b) How should I run and test

|||

I normally consider a 'batch file' as an input source, and a 'text file' as an output source.

Look up bcp in Books Online, Topic: bcp Utility.

There are a couple of examples that will execute in your query window.

Authorization problems with SQL Developer's edition

I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.
I would try to connect to it via its IP address using a SQL Server login just
in case it is a DNS issue. Just a thought...
Thomas
"Steve Z" wrote:

> I just installed developer's edition on a new laptop. Other machines in the
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instance
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.
|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
[vbcol=seagreen]
> I would try to connect to it via its IP address using a SQL Server login just
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:

Authorization problems with SQL Developer's edition

I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.I would try to connect to it via its IP address using a SQL Server login just
in case it is a DNS issue. Just a thought...
--
Thomas
"Steve Z" wrote:
> I just installed developer's edition on a new laptop. Other machines in the
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instance
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
> I would try to connect to it via its IP address using a SQL Server login just
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
> > I just installed developer's edition on a new laptop. Other machines in the
> > network cannot connect to this new instance.
> >
> > At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> > (we are inside a small network anyway - no need for local firewalls - I
> > guess).
> >
> > Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> > username under COMPUTER MANAGEMENT and disabled it.
> >
> > Now it's getting login failed for user NULL.
> >
> > Seems it's not on the network like the old laptop was. The old laptop did
> > not authenticate to the network, it logged in locally, but the SQL instance
> > was visible and connectable.
> >
> > I cannot seem to add DOMAIN\usernames to this instance.
> >
> > Any direction would be greatly appreciated.

Authorization problems with SQL Developer's edition

I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.I would try to connect to it via its IP address using a SQL Server login jus
t
in case it is a DNS issue. Just a thought...
--
Thomas
"Steve Z" wrote:

> I just installed developer's edition on a new laptop. Other machines in t
he
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall featur
e
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instanc
e
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
[vbcol=seagreen]
> I would try to connect to it via its IP address using a SQL Server login j
ust
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
>sql

Authentification problem with SQL Server 2000

Hello !
We use SQL Server 2000 (standard edition) under Windows 2003 Server.
Due to a hardware failure, we have fully set up the server after having
formating the hard drives. After having installed Windows Server 2003, we
have installed SQL Server 2000, then we have restored the databases from our
last night SQL backup.
Curiously : all our Windows XP users can connect to the server, but not our
Windows 2000 users! We have tried to create an ODBC data source with Windows
authentication : failure. With SQL authentication : failure.
But the same user, with his same userid, on another PC under Windows XP : no
problem.
And it was working well before the crash. Can anybody give us an explanation
? a solution ? a help ?
Thank you,
GilbertDo you have TCP/IP enabled on the SQL Server as an allowed connection type?
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Hello !
> We use SQL Server 2000 (standard edition) under Windows 2003 Server.
> Due to a hardware failure, we have fully set up the server after having
> formating the hard drives. After having installed Windows Server 2003, we
> have installed SQL Server 2000, then we have restored the databases from
> our last night SQL backup.
> Curiously : all our Windows XP users can connect to the server, but not
> our Windows 2000 users! We have tried to create an ODBC data source with
> Windows authentication : failure. With SQL authentication : failure.
> But the same user, with his same userid, on another PC under Windows XP :
> no problem.
> And it was working well before the crash. Can anybody give us an
> explanation ? a solution ? a help ?
> Thank you,
> Gilbert
>|||Hi Warren,
Thank you for your answer. Could you tell us where to look at, to answer
your question ?
Gilbert
"Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
> Do you have TCP/IP enabled on the SQL Server as an allowed connection
> type?
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
> "Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
> news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
>|||http://technet.microsoft.com/en-us/...y/ms174212.aspx
You need to use the SQL Server configuration manager which has an option for
viewing which connections are allowed...
Its under your start menu programs in the same group as SQL Server...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
> Hi Warren,
> Thank you for your answer. Could you tell us where to look at, to answer
> your question ?
> Gilbert
> "Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
> news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
>|||Hi Warren,
Sorry to be a bit late, but : Thank you !
And a Happy New Year,
Gilbert
"Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
news: OJDKPu5QIHA.5288@.TK2MSFTNGP04.phx.gbl...
> http://technet.microsoft.com/en-us/...y/ms174212.aspx
> You need to use the SQL Server configuration manager which has an option
> for viewing which connections are allowed...
> Its under your start menu programs in the same group as SQL Server...
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
>
> "Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
> news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
>

Authentication/Security Issue!

Hi,
I have installed SQL reporting services on the local system test machine
[standard edition] which points to a DB that is on a different machine.
Everything works ok if I use a domain account and assign security rights for
each report. But in production I will want to have a local windows account
and assign read rights on the reports individually. I tried doing this in
the test environment.
When I try to access the site using the IP I get the windows log on box.
After entering the local user account I can get to the reports but as soon
as I try and run the report it gives me this error:
The permissions granted to user [domain\user] are insufficient for
performing this operation. (rsAccessDenied)
The problem is i am not logged on as a domain user but as a local machine
user.
Was wondering if any of you have come across this error before and possibly
know the cause/solution to this.
Thanks for your help!
Regards
AnilHi Anil:
Even if you go to an IP address for the server, when you run a report
the report is rendered by an IFRAME element with the URL pointing to
the report server by name.
To verify this behavior, just right-click in the report area, select
properties, and look at the URL. You'll notice your address bar might
look like http://x.x.x.x, but the report properties URL will indicate
http://reporting. The server always uses the <ReportServerUrl> element
in RSWebApplication.config.
Since the IFRAME points you back to the server by name, IE is probably
automatically logging you in again with your domain account, which is
not in a Browse role. You can change IE's behavior in Tools ->
Internet Options -> Security -> Custom Level -> User Authentication
(at the bottom of the list).
--
Scott
http://www.OdeToCode.com
On Mon, 16 Aug 2004 12:31:41 +1200, "anil" <test@.test.com> wrote:
>Hi,
>I have installed SQL reporting services on the local system test machine
>[standard edition] which points to a DB that is on a different machine.
>Everything works ok if I use a domain account and assign security rights for
>each report. But in production I will want to have a local windows account
>and assign read rights on the reports individually. I tried doing this in
>the test environment.
>When I try to access the site using the IP I get the windows log on box.
>After entering the local user account I can get to the reports but as soon
>as I try and run the report it gives me this error:
>
>The permissions granted to user [domain\user] are insufficient for
>performing this operation. (rsAccessDenied)
>The problem is i am not logged on as a domain user but as a local machine
>user.
>Was wondering if any of you have come across this error before and possibly
>know the cause/solution to this.
>Thanks for your help!
>Regards
>Anil
>

Authentication With RS 2000

I am using RS 2000 Eval Edition
I have just enstalled it on my notebook. This is where my existing copy of
SQL Server 2000 resides. The SQL 2000 Server is working fine (as it has for
the past several months)
I installed RS 2000 Eval Edition using all of the "default" settings. I
then re-booted, and installed both RS 2000 Service Packages. ASP.net is
running, and I have verified this.
When I try to open the Report Manager a window pops up and states an
Authentication Required. It prompts me for a User Name and Password. When I
try to type in the Windows User Name and password, it fails. When I try to
type in the Username and password for the SQL 2000 Database it fails.
What am I doing wrong. I have installed RS 2000 Eval on another computer
several years ago so I know what the Report Manager looks like.
Further, I have tried simply going to the Internet and typing in several
variations of: http://<ServerName> directly. Each time it prompts for
Authentication.
I am becoming very frustrated and very angry. It should not be so difficult.
Any suggestions would be welcomed. Also, I have been asked to undertake
this work using SQL 2000 and RS 2000 so please don't tell me to get of of the
dark ages and upgrade to SQL 2005 and RS 2005!
PatHi Again...
I solved my problem by changing the Anonymous Access and Authentication
Control settings in the Default Website folder in my IIS settings.
Thanks
Pat
"Pat (Disciple of Aloof-ism)" wrote:
> I am using RS 2000 Eval Edition
> I have just enstalled it on my notebook. This is where my existing copy of
> SQL Server 2000 resides. The SQL 2000 Server is working fine (as it has for
> the past several months)
> I installed RS 2000 Eval Edition using all of the "default" settings. I
> then re-booted, and installed both RS 2000 Service Packages. ASP.net is
> running, and I have verified this.
> When I try to open the Report Manager a window pops up and states an
> Authentication Required. It prompts me for a User Name and Password. When I
> try to type in the Windows User Name and password, it fails. When I try to
> type in the Username and password for the SQL 2000 Database it fails.
> What am I doing wrong. I have installed RS 2000 Eval on another computer
> several years ago so I know what the Report Manager looks like.
> Further, I have tried simply going to the Internet and typing in several
> variations of: http://<ServerName> directly. Each time it prompts for
> Authentication.
> I am becoming very frustrated and very angry. It should not be so difficult.
> Any suggestions would be welcomed. Also, I have been asked to undertake
> this work using SQL 2000 and RS 2000 so please don't tell me to get of of the
> dark ages and upgrade to SQL 2005 and RS 2005!
> Pat
>

Authentication problem on 2005 Express Edition

I'll start from the beginning: I have a Windows application developed in C#.
It uses a SQL Server 2005 Express Edition database to store data. Now I have
created a deployment of this app and database, and I try to install it on my
own machine. No problems, works without errors.
Now, I put this deployment project on the network and a user downloads it to
his Vista machine and runs the setup. When he starts the app he gets the
following error message:
"Login failed for user "MyUser". The user is not associated with a thrusted
server connection".
The connection string I use in my application is this:
Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks
In the SQL Server Management Studio Express I have already marked the "SQL
Server and Windows authentication mode" (mixed mode?) under
server/options/security. If
there is anywhere else this should be set, please let me know.
Since I have no control over the Vista machine, I can't force him/her to
create a new account that is thrusted. All I want is to deploy my app and
database, without having to worry about authorization and any other weird
stuff, since in many cases I don't know the setup on each box.
I have already tried alot of the suggestions I've found, but let's start all
over so it will be right. What should I do to remove this error? How can I
deploy my database without having to think about authorization/security
stuff?
TIA
PZ
To resolve your issue, tell me how you defined the User MyUser at MyDB level;
is it mapped to a login? In this case, the login is a Windows login or a SQL
login?
If it is a Windows login (...CREATE LOGIN loginname FROM WINDOWS...) it
should map a Domain Account, otherwise on the new machine it will be not
authenticated, and yolu should script a new login and remap the MyUser to
this new login.
Gilberto Zampatti
> I'll start from the beginning: I have a Windows application developed in C#.
> It uses a SQL Server 2005 Express Edition database to store data. Now I have
> created a deployment of this app and database, and I try to install it on my
> own machine. No problems, works without errors.
> Now, I put this deployment project on the network and a user downloads it to
> his Vista machine and runs the setup. When he starts the app he gets the
> following error message:
> "Login failed for user "MyUser". The user is not associated with a thrusted
> server connection".
> The connection string I use in my application is this:
> Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks
> In the SQL Server Management Studio Express I have already marked the "SQL
> Server and Windows authentication mode" (mixed mode?) under
> server/options/security. If
> there is anywhere else this should be set, please let me know.
> Since I have no control over the Vista machine, I can't force him/her to
> create a new account that is thrusted. All I want is to deploy my app and
> database, without having to worry about authorization and any other weird
> stuff, since in many cases I don't know the setup on each box.
> I have already tried alot of the suggestions I've found, but let's start all
> over so it will be right. What should I do to remove this error? How can I
> deploy my database without having to think about authorization/security
> stuff?
> TIA
> PZ
>
>
|||Hi Gilberto
Sounds reasonable. I'll try to describe it here, so you can determine if I
am missing something (please note that I use Server Management Studio
Express on my development machine to deal with these issues, while I don't
setup anything on the deployment machine and I run no scripts):
- First of all, I want to create everything on database level/scope, so when
the database is deployed the user installing it don't have to create/change
any user/authenticaion in Windows at all.
- I have created a new User account in the database "MyDB" scope (under
"SQLExpress\databases\MyDB\Security\Users". This user is called "MyUser"
- This user is given 2 role memberships: db_datareader and db_datawriter
- This user is not set to any schema ownerships and no extended properties
are added
- Under the "SQLExpress\databases\MyDB\properties" I have added the user
"MyUser" as type "User" and given him the following explicit permissions:
Connect, Insert, Update, Delete, Execute
I have also created this user under "SQLExpress\Security\Logins" and
selected the option "SQL Server authentication" without selecting "Enforce
password policy". However, I fail to se if this is required, since this is
not on database level, but on server level. And I only deploy the database
files. Could it be that I'm missing this user on the other server under
"Logins"? Is that why I need a script to create it?
Can you explain to me how the database is deployed on the other machine?
Does it also create a server object and store the database MyDB within? In
that case, it could be true that I need to run some scripts to put that new
server object up-to-date?
Please advise.
Regards,
PZ
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:EF361E5F-D149-4006-8E5E-C0001E03E511@.microsoft.com...[vbcol=seagreen]
> To resolve your issue, tell me how you defined the User MyUser at MyDB
> level;
> is it mapped to a login? In this case, the login is a Windows login or a
> SQL
> login?
> If it is a Windows login (...CREATE LOGIN loginname FROM WINDOWS...) it
> should map a Domain Account, otherwise on the new machine it will be not
> authenticated, and yolu should script a new login and remap the MyUser to
> this new login.
> Gilberto Zampatti
|||What do you mean when you write "...And I only deploy the database
> files...": did you bak-up and restore the dbfiles or detach-attache the same files or what else?
It seems to me that in the deployed instance you are not able to mat MyUser
to a valid login (remember that this mapping is made considering some "sid"
of the login and not simply the login name.
The simplest way to operate could be:
- deploy (once) an instance of SQL Express and on each instance run a script
to create a SQL login (why not a Windows login?) named xxx
- deploy your DB files
- launch a script to:
- drop MyUser
- create MyUser mapping it to the xxx login and grant him the needed
permissions
Gilberto Zampatti
"Preben Zacho" wrote:

> Hi Gilberto
> Sounds reasonable. I'll try to describe it here, so you can determine if I
> am missing something (please note that I use Server Management Studio
> Express on my development machine to deal with these issues, while I don't
> setup anything on the deployment machine and I run no scripts):
> - First of all, I want to create everything on database level/scope, so when
> the database is deployed the user installing it don't have to create/change
> any user/authenticaion in Windows at all.
> - I have created a new User account in the database "MyDB" scope (under
> "SQLExpress\databases\MyDB\Security\Users". This user is called "MyUser"
> - This user is given 2 role memberships: db_datareader and db_datawriter
> - This user is not set to any schema ownerships and no extended properties
> are added
> - Under the "SQLExpress\databases\MyDB\properties" I have added the user
> "MyUser" as type "User" and given him the following explicit permissions:
> Connect, Insert, Update, Delete, Execute
> I have also created this user under "SQLExpress\Security\Logins" and
> selected the option "SQL Server authentication" without selecting "Enforce
> password policy". However, I fail to se if this is required, since this is
> not on database level, but on server level. And I only deploy the database
> files. Could it be that I'm missing this user on the other server under
> "Logins"? Is that why I need a script to create it?
> Can you explain to me how the database is deployed on the other machine?
> Does it also create a server object and store the database MyDB within? In
> that case, it could be true that I need to run some scripts to put that new
> server object up-to-date?
> Please advise.
> Regards,
> PZ
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:EF361E5F-D149-4006-8E5E-C0001E03E511@.microsoft.com...
>
>

Authentication problem on 2005 Express Edition

I'll start from the beginning: I have a Windows application developed in C#.
It uses a SQL Server 2005 Express Edition database to store data. Now I have
created a deployment of this app and database, and I try to install it on my
own machine. No problems, works without errors.
Now, I put this deployment project on the network and a user downloads it to
his Vista machine and runs the setup. When he starts the app he gets the
following error message:
"Login failed for user "MyUser". The user is not associated with a thrusted
server connection".
The connection string I use in my application is this:
Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks
In the SQL Server Management Studio Express I have already marked the "SQL
Server and Windows authentication mode" (mixed mode?) under
server/options/security. If
there is anywhere else this should be set, please let me know.
Since I have no control over the Vista machine, I can't force him/her to
create a new account that is thrusted. All I want is to deploy my app and
database, without having to worry about authorization and any other weird
stuff, since in many cases I don't know the setup on each box.
I have already tried alot of the suggestions I've found, but let's start all
over so it will be right. What should I do to remove this error? How can I
deploy my database without having to think about authorization/security
stuff?
TIA
PZTo resolve your issue, tell me how you defined the User MyUser at MyDB level
;
is it mapped to a login? In this case, the login is a Windows login or a SQL
login?
If it is a Windows login (...CREATE LOGIN loginname FROM WINDOWS...) it
should map a Domain Account, otherwise on the new machine it will be not
authenticated, and yolu should script a new login and remap the MyUser to
this new login.
Gilberto Zampatti
> I'll start from the beginning: I have a Windows application developed in C
#.
> It uses a SQL Server 2005 Express Edition database to store data. Now I ha
ve
> created a deployment of this app and database, and I try to install it on
my
> own machine. No problems, works without errors.
> Now, I put this deployment project on the network and a user downloads it
to
> his Vista machine and runs the setup. When he starts the app he gets the
> following error message:
> "Login failed for user "MyUser". The user is not associated with a thruste
d
> server connection".
> The connection string I use in my application is this:
> Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks
> In the SQL Server Management Studio Express I have already marked the "SQL
> Server and Windows authentication mode" (mixed mode?) under
> server/options/security. If
> there is anywhere else this should be set, please let me know.
> Since I have no control over the Vista machine, I can't force him/her to
> create a new account that is thrusted. All I want is to deploy my app and
> database, without having to worry about authorization and any other weird
> stuff, since in many cases I don't know the setup on each box.
> I have already tried alot of the suggestions I've found, but let's start a
ll
> over so it will be right. What should I do to remove this error? How can I
> deploy my database without having to think about authorization/security
> stuff?
> TIA
> PZ
>
>|||Hi Gilberto
Sounds reasonable. I'll try to describe it here, so you can determine if I
am missing something (please note that I use Server Management Studio
Express on my development machine to deal with these issues, while I don't
setup anything on the deployment machine and I run no scripts):
- First of all, I want to create everything on database level/scope, so when
the database is deployed the user installing it don't have to create/change
any user/authenticaion in Windows at all.
- I have created a new User account in the database "MyDB" scope (under
" SQLExpress\databases\MyDB\Security\Users
". This user is called "MyUser"
- This user is given 2 role memberships: db_datareader and db_datawriter
- This user is not set to any schema ownerships and no extended properties
are added
- Under the "SQLExpress\databases\MyDB\properties" I have added the user
"MyUser" as type "User" and given him the following explicit permissions:
Connect, Insert, Update, Delete, Execute
I have also created this user under "SQLExpress\Security\Logins" and
selected the option "SQL Server authentication" without selecting "Enforce
password policy". However, I fail to se if this is required, since this is
not on database level, but on server level. And I only deploy the database
files. Could it be that I'm missing this user on the other server under
"Logins"' Is that why I need a script to create it?
Can you explain to me how the database is deployed on the other machine?
Does it also create a server object and store the database MyDB within? In
that case, it could be true that I need to run some scripts to put that new
server object up-to-date'
Please advise.
Regards,
PZ
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:EF361E5F-D149-4006-8E5E-C0001E03E511@.microsoft.com...[vbcol=seagreen]
> To resolve your issue, tell me how you defined the User MyUser at MyDB
> level;
> is it mapped to a login? In this case, the login is a Windows login or a
> SQL
> login?
> If it is a Windows login (...CREATE LOGIN loginname FROM WINDOWS...) it
> should map a Domain Account, otherwise on the new machine it will be not
> authenticated, and yolu should script a new login and remap the MyUser to
> this new login.
> Gilberto Zampatti|||What do you mean when you write "...And I only deploy the database
> files...": did you bak-up and restore the dbfiles or detach-attache the same files
or what else?
It seems to me that in the deployed instance you are not able to mat MyUser
to a valid login (remember that this mapping is made considering some "sid"
of the login and not simply the login name.
The simplest way to operate could be:
- deploy (once) an instance of SQL Express and on each instance run a script
to create a SQL login (why not a Windows login?) named xxx
- deploy your DB files
- launch a script to:
- drop MyUser
- create MyUser mapping it to the xxx login and grant him the needed
permissions
Gilberto Zampatti
"Preben Zacho" wrote:

> Hi Gilberto
> Sounds reasonable. I'll try to describe it here, so you can determine if I
> am missing something (please note that I use Server Management Studio
> Express on my development machine to deal with these issues, while I don't
> setup anything on the deployment machine and I run no scripts):
> - First of all, I want to create everything on database level/scope, so wh
en
> the database is deployed the user installing it don't have to create/chang
e
> any user/authenticaion in Windows at all.
> - I have created a new User account in the database "MyDB" scope (under
> " SQLExpress\databases\MyDB\Security\Users
". This user is called "MyUser"
> - This user is given 2 role memberships: db_datareader and db_datawriter
> - This user is not set to any schema ownerships and no extended properties
> are added
> - Under the "SQLExpress\databases\MyDB\properties" I have added the user
> "MyUser" as type "User" and given him the following explicit permissions:
> Connect, Insert, Update, Delete, Execute
> I have also created this user under "SQLExpress\Security\Logins" and
> selected the option "SQL Server authentication" without selecting "Enforce
> password policy". However, I fail to se if this is required, since this is
> not on database level, but on server level. And I only deploy the database
> files. Could it be that I'm missing this user on the other server under
> "Logins"' Is that why I need a script to create it?
> Can you explain to me how the database is deployed on the other machine?
> Does it also create a server object and store the database MyDB within? In
> that case, it could be true that I need to run some scripts to put that ne
w
> server object up-to-date'
> Please advise.
> Regards,
> PZ
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:EF361E5F-D149-4006-8E5E-C0001E03E511@.microsoft.com...
>
>

Authentication problem on 2005 Express Edition

I'll start from the beginning: I have a Windows application developed in C#.
It uses a SQL Server 2005 Express Edition database to store data. Now I have
created a deployment of this app and database, and I try to install it on my
own machine. No problems, works without errors.
Now, I put this deployment project on the network and a user downloads it to
his Vista machine and runs the setup. When he starts the app he gets the
following error message:
"Login failed for user "MyUser". The user is not associated with a thrusted
server connection".
The connection string I use in my application is this:
Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks
In the SQL Server Management Studio Express I have already marked the "SQL
Server and Windows authentication mode" (mixed mode?) under
server/options/security. If
there is anywhere else this should be set, please let me know.
Since I have no control over the Vista machine, I can't force him/her to
create a new account that is thrusted. All I want is to deploy my app and
database, without having to worry about authorization and any other weird
stuff, since in many cases I don't know the setup on each box.
I have already tried alot of the suggestions I've found, but let's start all
over so it will be right. What should I do to remove this error? How can I
deploy my database without having to think about authorization/security
stuff?
TIA
PZTo resolve your issue, tell me how you defined the User MyUser at MyDB level;
is it mapped to a login? In this case, the login is a Windows login or a SQL
login?
If it is a Windows login (...CREATE LOGIN loginname FROM WINDOWS...) it
should map a Domain Account, otherwise on the new machine it will be not
authenticated, and yolu should script a new login and remap the MyUser to
this new login.
Gilberto Zampatti
> I'll start from the beginning: I have a Windows application developed in C#.
> It uses a SQL Server 2005 Express Edition database to store data. Now I have
> created a deployment of this app and database, and I try to install it on my
> own machine. No problems, works without errors.
> Now, I put this deployment project on the network and a user downloads it to
> his Vista machine and runs the setup. When he starts the app he gets the
> following error message:
> "Login failed for user "MyUser". The user is not associated with a thrusted
> server connection".
> The connection string I use in my application is this:
> Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks
> In the SQL Server Management Studio Express I have already marked the "SQL
> Server and Windows authentication mode" (mixed mode?) under
> server/options/security. If
> there is anywhere else this should be set, please let me know.
> Since I have no control over the Vista machine, I can't force him/her to
> create a new account that is thrusted. All I want is to deploy my app and
> database, without having to worry about authorization and any other weird
> stuff, since in many cases I don't know the setup on each box.
> I have already tried alot of the suggestions I've found, but let's start all
> over so it will be right. What should I do to remove this error? How can I
> deploy my database without having to think about authorization/security
> stuff?
> TIA
> PZ
>
>|||Hi Gilberto
Sounds reasonable. I'll try to describe it here, so you can determine if I
am missing something (please note that I use Server Management Studio
Express on my development machine to deal with these issues, while I don't
setup anything on the deployment machine and I run no scripts):
- First of all, I want to create everything on database level/scope, so when
the database is deployed the user installing it don't have to create/change
any user/authenticaion in Windows at all.
- I have created a new User account in the database "MyDB" scope (under
"SQLExpress\databases\MyDB\Security\Users". This user is called "MyUser"
- This user is given 2 role memberships: db_datareader and db_datawriter
- This user is not set to any schema ownerships and no extended properties
are added
- Under the "SQLExpress\databases\MyDB\properties" I have added the user
"MyUser" as type "User" and given him the following explicit permissions:
Connect, Insert, Update, Delete, Execute
I have also created this user under "SQLExpress\Security\Logins" and
selected the option "SQL Server authentication" without selecting "Enforce
password policy". However, I fail to se if this is required, since this is
not on database level, but on server level. And I only deploy the database
files. Could it be that I'm missing this user on the other server under
"Logins"' Is that why I need a script to create it?
Can you explain to me how the database is deployed on the other machine?
Does it also create a server object and store the database MyDB within? In
that case, it could be true that I need to run some scripts to put that new
server object up-to-date'
Please advise.
Regards,
PZ
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:EF361E5F-D149-4006-8E5E-C0001E03E511@.microsoft.com...
> To resolve your issue, tell me how you defined the User MyUser at MyDB
> level;
> is it mapped to a login? In this case, the login is a Windows login or a
> SQL
> login?
> If it is a Windows login (...CREATE LOGIN loginname FROM WINDOWS...) it
> should map a Domain Account, otherwise on the new machine it will be not
> authenticated, and yolu should script a new login and remap the MyUser to
> this new login.
> Gilberto Zampatti
>> I'll start from the beginning: I have a Windows application developed in
>> C#.
>> It uses a SQL Server 2005 Express Edition database to store data. Now I
>> have
>> created a deployment of this app and database, and I try to install it on
>> my
>> own machine. No problems, works without errors.
>> Now, I put this deployment project on the network and a user downloads it
>> to
>> his Vista machine and runs the setup. When he starts the app he gets the
>> following error message:
>> "Login failed for user "MyUser". The user is not associated with a
>> thrusted
>> server connection".
>> The connection string I use in my application is this:
>> Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks
>> In the SQL Server Management Studio Express I have already marked the
>> "SQL
>> Server and Windows authentication mode" (mixed mode?) under
>> server/options/security. If
>> there is anywhere else this should be set, please let me know.
>> Since I have no control over the Vista machine, I can't force him/her to
>> create a new account that is thrusted. All I want is to deploy my app and
>> database, without having to worry about authorization and any other weird
>> stuff, since in many cases I don't know the setup on each box.
>> I have already tried alot of the suggestions I've found, but let's start
>> all
>> over so it will be right. What should I do to remove this error? How can
>> I
>> deploy my database without having to think about authorization/security
>> stuff?
>> TIA
>> PZ
>>|||What do you mean when you write "...And I only deploy the database
> files...": did you bak-up and restore the dbfiles or detach-attache the same files or what else?
It seems to me that in the deployed instance you are not able to mat MyUser
to a valid login (remember that this mapping is made considering some "sid"
of the login and not simply the login name.
The simplest way to operate could be:
- deploy (once) an instance of SQL Express and on each instance run a script
to create a SQL login (why not a Windows login?) named xxx
- deploy your DB files
- launch a script to:
- drop MyUser
- create MyUser mapping it to the xxx login and grant him the needed
permissions
Gilberto Zampatti
"Preben Zacho" wrote:
> Hi Gilberto
> Sounds reasonable. I'll try to describe it here, so you can determine if I
> am missing something (please note that I use Server Management Studio
> Express on my development machine to deal with these issues, while I don't
> setup anything on the deployment machine and I run no scripts):
> - First of all, I want to create everything on database level/scope, so when
> the database is deployed the user installing it don't have to create/change
> any user/authenticaion in Windows at all.
> - I have created a new User account in the database "MyDB" scope (under
> "SQLExpress\databases\MyDB\Security\Users". This user is called "MyUser"
> - This user is given 2 role memberships: db_datareader and db_datawriter
> - This user is not set to any schema ownerships and no extended properties
> are added
> - Under the "SQLExpress\databases\MyDB\properties" I have added the user
> "MyUser" as type "User" and given him the following explicit permissions:
> Connect, Insert, Update, Delete, Execute
> I have also created this user under "SQLExpress\Security\Logins" and
> selected the option "SQL Server authentication" without selecting "Enforce
> password policy". However, I fail to se if this is required, since this is
> not on database level, but on server level. And I only deploy the database
> files. Could it be that I'm missing this user on the other server under
> "Logins"' Is that why I need a script to create it?
> Can you explain to me how the database is deployed on the other machine?
> Does it also create a server object and store the database MyDB within? In
> that case, it could be true that I need to run some scripts to put that new
> server object up-to-date'
> Please advise.
> Regards,
> PZ
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:EF361E5F-D149-4006-8E5E-C0001E03E511@.microsoft.com...
> > To resolve your issue, tell me how you defined the User MyUser at MyDB
> > level;
> > is it mapped to a login? In this case, the login is a Windows login or a
> > SQL
> > login?
> > If it is a Windows login (...CREATE LOGIN loginname FROM WINDOWS...) it
> > should map a Domain Account, otherwise on the new machine it will be not
> > authenticated, and yolu should script a new login and remap the MyUser to
> > this new login.
> > Gilberto Zampatti
> >> I'll start from the beginning: I have a Windows application developed in
> >> C#.
> >> It uses a SQL Server 2005 Express Edition database to store data. Now I
> >> have
> >> created a deployment of this app and database, and I try to install it on
> >> my
> >> own machine. No problems, works without errors.
> >>
> >> Now, I put this deployment project on the network and a user downloads it
> >> to
> >> his Vista machine and runs the setup. When he starts the app he gets the
> >> following error message:
> >>
> >> "Login failed for user "MyUser". The user is not associated with a
> >> thrusted
> >> server connection".
> >>
> >> The connection string I use in my application is this:
> >>
> >> Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks
> >>
> >> In the SQL Server Management Studio Express I have already marked the
> >> "SQL
> >> Server and Windows authentication mode" (mixed mode?) under
> >> server/options/security. If
> >> there is anywhere else this should be set, please let me know.
> >>
> >> Since I have no control over the Vista machine, I can't force him/her to
> >> create a new account that is thrusted. All I want is to deploy my app and
> >> database, without having to worry about authorization and any other weird
> >> stuff, since in many cases I don't know the setup on each box.
> >>
> >> I have already tried alot of the suggestions I've found, but let's start
> >> all
> >> over so it will be right. What should I do to remove this error? How can
> >> I
> >> deploy my database without having to think about authorization/security
> >> stuff?
> >>
> >> TIA
> >>
> >> PZ
> >>
> >>
> >>
>
>sql

Authentication mode, connecting from webpage

Hello,
I need help setting up SQL Server Express edition.
What I did so far:
1) Downloaded and installed it with windows authentication
2) Installed SQL Server Management Studio Express
3) Created a database
4) Realized I needed SQL Authentication for connecting via php page.
5) Followed these instructions to enable SQL Authentication
Now that SQL Authentication is enabled, how do I create a user account that I can use in php pages to connect to the database?
Thanks,
Kurt

Hey Kurt. See the documentation in Books Online for the following commands:

CREATE LOGIN

CREATE USER

The create login statement will create a user on your server, then run the create user statement to allow that user access to the database(s) on your system.

HTH,

|||Hello,
Ok thanks, I got my user created with the following. I also realized its the same as creating a user in SQL Management Studio Express.
sqlcmd -S .\SQLEXPRESS
1>CREATE LOGIN myuser WITH PASSWORD = 'mypassword';
2>GO
Is there anything else I have to change for php to beable to connect with this user?
Thanks,
Kurt|||

You need to run the CREATE USER command to give the login you just created access to the database(s) you want it to have access to. Then you have to provide the appropriate permissions to that user within the database in question (i.e. select from tables, update tables, delete tables and records, etc., etc.)

|||Hi Chad,
I keep getting an error when I try to connect from a webpage. For the server can I use localhost?
Warning: mssql_connect(): Unable to connect to server: localhost in D:\wwwRoot\db\connect.php on line 18

Thanks,
Kurt

Attribute Limit of 5000 When Mining a Cube

I'm trying to build a association model in the Standard Edition based on an existing cube. I keep getting the error:

Error (Data mining): The 'Product Recommendations' mining model has 60385 attributes. This number of attributes exceeds the attribute limit of 5000 allowed by the current version of the algorithm associated with the mining model.

I created Cube Slice filters and those limit the Customer and Product dimensions (Product is Nested) to well under 5000. The error message also does not change. The number of attributes is equal to the number of rows in the Product dimension, but I expected the cube slice to reduce the number. I tested all the SQL used while it processes and with the MDXFilters the number of rows returned is well under 5000.

So, in short, the final questions is, is it possible to create a mining model in standard edition based on an existing cube where the nested dimension in the model has more than 5000 rows? Is there some other way to filter the query?

I guess my only choice on this if there isn't a way is to extract the data into relational table with only the rows I want to analyze....that's a huge pain and doesn't really make sense when the filters should limit the model size.

What is annoying on this is I can't find one reference anywhere on the microsoft site that this limit even exists within the product...

Thanks for any assistance on this!

This sounds like a bug (and knowing the code, I can see where it comes from).

Standard edition is limited to 5000 attributes for Standard Edition. What you are doing is perfectly legal, assuming there are actually less than 5000 attributes. You may need to contact support so we can get this fixed, or start by writing up a bug report at connect.microsoft.com. If you cannot get this resolved through support and this is blocking you, please let us know and we will see if we can make something happen.

Thanks

-Jamie

|||

Thanks...I'll get a support case open and see what happens.

- L

|||

Jamie,

I opened a support case with Microsoft and have been working with them for a few days. They did agree that this is a defect in the product. The current response is that, "they may consider a design change to account for filtered cube slices". This is a pretty big deal for our development. I'd also question the limit in general since its not even documented, does the limit really drive more sales to the Enterprise Version of the product? I think if there is a limit, it should really be much larger since in practice, 5000 rows in a nested table is so small. It is very common for small companies to have product catalogs of 60k products.

THANKS!

|||

I have been working with the support person you are in contact with. The issue isn't if the problem with be fixed, it is simply how the problem will be fixed. I believe we will have a resolution today - in any case, it will resolve the issue you are seeing.

Regarding the 5000 attribute limit, that's a completely seperate debate that I don't want to get deeply into in the forums. I would only state that the differentiation between the various editions isn't limited to data volumes, functional differences arise as well (e.g. data mining transforms in Integration Services, etc.). Your cost structure in general may not support a wholesale changeover to Enterprise edition due to data volumes, but the ROI of some of the features that are made available in the larger edition may warrant an upgrade on a single machine. There are different licensing options for this as well, i.e. server CAL vs Processor licences, which for a small-medium size business, a 50-CAL Enterprise license may do the trick and still be in the affordable price range.

If you want to contact me directly, it's Jamie <dot> MacLennan <at> microsoft <dot> com

Thanks

Attribute Limit of 5000 When Mining a Cube

I'm trying to build a association model in the Standard Edition based on an existing cube. I keep getting the error:

Error (Data mining): The 'Product Recommendations' mining model has 60385 attributes. This number of attributes exceeds the attribute limit of 5000 allowed by the current version of the algorithm associated with the mining model.

I created Cube Slice filters and those limit the Customer and Product dimensions (Product is Nested) to well under 5000. The error message also does not change. The number of attributes is equal to the number of rows in the Product dimension, but I expected the cube slice to reduce the number. I tested all the SQL used while it processes and with the MDXFilters the number of rows returned is well under 5000.

So, in short, the final questions is, is it possible to create a mining model in standard edition based on an existing cube where the nested dimension in the model has more than 5000 rows? Is there some other way to filter the query?

I guess my only choice on this if there isn't a way is to extract the data into relational table with only the rows I want to analyze....that's a huge pain and doesn't really make sense when the filters should limit the model size.

What is annoying on this is I can't find one reference anywhere on the microsoft site that this limit even exists within the product...

Thanks for any assistance on this!

This sounds like a bug (and knowing the code, I can see where it comes from).

Standard edition is limited to 5000 attributes for Standard Edition. What you are doing is perfectly legal, assuming there are actually less than 5000 attributes. You may need to contact support so we can get this fixed, or start by writing up a bug report at connect.microsoft.com. If you cannot get this resolved through support and this is blocking you, please let us know and we will see if we can make something happen.

Thanks

-Jamie

|||

Thanks...I'll get a support case open and see what happens.

- L

|||

Jamie,

I opened a support case with Microsoft and have been working with them for a few days. They did agree that this is a defect in the product. The current response is that, "they may consider a design change to account for filtered cube slices". This is a pretty big deal for our development. I'd also question the limit in general since its not even documented, does the limit really drive more sales to the Enterprise Version of the product? I think if there is a limit, it should really be much larger since in practice, 5000 rows in a nested table is so small. It is very common for small companies to have product catalogs of 60k products.

THANKS!

|||

I have been working with the support person you are in contact with. The issue isn't if the problem with be fixed, it is simply how the problem will be fixed. I believe we will have a resolution today - in any case, it will resolve the issue you are seeing.

Regarding the 5000 attribute limit, that's a completely seperate debate that I don't want to get deeply into in the forums. I would only state that the differentiation between the various editions isn't limited to data volumes, functional differences arise as well (e.g. data mining transforms in Integration Services, etc.). Your cost structure in general may not support a wholesale changeover to Enterprise edition due to data volumes, but the ROI of some of the features that are made available in the larger edition may warrant an upgrade on a single machine. There are different licensing options for this as well, i.e. server CAL vs Processor licences, which for a small-medium size business, a 50-CAL Enterprise license may do the trick and still be in the affordable price range.

If you want to contact me directly, it's Jamie <dot> MacLennan <at> microsoft <dot> com

Thanks

Attempts to made backup on the network drive are failed

MS SQL Server 2000 Enterprise Edition Service Pack 3
on MS Windows Advanced Server Service Pack 4
Attempts to made backup on the network drive are failed.
There are two databases with this feature. One has 1400Mb data and 100Mb
log. Another has 4410Mb data and 1000Mb log.
First database has about 80% successful attempts. Second - only 10%. However
there are a lot of databases about 300-500Mb that are backed up successfully
always and one that has 4100Mb data and 1000Mb log, that is backed up
successfully always.
Backups on the local drives are always successful.
Copying entire catalog \data (about 20Gb mdf and ldf files) on the same
network drive is always successful.
Symptoms:
After issuing this statement:
backup database LargeDB to
disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
we have result:
1 percent backed up.
2 percent backed up.
3 percent backed up.
................
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 563608 pages for database 'LargeDB', file 'LargeDBData' on file 1.
100 percent backed up.
Processed 1 pages for database 'LargeDB', file 'LargeDBlog' on file 1.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL Server log contains two records:
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\server001\backup2\mssql\LargeDB_20031209.bak'. Operating system error
64(error not found).
BACKUP failed to complete the command backup database LargeDB to
disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
Application event log contains two records:
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\server001\backup2\mssql\LargeDB_20031209.bak'. Operating system error
64(error not found).
3041 :
BACKUP failed to complete the command backup database LargeDB to
disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
System event log has no records
Events logs from file server has no records.
Attempt to restore from the "unsuccessful" backup file always is successful.
What should I do?|
| MS SQL Server 2000 Enterprise Edition Service Pack 3
| on MS Windows Advanced Server Service Pack 4
|
| Attempts to made backup on the network drive are failed.
| There are two databases with this feature. One has 1400Mb data and 100Mb
| log. Another has 4410Mb data and 1000Mb log.
| First database has about 80% successful attempts. Second - only 10%.
However
| there are a lot of databases about 300-500Mb that are backed up
successfully
| always and one that has 4100Mb data and 1000Mb log, that is backed up
| successfully always.
| Backups on the local drives are always successful.
| Copying entire catalog \data (about 20Gb mdf and ldf files) on the same
| network drive is always successful.
|
| Symptoms:
| After issuing this statement:
| backup database LargeDB to
| disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
| we have result:
| 1 percent backed up.
| 2 percent backed up.
| 3 percent backed up.
| ................
| 97 percent backed up.
| 98 percent backed up.
| 99 percent backed up.
| Processed 563608 pages for database 'LargeDB', file 'LargeDBData' on file
1.
| 100 percent backed up.
| Processed 1 pages for database 'LargeDB', file 'LargeDBlog' on file 1.
| Server: Msg 3013, Level 16, State 1, Line 1
| BACKUP DATABASE is terminating abnormally.
|
| SQL Server log contains two records:
| BackupDiskFile::RequestDurableMedia: failure on backup device
| '\\server001\backup2\mssql\LargeDB_20031209.bak'. Operating system error
| 64(error not found).
| BACKUP failed to complete the command backup database LargeDB to
| disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
|
| Application event log contains two records:
| 18210 :
| BackupDiskFile::RequestDurableMedia: failure on backup device
| '\\server001\backup2\mssql\LargeDB_20031209.bak'. Operating system error
| 64(error not found).
| 3041 :
| BACKUP failed to complete the command backup database LargeDB to
| disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
| System event log has no records
|
| Events logs from file server has no records.
|
| Attempt to restore from the "unsuccessful" backup file always is
successful.
|
| What should I do?
--
Go to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
eters\SessTimeout
Increase this value to 600 (10 minutes) and see how you go.
Hope this helps,
--
Eric Cárdenas
SQL Server support

Attached .mdf file security settings

I'm having some problems with SQL Server 2005. I installed the Personal Starter kit but don't have the Express edition installed so I attached the .mdf file to SQL Server 2005. That's ok and I also changed the connection string to integrated security.
<add name="Personal" connectionString="Data Source=MyTestServer;Initial Catalog=Personal;Integrated Security=True" providerName="System.Data.SqlClient"/>
I tried setting the security settings in the Management studio under Security | Logins | BUILTIN\Administrators where I select the User mapping and check the checkbox before the Personal.mdf file. But this doesn't seem to do the trick. How can I set the correct security settings?
Please, does someone here know an answer for this?
|||It seemed that the attached .mdf file got the position on the hard drive (c:\...\personal.mdf) instead of the proper name. After changing that with the sp_renamedb command I could get it to work.

AttachDBFileName

Group,
Does the AttachDBFileName requires a running SQL Server Express (or any
edition) on that server?
Meaning, can it be accessed like MS Access, not necessarily need a software
installed on that computer, though using OLEDB or connecting with ODBC,
DSN-less still allow you to connect to that database.
Please help.Even Access requires that software be installed on the computer.
AttachDBFileName points to an attachable SQLS database file in a
SqlClient connection string. Here's some links to the relevant
documentation:
http://msdn2.microsoft.com/en-us/library/ms254499.aspx
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring.aspx
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnectionstringbuilder.attachdbfilename.aspx
--Mary
On Fri, 16 Feb 2007 09:50:32 -0800, Ronin
<Ronin@.discussions.microsoft.com> wrote:
>Group,
>Does the AttachDBFileName requires a running SQL Server Express (or any
>edition) on that server?
>Meaning, can it be accessed like MS Access, not necessarily need a software
>installed on that computer, though using OLEDB or connecting with ODBC,
>DSN-less still allow you to connect to that database.
>
>Please help.|||The software doesn't necessarily have to be on "that" computer. SQL Server
needs to be running on some machine to which your PC or program has access.
You can't use a database file without first attaching it to an installed
instance of SQL Server and the database file must be local to the server -
on direct-attached or SAN storage but not on a NAS or network drive.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--