Do I need CAL for a customized program connect to SQL Server 2005 Express Edition?

Hi all,

I am developing a program to connect to SQL 2005 Express. I don't know if I need any CAL license in order to make the connection. If it is not necessary for the Express Edition case, how about if my client upgrate to SQL 2005 in the future? Do I need CAL license for SQL 2005?

Thanks for any advice given.

You do not need a CAL to connect to SQL Server Express. Each cient does need a CAL for all other editions.

Buck Woody

Do I need CAL for a customized program connect to SQL Server 2005 Express Edition?

Hi all,

I am developing a program to connect to SQL 2005 Express. I don't know if I need any CAL license in order to make the connection. If it is not necessary for the Express Edition case, how about if my client upgrate to SQL 2005 in the future? Do I need CAL license for SQL 2005?

Thanks for any advice given.

You do not need a CAL to connect to SQL Server Express. Each cient does need a CAL for all other editions.

Buck Woody

DNS problem with reports (server URL)

I'm developing a SSRS site using SQL Server 2000 and Visual Studio 2003.
The target device is a Nokia 770 Internet tablet over a wireless network
using VPN for authentication (corporate requirement).
The 770 currently has a problem resolving server names to a fully-qualified
URL. It's been identified as a DNS-oriented bug that may take time to be
fixed. In order to enable the 770 tablet to navigate to my site, instead of
using http://myserver/Reports I have to instruct users to enter
http://myserver.country.company.com/Reports. This in and of itself is not a
problem. The trouble starts when the user clicks a report or chart; the url
generated contains a reference to http://myserver/Reportserver.
Unfortunately the tablet can't resolve this.
What I am looking for is a way to override whatever setting is limiting the
Reportserver URL and replace it with a fully qualified URL.
Anyone have any ideas? I've looked into it some but haven't figured out
what I can do.
Thanks,
Randall Arnold
NokiaRandall,
If you're able, I think the simplest solution would be to create a little
one page aspx program in which you can display your reports. Then you can
pass the full domain name to the reports server as part of the program.
Tim
Pharos Innovations
"Randall Arnold" wrote:
> I'm developing a SSRS site using SQL Server 2000 and Visual Studio 2003.
> The target device is a Nokia 770 Internet tablet over a wireless network
> using VPN for authentication (corporate requirement).
> The 770 currently has a problem resolving server names to a fully-qualified
> URL. It's been identified as a DNS-oriented bug that may take time to be
> fixed. In order to enable the 770 tablet to navigate to my site, instead of
> using http://myserver/Reports I have to instruct users to enter
> http://myserver.country.company.com/Reports. This in and of itself is not a
> problem. The trouble starts when the user clicks a report or chart; the url
> generated contains a reference to http://myserver/Reportserver.
> Unfortunately the tablet can't resolve this.
> What I am looking for is a way to override whatever setting is limiting the
> Reportserver URL and replace it with a fully qualified URL.
> Anyone have any ideas? I've looked into it some but haven't figured out
> what I can do.
> Thanks,
> Randall Arnold
> Nokia
>
>sql

Distribution of SQLServer Database

Hi,
We're in the process of developing a .NET application which will use a
SQLServer database. When installed/deployed the application will query this
database. I assume each time the application is installed the SQL Server
database will need to be installed. Is this the case - sorry I know it's a
dumb question but I am a complete SQL Server novice. If this is the case then
which licensing option should we go for?
Any help would be greatly appreciated.
-Kim
Hi Kim
There is a version of SQL Server which is designed to be deployed with user
programs. It's called MSDE & you can read more about it here:
http://msdn.microsoft.com/library/de...ar_ts_67ax.asp
There are limits on it's growth (2Gb per db, max 2 CPUs etc) & if you exceed
these, you'd probably be looking at SQL Server Standard Edition.
Regards,
Greg Linwood
SQL Server MVP
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> Hi,
> We're in the process of developing a .NET application which will use a
> SQLServer database. When installed/deployed the application will query
> this
> database. I assume each time the application is installed the SQL Server
> database will need to be installed. Is this the case - sorry I know it's a
> dumb question but I am a complete SQL Server novice. If this is the case
> then
> which licensing option should we go for?
> Any help would be greatly appreciated.
> -Kim
|||It also depends on what you mean about deplying SQL... YOu might wish all of
the clients to share data from a single database, or you might wish to
install the MSDE version on each client, so there is no data sharing...
In either case, at least you will have to the the SQL Connectivity piece on
the client.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> Hi,
> We're in the process of developing a .NET application which will use a
> SQLServer database. When installed/deployed the application will query
this
> database. I assume each time the application is installed the SQL Server
> database will need to be installed. Is this the case - sorry I know it's a
> dumb question but I am a complete SQL Server novice. If this is the case
then
> which licensing option should we go for?
> Any help would be greatly appreciated.
> -Kim
|||Ideally clients would share data from a single database but there would be
the capability to work 'off-line' - in other words users could access the
database even while not explicitly connected to the server. I presume in this
case it would require a separate MSDE installation on each client as well as
on the server database. Does MSDE support this type of behaviour?
"Wayne Snyder" wrote:

