New Server Registration offers no Server Name options

Real newbie question this, I suppose. (Apologies if in the wrong forum!)

Have just downloaded and installed SQL Server Express. When I attempt to start it up, the New Server Registration dialogue box appears. When I attempt to enter a Server Name, there are no options in the drop-down box except <Browse for more>, which then offers me neither Local Servers or Network Servers.

The machine is running XP Pro and I wish to use the SQL package to develop on the PC as a stand-alone environment while I evaluate it.

So what am I doing wrong?

Many thanks in advance for any help.

I have been looking through previous threads and camce across an entry from Mike Wachal, who suggested typing the following into a command window.

SQLCmd -S .\sqlexpress -E

The response was 'SQLCmd is not recognized as an internal or external command, operable program or batch file'. Is this anything to do with my problem?

|||

Duh! I realized that I had only downloaded the Management Studio package and not SQL Server itself. All working now ...

New problem getting data from xml table in sql db (Newbie)

Hello,

I have this xml tablerow in a table in my db.

2 examples

<Toyconfiguration version = "1" name = "Lego">

<Ballconfiguration version = "2020" name= "Adidas">

If I would want to get the name of the toy or ball I would write

Select

Tablerow.value('((@.name)[1]', 'varchar(100)')

From table

This would return Lego and Adidas

But what if I want to know which kind of configuration it is? How do I do this?

The answer I want is Toyconfiguration and Ballconfiguration..

Any help would be appreciated!

You could use local-name() function:

select

Tablerow.xml_col.value('(//@.name)[1]', 'varchar(100)')

,Tablerow.xml_col.value('local-name((*[@.name])[1])', 'varchar(100)')

from TableRow

|||

Kontantin,

Thanks a bunch for your answer. You saved me!!!

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'm
> getting EXECUTE permission errors when calling sprocs. I know how to grant
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not coming
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>|||oooh, uncharted territory! - scary and exciting :)
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
>> I'm a newbie to the admin side of SqlServer. I created a new login:
>> <code>
>> CREATE LOGIN pmd_app
>> WITH PASSWORD='********'
>> </code>
>>
>> I then used the "Server Management Studio Express" to create a new user
>> in
>> my DB with the same name, then give the logical permissions, at least
>> logical to me. I can read and write table data with this new user, but
>> I'm
>> getting EXECUTE permission errors when calling sprocs. I know how to
>> grant
>> permissions to a user on a per object basis, but what role memberships
>> should I be using to give them EXECUTE permissions to all new sprocs that
>> I
>> create?
>> I'm looking over BOL to see if I can find the answer, but so far not
>> coming
>> up with anything.
>> Also, if anyone knows a good place to find an article covering SQLServer
>> security, role, permission, schemas, etc that would be awesome ;)
>> Thanks for any help,
>> Steve
>>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
>> getting EXECUTE permission errors when calling sprocs. I know how to
>> grant permissions to a user on a per object basis, but what role
>> memberships
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know :)
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve
>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>> I'm a newbie to the admin side of SqlServer. I created a new login:
>> <code>
>> CREATE LOGIN pmd_app
>> WITH PASSWORD='********'
>> </code>
>>
>> I then used the "Server Management Studio Express" to create a new user
>> in my DB with the same name, then give the logical permissions, at least
>> logical to me. I can read and write table data with this new user, but
>> I'm getting EXECUTE permission errors when calling sprocs. I know how to
>> grant permissions to a user on a per object basis, but what role
>> memberships should I be using to give them EXECUTE permissions to all new
>> sprocs that I create?
>> I'm looking over BOL to see if I can find the answer, but so far not
>> coming up with anything.
>> Also, if anyone knows a good place to find an article covering SQLServer
>> security, role, permission, schemas, etc that would be awesome ;)
>> Thanks for any help,
>> Steve
>

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve
> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:

> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'm
> getting EXECUTE permission errors when calling sprocs. I know how to grant
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not coming
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>
|||oooh, uncharted territory! - scary and exciting
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...[vbcol=seagreen]
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve

>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:

> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'
m
> getting EXECUTE permission errors when calling sprocs. I know how to gran
t
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that
I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not comin
g
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>|||oooh, uncharted territory! - scary and exciting
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...[vbcol=seagreen]
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve

