Hello,
our customer tried to update his existing SQL Server 64 Bit Enterprise
Edition with reporting services to SP2. During Setup there was an error with
the reporting services. So the customer decided to uninstall the reporting
services and applied SP2 successfully after that.
Now he needs the reporting services for a new application. Can i install the
reporting services from the original media and then upgrade that reporting
services installation to sp2?What do i have to take care of?
My plan was to install reporting services via software. Change SQL Server
Installation and add reporting services.
I tried that but the setup then comes up with the warning that there is a
version change. I think that is because the sql server has another
patchlevel than the original installation media. Can i ignore that?
thanks in advance
thomasHi Thomas
Although I haven't tried what you are doing, there is not really any
alternative as there is no slipstreamed releases of SQL Server that will go
straight in as SP2, so I guess you have to ignore the error and continue. It
is probably better to install this by hand!
John
"Thomas Oeser" wrote:
> Hello,
> our customer tried to update his existing SQL Server 64 Bit Enterprise
> Edition with reporting services to SP2. During Setup there was an error with
> the reporting services. So the customer decided to uninstall the reporting
> services and applied SP2 successfully after that.
> Now he needs the reporting services for a new application. Can i install the
> reporting services from the original media and then upgrade that reporting
> services installation to sp2?What do i have to take care of?
> My plan was to install reporting services via software. Change SQL Server
> Installation and add reporting services.
> I tried that but the setup then comes up with the warning that there is a
> version change. I think that is because the sql server has another
> patchlevel than the original installation media. Can i ignore that?
> thanks in advance
> thomas
>
Showing posts with label bit. Show all posts
Showing posts with label bit. Show all posts
Friday, March 30, 2012
Install question
I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron
>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.
> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A
|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CAL
> licensing becomes irrelevant. You should not be running the MSDN version of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>
|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A
|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>
|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.
|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:
> I am not sure what you are using it for, if you require licensing, what your
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>
|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron
>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.
> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A
|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CAL
> licensing becomes irrelevant. You should not be running the MSDN version of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>
|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A
|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>
|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.
|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:
> I am not sure what you are using it for, if you require licensing, what your
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>
|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:
Install question
I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.
> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CA
L
> licensing becomes irrelevant. You should not be running the MSDN version
of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:
> I am not sure what you are using it for, if you require licensing, what yo
ur
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.
> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CA
L
> licensing becomes irrelevant. You should not be running the MSDN version
of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:
> I am not sure what you are using it for, if you require licensing, what yo
ur
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
Wednesday, March 21, 2012
Install enterprise manager on 64 bit server
Is it possible to install the enterprise manager and tools on the 64 bit
version of sql server, running on windows 2003 server?
Thanks,
JeffI'm pretty certain that there is code in there that doesn't run on 64 bit,
hence why MS removed the client tools from the install in the first place.
:-)=
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Scanner2001" <jeffsanders125@.hotmail.com> wrote in message
news:%23YS3LkS4DHA.1816@.TK2MSFTNGP12.phx.gbl...
version of sql server, running on windows 2003 server?
Thanks,
JeffI'm pretty certain that there is code in there that doesn't run on 64 bit,
hence why MS removed the client tools from the install in the first place.
:-)=
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Scanner2001" <jeffsanders125@.hotmail.com> wrote in message
news:%23YS3LkS4DHA.1816@.TK2MSFTNGP12.phx.gbl...
quote:
> Is it possible to install the enterprise manager and tools on the 64 bit
> version of sql server, running on windows 2003 server?
> Thanks,
> Jeff
>
Install enterprise manager on 64 bit server
Is it possible to install the enterprise manager and tools on the 64 bit
version of sql server, running on windows 2003 server?
Thanks,
JeffI'm pretty certain that there is code in there that doesn't run on 64 bit,
hence why MS removed the client tools from the install in the first place.
:-)=--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Scanner2001" <jeffsanders125@.hotmail.com> wrote in message
news:%23YS3LkS4DHA.1816@.TK2MSFTNGP12.phx.gbl...
> Is it possible to install the enterprise manager and tools on the 64 bit
> version of sql server, running on windows 2003 server?
> Thanks,
> Jeff
>sql
version of sql server, running on windows 2003 server?
Thanks,
JeffI'm pretty certain that there is code in there that doesn't run on 64 bit,
hence why MS removed the client tools from the install in the first place.
:-)=--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Scanner2001" <jeffsanders125@.hotmail.com> wrote in message
news:%23YS3LkS4DHA.1816@.TK2MSFTNGP12.phx.gbl...
> Is it possible to install the enterprise manager and tools on the 64 bit
> version of sql server, running on windows 2003 server?
> Thanks,
> Jeff
>sql
Monday, March 12, 2012
Install 32 bit SQL on 64 bit Windows ??
Can i install 32 bit SQL 2000 or 2005 on 64 bit Windows 2003 ?
If possible,anything to watch out for ?
Let me know
ThanksHi
Yes it can be although I don't have experience of this!
Why do you would want to do this?
John
"Hassan" wrote:
> Can i install 32 bit SQL 2000 or 2005 on 64 bit Windows 2003 ?
> If possible,anything to watch out for ?
> Let me know
> Thanks
>
>
If possible,anything to watch out for ?
Let me know
ThanksHi
Yes it can be although I don't have experience of this!
Why do you would want to do this?
John
"Hassan" wrote:
> Can i install 32 bit SQL 2000 or 2005 on 64 bit Windows 2003 ?
> If possible,anything to watch out for ?
> Let me know
> Thanks
>
>
Friday, February 24, 2012
Inserting to multiple tables in SQL Server 2005 that use identity specification
Hi, I am having a bit of hassle with trying to enter details to multiple tables in SQL Server 2005.
I have four tables, an
Attendance Table (AttendanceID(PK Identity specific), MembershipNo, Date)
Resistance Table (ResistId(PK Identity specific), Weight , Reps, Sets)
Aerobics Tables(AerobicsID(PK Identity specific), MachineID, Intensity, Time)
and a linking table for all of them... ExerciseMaster(AttendanceID,ResistanceID,AerobicsI D)
My problem is that I can insert data to each specific table by itself using seperate insert statements....eg...
//insert an attendance record to the attendance table
string userID;
userID = Session["User"].ToString();
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommand = "INSERT INTO [Attendance] ([MembershipNo], [Date]) VALUES (@.MembershipNo, @.Date)";
pgpDataSource.InsertParameters.Add("MembershipNo", userID);
pgpDataSource.InsertParameters.Add("Date", txtVisitDate.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}
//insert an aerobics record into the aerocibs table
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommand = "INSERT INTO [Aerobics] ([MachineID], [Intensity], [ExerciseTime]) VALUES (@.MachineID, @.Intensity, @.ExerciseTime)";
pgpDataSource.InsertParameters.Add("MachineID", rower.ToString());
pgpDataSource.InsertParameters.Add("Intensity", txtRowerLevel.Text);
pgpDataSource.InsertParameters.Add("ExerciseTime", txtRowerTime.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}
//same code as above for the resistance table
However, i am facing the problem where this does not populate the link table(ExerciseMaster) with any information as i am unable to write the relevant IDs into the table that have been auto generated by SQL Server for each of the subTables.
I have read several forums where they recommend using something called @.@.IDENTITY but i have no idea how or where to use this in order to fill my exercise table...
Any help would be so much appreciated... Also, hopefully what i have said all makes sense and someone will be able to help me...oh and one more thing...this is an ASP.NET page coding in C#
Cheers
ScottyI think the problem is in your design. I'm thinking you should dump the ExerciseMaster table.
If you have a one-to-one relationship between attendance, Resistance, and Aerobics, then a single table will do. If you have a one-to-many relationship (for a given attendance, there may be zero or more resistance sessions and zero or more aerobics sessions) then this schema should work for you:
1. Attendance Table (AttendanceID(PK Identity specific), MembershipNo, Date)
2. Resistance Table (ResistId(PK Identity specific), AttendanceID(FK), Weight , Reps, Sets)
3. Aerobics Table(AerobicsID(PK Identity specific), AttendanceID(FK), MachineID, Intensity, Time)
You can insert the attendance record and then either recover the ID created using @.@.Identity or switch to GUID identifiers and let your interface create the ID. Then use that ID when you insert the Resistance and Aerobics records.|||Thanks Blindman, I see where you are coming from about the tables and I agree with what you have suggested. However, i am still a bit lost as to what the actual code would be to use the @.@.IDENTITY...
eg.
Suppose i have changed my database design to reflect your suggestions and want to enter code to the Aerobics table, how do i use the attendanceID that is used in the attendance table and enter it into the attendanceID in the Aerobics table..I have no idea how or where to use the @.@.IDENTITY in my code...
//insert an attendance record to the attendance table
string userID;
userID = Session["User"].ToString();
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommand = "INSERT INTO [Attendance] ([MembershipNo], [Date]) VALUES (@.MembershipNo, @.Date)";
pgpDataSource.InsertParameters.Add("MembershipNo", userID);
pgpDataSource.InsertParameters.Add("Date", txtVisitDate.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}
//insert an aerobics record into the aerocibs table
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommand = "INSERT INTO [Aerobics] ([AttendanceID], [/COLOR][MachineID], [Intensity], [ExerciseTime]) VALUES (@.MachineID, @.Intensity, @.ExerciseTime)";
pgpDataSource.InsertParameters.Add("MachineID", rower.ToString());
pgpDataSource.InsertParameters.Add("Intensity", txtRowerLevel.Text);
pgpDataSource.InsertParameters.Add("ExerciseTime", txtRowerTime.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}|||Well, the other thing you need to do is to stop issuing dynamic SQL code from your application. It is more complicated, less efficient, and insecure.
Write a store procedure called "InsertAttendance" that takes MembershipNo and Date as parameters. The stored procedure will insert the new record (after checking to make sure it does not already exist), and then call @.@.Identity (better yet, use @.@.SCOPEIDENTITY...) to get the ID that was just created. The sproc can pass the new ID back as an output parameter.
Or, as I said, you can switch to using GUIDs rather than identity integers as your primary key. Then you can actually create the new GUID within your application code, and you never have to query the database to find out what ID was assigned.|||is there any chance you could provide some sample code as to how i would call the @.@.IDENTITY, where i would call it from and how i would use it to actually write the information to another table ? im a bit lost as im very new to all this...
Thanks|||set nocount on
--Create a dummy table
create table SampleTable (IdentityColumn int identity, DummyData varchar(50))
go
--Create a dummy sproc
create procedure InsertSample (@.DummyValue varchar(50), @.NewIdentity int output)
as
begin
insert into SampleTable (DummyData) values(@.DummyValue)
set @.NewIdentity = Scope_Identity()
end
go
--Run some insert statements and check the ID values retrieved
declare @.NewID int
exec InsertSample 'Fubar1', @.NewIdentity = @.NewID output
select @.NewID
exec InsertSample 'Fubar2', @.NewIdentity = @.NewID output
select @.NewID
exec InsertSample 'Fubar3', @.NewIdentity = @.NewID output
select @.NewID
--Cleanup
drop procedure InsertSample
drop table SampleTable
go|||Thanks for that, Have that working but only when i execute the stored procedure from the database. I am still unable to actually use it unfortunatley within the application...
string userID;
const int macId = 3;
userID = Session["User"].ToString();
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.SelectCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.StoredProcedure;
pgpDataSource.InsertCommand = "InsertAttendance";
pgpDataSource.InsertParameters.Add("MembershipNo", userID);
pgpDataSource.InsertParameters.Add("Date", txtVisitDate.Text);
//I think this may be the problem, both here and again below where
// i have the line of code commented out again...
//pgpDataSource.InsertParameters.Add("AttendanceID", newID.ToString());
pgpDataSource.InsertParameters.Add("MachineID", macId.ToString());
pgpDataSource.InsertParameters.Add("Intensity", txtRowerLevel.Text );
pgpDataSource.InsertParameters.Add("ExerciseTime", txtRowerTime.Text);
//pgpDataSource.InsertParameters.Add("AttendanceID", newID.ToString());
pgpDataSource.InsertParameters.Add("Reps", txtReps.Text);
pgpDataSource.InsertParameters.Add("Sets", txtSets.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}
if (RowsAffected != 1)
{
Response.Redirect("~/Problem.aspx");
}
else
{
Response.Redirect("~/Log.aspx");
}
}
This is the storedProcedure i created to fill all three tables which works but not when i try to use it in the application...
ALTER PROCEDURE InsertAttendance
@.NewIdentity int output,
@.MembershipNo smallint,
@.Date datetime,
@.Reps smallint,
@.Sets smallint,
@.Weight smallint,
@.MachineID smallint,
@.Intensity smallint,
@.ExerciseTime int
AS
BEGIN
INSERT Attendance (MembershipNo, Date)
Values (@.MembershipNo, @.Date)
INSERT Aerobics (AttendanceID, MachineID, Intensity, ExerciseTime)
Values (@.NewIdentity, @.MachineID, @.Intensity, @.ExerciseTime)
INSERT Resistance ( AttendanceID, Reps, Sets, Weight)
VALUES (@.NewIdentity, @.Reps, @.Sets, @.Weight)
Set @.NewIdentity = Scope_Identity()
END|||How you call this stored procedure from your application code depends upon your programming platform. I don't code interfaces, so I can't help you with that. But I'd have a hard time believing that any respectable programming language would not have a method of calling a stored procedure and retrieving an output parameter.
I suggest you ask about this on a forum specific to your development platform.|||Are you sure this works properly? I would have thought that you would have to set the value of @.NewIdentity before you used it in the Insert statements for the Aerobics and Resistance tables.
[/QUOTE]
INSERT Attendance (MembershipNo, Date)
Values (@.MembershipNo, @.Date)
INSERT Aerobics (AttendanceID, MachineID, Intensity, ExerciseTime)
Values (@.NewIdentity, @.MachineID, @.Intensity, @.ExerciseTime)
INSERT Resistance ( AttendanceID, Reps, Sets, Weight)
VALUES (@.NewIdentity, @.Reps, @.Sets, @.Weight)
Set @.NewIdentity = Scope_Identity()
END[/QUOTE]
I have four tables, an
Attendance Table (AttendanceID(PK Identity specific), MembershipNo, Date)
Resistance Table (ResistId(PK Identity specific), Weight , Reps, Sets)
Aerobics Tables(AerobicsID(PK Identity specific), MachineID, Intensity, Time)
and a linking table for all of them... ExerciseMaster(AttendanceID,ResistanceID,AerobicsI D)
My problem is that I can insert data to each specific table by itself using seperate insert statements....eg...
//insert an attendance record to the attendance table
string userID;
userID = Session["User"].ToString();
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommand = "INSERT INTO [Attendance] ([MembershipNo], [Date]) VALUES (@.MembershipNo, @.Date)";
pgpDataSource.InsertParameters.Add("MembershipNo", userID);
pgpDataSource.InsertParameters.Add("Date", txtVisitDate.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}
//insert an aerobics record into the aerocibs table
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommand = "INSERT INTO [Aerobics] ([MachineID], [Intensity], [ExerciseTime]) VALUES (@.MachineID, @.Intensity, @.ExerciseTime)";
pgpDataSource.InsertParameters.Add("MachineID", rower.ToString());
pgpDataSource.InsertParameters.Add("Intensity", txtRowerLevel.Text);
pgpDataSource.InsertParameters.Add("ExerciseTime", txtRowerTime.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}
//same code as above for the resistance table
However, i am facing the problem where this does not populate the link table(ExerciseMaster) with any information as i am unable to write the relevant IDs into the table that have been auto generated by SQL Server for each of the subTables.
I have read several forums where they recommend using something called @.@.IDENTITY but i have no idea how or where to use this in order to fill my exercise table...
Any help would be so much appreciated... Also, hopefully what i have said all makes sense and someone will be able to help me...oh and one more thing...this is an ASP.NET page coding in C#
Cheers
ScottyI think the problem is in your design. I'm thinking you should dump the ExerciseMaster table.
If you have a one-to-one relationship between attendance, Resistance, and Aerobics, then a single table will do. If you have a one-to-many relationship (for a given attendance, there may be zero or more resistance sessions and zero or more aerobics sessions) then this schema should work for you:
1. Attendance Table (AttendanceID(PK Identity specific), MembershipNo, Date)
2. Resistance Table (ResistId(PK Identity specific), AttendanceID(FK), Weight , Reps, Sets)
3. Aerobics Table(AerobicsID(PK Identity specific), AttendanceID(FK), MachineID, Intensity, Time)
You can insert the attendance record and then either recover the ID created using @.@.Identity or switch to GUID identifiers and let your interface create the ID. Then use that ID when you insert the Resistance and Aerobics records.|||Thanks Blindman, I see where you are coming from about the tables and I agree with what you have suggested. However, i am still a bit lost as to what the actual code would be to use the @.@.IDENTITY...
eg.
Suppose i have changed my database design to reflect your suggestions and want to enter code to the Aerobics table, how do i use the attendanceID that is used in the attendance table and enter it into the attendanceID in the Aerobics table..I have no idea how or where to use the @.@.IDENTITY in my code...
//insert an attendance record to the attendance table
string userID;
userID = Session["User"].ToString();
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommand = "INSERT INTO [Attendance] ([MembershipNo], [Date]) VALUES (@.MembershipNo, @.Date)";
pgpDataSource.InsertParameters.Add("MembershipNo", userID);
pgpDataSource.InsertParameters.Add("Date", txtVisitDate.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}
//insert an aerobics record into the aerocibs table
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommand = "INSERT INTO [Aerobics] ([AttendanceID], [/COLOR][MachineID], [Intensity], [ExerciseTime]) VALUES (@.MachineID, @.Intensity, @.ExerciseTime)";
pgpDataSource.InsertParameters.Add("MachineID", rower.ToString());
pgpDataSource.InsertParameters.Add("Intensity", txtRowerLevel.Text);
pgpDataSource.InsertParameters.Add("ExerciseTime", txtRowerTime.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}|||Well, the other thing you need to do is to stop issuing dynamic SQL code from your application. It is more complicated, less efficient, and insecure.
Write a store procedure called "InsertAttendance" that takes MembershipNo and Date as parameters. The stored procedure will insert the new record (after checking to make sure it does not already exist), and then call @.@.Identity (better yet, use @.@.SCOPEIDENTITY...) to get the ID that was just created. The sproc can pass the new ID back as an output parameter.
Or, as I said, you can switch to using GUIDs rather than identity integers as your primary key. Then you can actually create the new GUID within your application code, and you never have to query the database to find out what ID was assigned.|||is there any chance you could provide some sample code as to how i would call the @.@.IDENTITY, where i would call it from and how i would use it to actually write the information to another table ? im a bit lost as im very new to all this...
Thanks|||set nocount on
--Create a dummy table
create table SampleTable (IdentityColumn int identity, DummyData varchar(50))
go
--Create a dummy sproc
create procedure InsertSample (@.DummyValue varchar(50), @.NewIdentity int output)
as
begin
insert into SampleTable (DummyData) values(@.DummyValue)
set @.NewIdentity = Scope_Identity()
end
go
--Run some insert statements and check the ID values retrieved
declare @.NewID int
exec InsertSample 'Fubar1', @.NewIdentity = @.NewID output
select @.NewID
exec InsertSample 'Fubar2', @.NewIdentity = @.NewID output
select @.NewID
exec InsertSample 'Fubar3', @.NewIdentity = @.NewID output
select @.NewID
--Cleanup
drop procedure InsertSample
drop table SampleTable
go|||Thanks for that, Have that working but only when i execute the stored procedure from the database. I am still unable to actually use it unfortunatley within the application...
string userID;
const int macId = 3;
userID = Session["User"].ToString();
SqlDataSource pgpDataSource = new SqlDataSource();
pgpDataSource.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStringLogin"].ToString();
pgpDataSource.SelectCommandType = SqlDataSourceCommandType.Text;
pgpDataSource.InsertCommandType = SqlDataSourceCommandType.StoredProcedure;
pgpDataSource.InsertCommand = "InsertAttendance";
pgpDataSource.InsertParameters.Add("MembershipNo", userID);
pgpDataSource.InsertParameters.Add("Date", txtVisitDate.Text);
//I think this may be the problem, both here and again below where
// i have the line of code commented out again...
//pgpDataSource.InsertParameters.Add("AttendanceID", newID.ToString());
pgpDataSource.InsertParameters.Add("MachineID", macId.ToString());
pgpDataSource.InsertParameters.Add("Intensity", txtRowerLevel.Text );
pgpDataSource.InsertParameters.Add("ExerciseTime", txtRowerTime.Text);
//pgpDataSource.InsertParameters.Add("AttendanceID", newID.ToString());
pgpDataSource.InsertParameters.Add("Reps", txtReps.Text);
pgpDataSource.InsertParameters.Add("Sets", txtSets.Text);
int RowsAffected = 0;
try
{
RowsAffected = pgpDataSource.Insert();
}
catch (Exception ex)
{
Server.Transfer("~/Problem.aspx");
}
finally
{
pgpDataSource = null;
}
if (RowsAffected != 1)
{
Response.Redirect("~/Problem.aspx");
}
else
{
Response.Redirect("~/Log.aspx");
}
}
This is the storedProcedure i created to fill all three tables which works but not when i try to use it in the application...
ALTER PROCEDURE InsertAttendance
@.NewIdentity int output,
@.MembershipNo smallint,
@.Date datetime,
@.Reps smallint,
@.Sets smallint,
@.Weight smallint,
@.MachineID smallint,
@.Intensity smallint,
@.ExerciseTime int
AS
BEGIN
INSERT Attendance (MembershipNo, Date)
Values (@.MembershipNo, @.Date)
INSERT Aerobics (AttendanceID, MachineID, Intensity, ExerciseTime)
Values (@.NewIdentity, @.MachineID, @.Intensity, @.ExerciseTime)
INSERT Resistance ( AttendanceID, Reps, Sets, Weight)
VALUES (@.NewIdentity, @.Reps, @.Sets, @.Weight)
Set @.NewIdentity = Scope_Identity()
END|||How you call this stored procedure from your application code depends upon your programming platform. I don't code interfaces, so I can't help you with that. But I'd have a hard time believing that any respectable programming language would not have a method of calling a stored procedure and retrieving an output parameter.
I suggest you ask about this on a forum specific to your development platform.|||Are you sure this works properly? I would have thought that you would have to set the value of @.NewIdentity before you used it in the Insert statements for the Aerobics and Resistance tables.
[/QUOTE]
INSERT Attendance (MembershipNo, Date)
Values (@.MembershipNo, @.Date)
INSERT Aerobics (AttendanceID, MachineID, Intensity, ExerciseTime)
Values (@.NewIdentity, @.MachineID, @.Intensity, @.ExerciseTime)
INSERT Resistance ( AttendanceID, Reps, Sets, Weight)
VALUES (@.NewIdentity, @.Reps, @.Sets, @.Weight)
Set @.NewIdentity = Scope_Identity()
END[/QUOTE]
Subscribe to:
Posts (Atom)