> It also depends on what you mean about deplying SQL... YOu might wish all of
> the clients to share data from a single database, or you might wish to
> install the MSDE version on each client, so there is no data sharing...
> In either case, at least you will have to the the SQL Connectivity piece on
> the client.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> this
> then
>
>
|||Great, so does this mean that we would only need to purchase a SQLServer
developers license?
"Greg Linwood" wrote:

> Hi Kim
> There is a version of SQL Server which is designed to be deployed with user
> programs. It's called MSDE & you can read more about it here:
> http://msdn.microsoft.com/library/de...ar_ts_67ax.asp
> There are limits on it's growth (2Gb per db, max 2 CPUs etc) & if you exceed
> these, you'd probably be looking at SQL Server Standard Edition.
> Regards,
> Greg Linwood
> SQL Server MVP
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
>
>
|||In this case, you'd be looking at Personal Edition, which is on the SS
media. Then you replicate the Central Database to your clients, which can
then go "offline."
That's what this edition was created for. It has restrictions, but
different than those of MSDE, which is more an Access database replacement.
SS Personal Edition is more for business, semi-connected users, like sales
staff.
Sincerely,
Anthony Thomas

"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:7E0720DF-6224-4B91-A92E-5D4C542D7FC3@.microsoft.com...
Ideally clients would share data from a single database but there would be
the capability to work 'off-line' - in other words users could access the
database even while not explicitly connected to the server. I presume in
this
case it would require a separate MSDE installation on each client as well as
on the server database. Does MSDE support this type of behaviour?
"Wayne Snyder" wrote:

> It also depends on what you mean about deplying SQL... YOu might wish all
of
> the clients to share data from a single database, or you might wish to
> install the MSDE version on each client, so there is no data sharing...
> In either case, at least you will have to the the SQL Connectivity piece
on[vbcol=seagreen]
> the client.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> this
a
> then
>
>

Distribution of SQLServer Database