>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>

New instance

Hello all,
I have (what I think is) a newbie question that so far
I have not been able to find the answer to as yet.
I have a SQL Server 2000 woth some databases running in
the default instance. I am in preparation of installing an
application that uses SQL Server 2000, but requires a
separate instance. The $64 question is, how do I create a
new instance? Including any other factors I might overlook
in creating a new instance of SQL Server 2000 to support
this other application.
Thanks!
GregThis is a multi-part message in MIME format.
--=_NextPart_000_0181_01C45AD0.170CD1B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Look for "How to install a named instance of SQL Server 2000 (Setup)" in =Books Online.
"Greg" <anonymous@.discussions.microsoft.com> wrote in message =news:21cb901c45ae6$7caa9af0$a001280a@.phx.gbl...
> Hello all,
> > I have (what I think is) a newbie question that so far > I have not been able to find the answer to as yet.
> > I have a SQL Server 2000 woth some databases running in > the default instance. I am in preparation of installing an > application that uses SQL Server 2000, but requires a > separate instance. The $64 question is, how do I create a > new instance? Including any other factors I might overlook > in creating a new instance of SQL Server 2000 to support > this other application.
> > Thanks!
> > Greg
--=_NextPart_000_0181_01C45AD0.170CD1B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Look for "How to install a named instance of SQL Server 2000 (Setup)" in Books Online.
"Greg" wrote in message news:21cb901c45ae6$7caa9af0$a001280a@.phx.gbl...> Hello =all,> > I have (what I think is) a newbie question that so far => I have not been able to find the answer to as yet.> > I have =a SQL Server 2000 woth some databases running in > the default =instance. I am in preparation of installing an > application that uses SQL =Server 2000, but requires a > separate instance. The $64 question is, how do I =create a > new instance? Including any other factors I might overlook => in creating a new instance of SQL Server 2000 to support > this =other application.> > Thanks!> > =Greg

---

--=_NextPart_000_0181_01C45AD0.170CD1B0--|||Hi,
how do I create a new instance?
Just insert the SQL Server CD and select Setup.exe or Autorun.exe. THis
automatically detects the default instance already installed and so
the setup program will ask for name for the instanc. The rest of the steps
will be same as default installation.
This new instance is totally independant of the default instance, all the
resources alocation (Memory / CPU,...) are seperate.
This installation requires seperate license.
So if possible create the new database in the default instance itself.
Thanks
Hari
MCDBA
"Greg" <anonymous@.discussions.microsoft.com> wrote in message
news:21cb901c45ae6$7caa9af0$a001280a@.phx.gbl...
> Hello all,
> I have (what I think is) a newbie question that so far
> I have not been able to find the answer to as yet.
> I have a SQL Server 2000 woth some databases running in
> the default instance. I am in preparation of installing an
> application that uses SQL Server 2000, but requires a
> separate instance. The $64 question is, how do I create a
> new instance? Including any other factors I might overlook
> in creating a new instance of SQL Server 2000 to support
> this other application.
> Thanks!
> Greg

New instance

Hello all,
I have (what I think is) a newbie question that so far
I have not been able to find the answer to as yet.
I have a SQL Server 2000 woth some databases running in
the default instance. I am in preparation of installing an
application that uses SQL Server 2000, but requires a
separate instance. The $64 question is, how do I create a
new instance? Including any other factors I might overlook
in creating a new instance of SQL Server 2000 to support
this other application.
Thanks!
Greg
Look for "How to install a named instance of SQL Server 2000 (Setup)" in Books Online.
"Greg" <anonymous@.discussions.microsoft.com> wrote in message news:21cb901c45ae6$7caa9af0$a001280a@.phx.gbl...
> Hello all,
> I have (what I think is) a newbie question that so far
> I have not been able to find the answer to as yet.
> I have a SQL Server 2000 woth some databases running in
> the default instance. I am in preparation of installing an
> application that uses SQL Server 2000, but requires a
> separate instance. The $64 question is, how do I create a
> new instance? Including any other factors I might overlook
> in creating a new instance of SQL Server 2000 to support
> this other application.
> Thanks!
> Greg
|||Hi,
how do I create a new instance?
Just insert the SQL Server CD and select Setup.exe or Autorun.exe. THis
automatically detects the default instance already installed and so
the setup program will ask for name for the instanc. The rest of the steps
will be same as default installation.
This new instance is totally independant of the default instance, all the
resources alocation (Memory / CPU,...) are seperate.
This installation requires seperate license.
So if possible create the new database in the default instance itself.
Thanks
Hari
MCDBA
"Greg" <anonymous@.discussions.microsoft.com> wrote in message
news:21cb901c45ae6$7caa9af0$a001280a@.phx.gbl...
> Hello all,
> I have (what I think is) a newbie question that so far
> I have not been able to find the answer to as yet.
> I have a SQL Server 2000 woth some databases running in
> the default instance. I am in preparation of installing an
> application that uses SQL Server 2000, but requires a
> separate instance. The $64 question is, how do I create a
> new instance? Including any other factors I might overlook
> in creating a new instance of SQL Server 2000 to support
> this other application.
> Thanks!
> Greg

New instance

Hello all,
I have (what I think is) a newbie question that so far
I have not been able to find the answer to as yet.
I have a SQL Server 2000 woth some databases running in
the default instance. I am in preparation of installing an
application that uses SQL Server 2000, but requires a
separate instance. The $64 question is, how do I create a
new instance? Including any other factors I might overlook
in creating a new instance of SQL Server 2000 to support
this other application.
Thanks!
GregLook for "How to install a named instance of SQL Server 2000 (Setup)" in Boo
ks Online.
"Greg" <anonymous@.discussions.microsoft.com> wrote in message news:21cb901c45ae6$7caa9af0$a0
01280a@.phx.gbl...
> Hello all,
>
> I have (what I think is) a newbie question that so far
> I have not been able to find the answer to as yet.
>
> I have a SQL Server 2000 woth some databases running in
> the default instance. I am in preparation of installing an
> application that uses SQL Server 2000, but requires a
> separate instance. The $64 question is, how do I create a
> new instance? Including any other factors I might overlook
> in creating a new instance of SQL Server 2000 to support
> this other application.
>
> Thanks!
>
> Greg|||Hi,
how do I create a new instance?
Just insert the SQL Server CD and select Setup.exe or Autorun.exe. THis
automatically detects the default instance already installed and so
the setup program will ask for name for the instanc. The rest of the steps
will be same as default installation.
This new instance is totally independant of the default instance, all the
resources alocation (Memory / CPU,...) are seperate.
This installation requires seperate license.
So if possible create the new database in the default instance itself.
Thanks
Hari
MCDBA
"Greg" <anonymous@.discussions.microsoft.com> wrote in message
news:21cb901c45ae6$7caa9af0$a001280a@.phx
.gbl...
> Hello all,
> I have (what I think is) a newbie question that so far
> I have not been able to find the answer to as yet.
> I have a SQL Server 2000 woth some databases running in
> the default instance. I am in preparation of installing an
> application that uses SQL Server 2000, but requires a
> separate instance. The $64 question is, how do I create a
> new instance? Including any other factors I might overlook
> in creating a new instance of SQL Server 2000 to support
> this other application.
> Thanks!
> Greg

New in MSDE, Please help!

Hi,

I am newbie in ASP.NET and MSDE arena. I understand that MSDE has no GUI and I need to have MSDE tools to work with it. I have already installed ASP.NET 1.1 and Microsoft.NET SDK 1.1 and MSDE in my Windown Professional 2000 PC and I have run and tested for .aspx and its working perfectly. But I want to use MSDE to create some database driven web applications.

Could you please help me how I can do that? BTW, I installed Microsoft SQL Web Data Administrator and its giving me SQLWebAdminStart.exe Application error and asking for debugging while opening the program. I am stranded what to do now?

I really appreciate your help.

regards,
Peter-Toronto
(Linux, PHP, MySQL)Hello Peter again,

I want to ask you which tools are you using to build your ASP.net application. If you'r using WebMAtrix project, then you can easly create your own database by going to Data Tab(located on the right section of the webmatrix page). Then go to "Aadd database connection". from there you can choose whether you want to create MSDE or Access databases. finally, you can go through the next steps to create your database. It is easy steps.