Hi,
We're in the process of developing a .NET application which will use a
SQLServer database. When installed/deployed the application will query this
database. I assume each time the application is installed the SQL Server
database will need to be installed. Is this the case - sorry I know it's a
dumb question but I am a complete SQL Server novice. If this is the case then
which licensing option should we go for?
Any help would be greatly appreciated.
-KimHi Kim
There is a version of SQL Server which is designed to be deployed with user
programs. It's called MSDE & you can read more about it here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_67ax.asp
There are limits on it's growth (2Gb per db, max 2 CPUs etc) & if you exceed
these, you'd probably be looking at SQL Server Standard Edition.
Regards,
Greg Linwood
SQL Server MVP
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> Hi,
> We're in the process of developing a .NET application which will use a
> SQLServer database. When installed/deployed the application will query
> this
> database. I assume each time the application is installed the SQL Server
> database will need to be installed. Is this the case - sorry I know it's a
> dumb question but I am a complete SQL Server novice. If this is the case
> then
> which licensing option should we go for?
> Any help would be greatly appreciated.
> -Kim|||It also depends on what you mean about deplying SQL... YOu might wish all of
the clients to share data from a single database, or you might wish to
install the MSDE version on each client, so there is no data sharing...
In either case, at least you will have to the the SQL Connectivity piece on
the client.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> Hi,
> We're in the process of developing a .NET application which will use a
> SQLServer database. When installed/deployed the application will query
this
> database. I assume each time the application is installed the SQL Server
> database will need to be installed. Is this the case - sorry I know it's a
> dumb question but I am a complete SQL Server novice. If this is the case
then
> which licensing option should we go for?
> Any help would be greatly appreciated.
> -Kim|||Ideally clients would share data from a single database but there would be
the capability to work 'off-line' - in other words users could access the
database even while not explicitly connected to the server. I presume in this
case it would require a separate MSDE installation on each client as well as
on the server database. Does MSDE support this type of behaviour?
"Wayne Snyder" wrote:
> It also depends on what you mean about deplying SQL... YOu might wish all of
> the clients to share data from a single database, or you might wish to
> install the MSDE version on each client, so there is no data sharing...
> In either case, at least you will have to the the SQL Connectivity piece on
> the client.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> > Hi,
> > We're in the process of developing a .NET application which will use a
> > SQLServer database. When installed/deployed the application will query
> this
> > database. I assume each time the application is installed the SQL Server
> > database will need to be installed. Is this the case - sorry I know it's a
> > dumb question but I am a complete SQL Server novice. If this is the case
> then
> > which licensing option should we go for?
> > Any help would be greatly appreciated.
> > -Kim
>
>|||Great, so does this mean that we would only need to purchase a SQLServer
developers license?
"Greg Linwood" wrote:
> Hi Kim
> There is a version of SQL Server which is designed to be deployed with user
> programs. It's called MSDE & you can read more about it here:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_67ax.asp
> There are limits on it's growth (2Gb per db, max 2 CPUs etc) & if you exceed
> these, you'd probably be looking at SQL Server Standard Edition.
> Regards,
> Greg Linwood
> SQL Server MVP
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> > Hi,
> > We're in the process of developing a .NET application which will use a
> > SQLServer database. When installed/deployed the application will query
> > this
> > database. I assume each time the application is installed the SQL Server
> > database will need to be installed. Is this the case - sorry I know it's a
> > dumb question but I am a complete SQL Server novice. If this is the case
> > then
> > which licensing option should we go for?
> > Any help would be greatly appreciated.
> > -Kim
>
>|||In this case, you'd be looking at Personal Edition, which is on the SS
media. Then you replicate the Central Database to your clients, which can
then go "offline."
That's what this edition was created for. It has restrictions, but
different than those of MSDE, which is more an Access database replacement.
SS Personal Edition is more for business, semi-connected users, like sales
staff.
Sincerely,
Anthony Thomas
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:7E0720DF-6224-4B91-A92E-5D4C542D7FC3@.microsoft.com...
Ideally clients would share data from a single database but there would be
the capability to work 'off-line' - in other words users could access the
database even while not explicitly connected to the server. I presume in
this
case it would require a separate MSDE installation on each client as well as
on the server database. Does MSDE support this type of behaviour?
"Wayne Snyder" wrote:
> It also depends on what you mean about deplying SQL... YOu might wish all
of
> the clients to share data from a single database, or you might wish to
> install the MSDE version on each client, so there is no data sharing...
> In either case, at least you will have to the the SQL Connectivity piece
on
> the client.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> > Hi,
> > We're in the process of developing a .NET application which will use a
> > SQLServer database. When installed/deployed the application will query
> this
> > database. I assume each time the application is installed the SQL Server
> > database will need to be installed. Is this the case - sorry I know it's
a
> > dumb question but I am a complete SQL Server novice. If this is the case
> then
> > which licensing option should we go for?
> > Any help would be greatly appreciated.
> > -Kim
>
>

distribution agent

I'm developing a setup package for an application that involves some
replications.
I create the new replication database, transactional publication, merge
pulication and a pull named subscription on the rtansactional
publication.
For checking that the snapshots have been generated successfully I do
the following:
get the job_name from the mssnapshot_agents table on distribution
database.
update job_state to run agent.
This worked well on both snapshots (trans, merge)
The problem is that I try to do the same steps for running the
distribution agent to initialize the subscription:
get the job_name from msdistribution_agents table on distribution
database.
BUT the job name is always "dose not exist"
I use sp_update_job to update the current step to start
and sp_start_job to start the job.
Is there a problem with those SPs or another way to do the same with
other SPs.
Thanks.
Have you looked at the replication ActiveX controls?
I think this is probably the simplest way to carry out what you are trying
to accomplish.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"taghreed" <tssamak@.gmail.com> wrote in message
news:1103290693.352210.19720@.z14g2000cwz.googlegro ups.com...
> I'm developing a setup package for an application that involves some
> replications.
> I create the new replication database, transactional publication, merge
> pulication and a pull named subscription on the rtansactional
> publication.
> For checking that the snapshots have been generated successfully I do
> the following:
> get the job_name from the mssnapshot_agents table on distribution
> database.
> update job_state to run agent.
> This worked well on both snapshots (trans, merge)
> The problem is that I try to do the same steps for running the
> distribution agent to initialize the subscription:
> get the job_name from msdistribution_agents table on distribution
> database.
> BUT the job name is always "dose not exist"
> I use sp_update_job to update the current step to start
> and sp_start_job to start the job.
> Is there a problem with those SPs or another way to do the same with
> other SPs.
> Thanks.
>
|||Thanks Hilary,
but I don't have time to reconstruct the application using ActiveX
controls.
Do you have other ideas?