I hope it is clear now.

New Guy Question: Which came first ... the chicken or the checkpoint file?

Hello all...here's a question from a newbie ...

I'm attempting to configure my SSIS package to use a checkpoint file. I've checked the docs, and I believe I've set all the package properties for this ... except they are looking for the name of the checkpoint file. I've tried a couple of experiments such as c:\myCheckpoint.txt and c:\myCheckpoint.xml ... just for grins ... to see if SSIS would generate a checkpoint file for me at the start of the package ... no luck:

Message: Checkpoint file "C:\myCheckpoint.xml" failed to open due to error
0x80070002 "The system cannot find the file specified.".

From these runtime errors I've seen, it appears the checkpoint file should be an XML file that is created w/ specific nodes, etc. My question is ... how do I create the checkpoint file in advance so that when the package is executed it will find it and run?

SSIS ... pretty cool stuff!

Thanks!This is controlled by Package.CheckpointUsage property.
You probably have it set to 'Always' which causes package
to require the checkpoint file. You need to set it to 'IfExists' -
then the checkpoint file will be used if it exists.|||Yeah, that's what I figured too. The property options are Always, IfExists and Never. The doc doesn't specify that a file is created for you if you use Always, and on practical experimentation this didn't seem to help. Perhaps there's another property I missed; I did try to follow all the Package property settings that appeared to relate to checkpoints.

Thank you very much for trying!

DB|||The checkpoint is created automatically when the package fails (if it is configured to use checkpoints).

When you set CheckpointUsage=Always, you tell package that it has to start from previously saved checkpoint, i.e. the checkpoint file is expected to exist.

If you don't have checkpoint file yet, set CheckpointUsage=IfExists and run the package. It will run fine, and if it fails the package will create a checkpoint file. Next time when you run this package it will use that checkpoint.|||Thank you very, very much for your help! That makes sense!

Doug|||

Being another newbe, this post has been exceedingly helpful - I ran into the same issue!

Thanks! :-)

New Guy Question: Which came first ... the chicken or the checkpoint file?

Hello all...here's a question from a newbie ...

I'm attempting to configure my SSIS package to use a checkpoint file. I've checked the docs, and I believe I've set all the package properties for this ... except they are looking for the name of the checkpoint file. I've tried a couple of experiments such as c:\myCheckpoint.txt and c:\myCheckpoint.xml ... just for grins ... to see if SSIS would generate a checkpoint file for me at the start of the package ... no luck:

Message: Checkpoint file "C:\myCheckpoint.xml" failed to open due to error
0x80070002 "The system cannot find the file specified.".

From these runtime errors I've seen, it appears the checkpoint file should be an XML file that is created w/ specific nodes, etc. My question is ... how do I create the checkpoint file in advance so that when the package is executed it will find it and run?

SSIS ... pretty cool stuff!

Thanks!This is controlled by Package.CheckpointUsage property.
You probably have it set to 'Always' which causes package
to require the checkpoint file. You need to set it to 'IfExists' -
then the checkpoint file will be used if it exists.|||Yeah, that's what I figured too. The property options are Always, IfExists and Never. The doc doesn't specify that a file is created for you if you use Always, and on practical experimentation this didn't seem to help. Perhaps there's another property I missed; I did try to follow all the Package property settings that appeared to relate to checkpoints.

Thank you very much for trying!

DB|||The checkpoint is created automatically when the package fails (if it is configured to use checkpoints).

When you set CheckpointUsage=Always, you tell package that it has to start from previously saved checkpoint, i.e. the checkpoint file is expected to exist.

If you don't have checkpoint file yet, set CheckpointUsage=IfExists and run the package. It will run fine, and if it fails the package will create a checkpoint file. Next time when you run this package it will use that checkpoint.|||Thank you very, very much for your help! That makes sense!

Doug|||

Being another newbe, this post has been exceedingly helpful - I ran into the same issue!

Thanks! :-)

New Dimension

Hi!
I am a newbie, creating new Dimensions, Dimension structures, getting following error running a process; How would I fix this...
"the Dim_Salesperson was not found in the DW database on the server "

In Browser following sentence:
"Either the user, name, does not have access to the DW database or database does not exist."Sorry sorry... problem solved... :-)