Hi,
At the SQL Server cluster installation time I haven't choose the replication component(wasn't required at that time). Now it is and when I run again the setup to modify the installation and to add the replication components it doesn't give me that option.
The only option that I have is to uninstall the SQL Server.
Is it what is suppose to be? If yes how can I install the replication components?
Cata,
replication isn't enabled from the setup. If you use EM, and go to tools,
replication, configure publishing... you can set it up there.
Regards,
Paul Ibison
|||Thanks for your replay.
At the setup time when you install the SQL Server one is
asked if he wants to install the Replication components -
so there are some components that have to be installed. I
haven't choose that option.
Additionally when I am choosing to configure replication
EM - Tools - Cofigure Publishing, I get the message "The
Replication components were not included when SQL Server
was installed on <server>"
>--Original Message--
>Cata,
>replication isn't enabled from the setup. If you use EM,
and go to tools,
>replication, configure publishing... you can set it up
there.
>Regards,
>Paul Ibison
>
>.
>
|||My apologies - I had selected this checkbox without thinking when I installed, which was a while ago. I'm out of the office for a while but if no-one else answers in the next few days then I'll try on a test cluster I have built back at work. I suspect yo
u'll have to break the cluster then add the components, but I'll have a look.
Regards,
Paul Ibison
Showing posts with label time. Show all posts
Showing posts with label time. 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 28, 2012
Install Problem Error 29503 & 1067 OR Error 29503 & 2146885628
I'm new with development and just wanted to get the Personal Website Sample to work. So far, I'm have am having a terrible time installing SQL Express Edition. I'm not exactly sure what to do next. I have installed, manually uninstalled, and reinstalled many times. Sometimes I get error 29503 & 1067. Other times when I reinstall I get 29503 & -2146885628 . Here's the info I got so far for my 29503&1067 since that error occurs 95% of time. I believe I got the -2146885628 error when I changed a setting from network to local services.
I feel so confused right now. Any help would be appreciative.
From the Summary Log:
Code Snippet
Machine : DELL1Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--
Machine : DELL1
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0018_DELL1_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
Error Number : 29503
--
From there, I searched the error logs to find this in the SQL.log
Code Snippet
- Context --
Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Error Code: 1067
MSI (s) (84!D4) [01:48:10:750]: Product: Microsoft SQL Server 2005 -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
.
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Tue Aug 28 01:48:10 2007
Service MSSQL$SQLEXPRESS with parameters '-m SqlSetup -Q -qJapanese_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Tue Aug 28 01:48:10 2007
Service failed unexpectedly (1067)
Error Code: 0x8007042b (1067)
Windows Error Text: The process terminated unexpectedly.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Wed Jun 14 16:29:04 2006
Function Name: sqls::Service::Start
Source Line Number: 301
- Context --
Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Error Code: 1067
MSI (s) (84!D4) [01:48:13:968]: Product: Microsoft SQL Server 2005 -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
.
MSI (s) (84:10) [01:48:14:109]: User policy value 'DisableRollback' is 0
MSI (s) (84:10) [01:48:14:109]: Machine policy value 'DisableRollback' is 0
Action ended 1:48:14: InstallFinalize. Return value 3.
MSI (s) (84:10) [01:48:14:171]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=924585293,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (84:10) [01:48:14:171]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (84:10) [01:48:14:171]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005)
MSI (s) (84:10) [01:48:14:171]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: ActionStart(Name=Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Starting SQL Service: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: ProductInfo(ProductKey={B0F9497C-52B4-4686-8E73-74D866BBDF59},ProductName=Microsoft SQL Server 2005,PackageName=sqlrun_sql.msi,Language=1033,Version=151129058,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=\Setup\,PackageCode={08AD0897-0300-4F7D-A3CC-A0CCEDD42E0D},,,InstanceType=1,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (84:10) [01:48:14:171]: Executing op: ActionStart(Name=Rollback_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Stopping SQL Service: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: CustomActionRollback(Action=Rollback_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_sqlScript,CustomActionData=100Configuring Microsoft SQL Server81062400lpc:DELL1\SQLEXPRESS)
MSI (s) (84:B4) [01:48:14:171]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI571.tmp, Entrypoint: Rollback_sqlScript
Function=Rollback_sqlScript
Doing Action: Rollback_sqlScript
This log does get kind of big, so if you need more information, please feel free to ask
The first link is a cleaned up version of the Personal Starter Kit and the second link is where he can answer your questions. The third link is tutorials for many starter kits. Hope this helps.
http://www.jeremywadsworth.com/
http://forums.asp.net/1003.aspx
http://msdn2.microsoft.com/en-us/library/aa530759.aspx
|||Will I ever need to install SQL EE (right now I'm SQL less)? This error looks really big and I'm not sure exactly how to solve it.|||
EDIT
I don't see how you plan to run an application that needs SQL Server database without running Express. Express Advanced that is almost like the full edition is free. If you plan to develop you can download the Advanced below.
http://msdn2.microsoft.com/en-us/express/bb410792.aspx
|||Still waiting around for an answer to my install errors. I did install mySQL in about 15mins vs 3 full days and counting for SQL Server EE. It's pretty nice...but besides that, still wondering if anyone knows about these SQL EE Errors?|||
You cannot install MySQL and expect to run software created to use SQL Server Here is the thing I have installed the kit without problem a whileback and you are having problem so read those tutorials in my recent post the two for this kit and post in the forum I gave to you.
|||I am very very confused now.I can't install SQL Server Express Edition because I get errors 29503 & -2146885628 during the install process. Thus, SQL Server Express is not installed in my computer.
The links you gave me are troubleshooting tips for the Personal WebKit. Since you gave it too me, I thought I could run it without SQL Server Express Edition but your reply to that makes it sound like I need SQL Server Express Edition which I cannot install due to the errors above. I already install, manually uninstall, etc etc etc. As far as I can tell, during my install process, SQL Server Express Edition just installs maybe 80% of what it should be installing because my summary log says this:
I am assumming because my summary log says "Failed" in the install section, that SQL Server failed to install. I may be wrong and this may be a bug in the summary log.
I am very very confused now. Do I or do I not need to install SQL Server Express Edition first?
|||SQL Server 2005 is the easiest SQL Server to install I have installed 7.0, 2000 and now 2005 on all exist operating systems except Vista, that means server included. Now if you are running XP it comes with System Restore roll your Operating System back by one month if you have restore point that far back. You cannot install this starter kit without SQL Server because I have not seen MySQL versions of it. The link I gave you is where errors for this kit are resolved and you are right your current problem is SQL Server installation so now go roll back the Operating System and try the install again. Now go do some work and post again.|||
I did a search and found a number of possible causes of this error, but the log segment you provided does not provide enough information to really tell what the issue is. For starters, check out the KB article at http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B920114 and see if this applies to your situation.
If that doesn't work, search the log for "ue 3" to find any lines that contain 'Return Value 3' indicating a failure. The several lines above the return value should give you a more specific message about what actually failed to cause the error you're seeing. If that information doesn't point you in an obvious direction, post that snippet to the forum and we can take a look at it.
Mike
sqlInstall Problem Error 29503 & 1067 OR Error 29503 & 2146885628
I'm new with development and just wanted to get the Personal Website Sample to work. So far, I'm have am having a terrible time installing SQL Express Edition. I'm not exactly sure what to do next. I have installed, manually uninstalled, and reinstalled many times. Sometimes I get error 29503 & 1067. Other times when I reinstall I get 29503 & -2146885628 . Here's the info I got so far for my 29503&1067 since that error occurs 95% of time. I believe I got the -2146885628 error when I changed a setting from network to local services.
I feel so confused right now. Any help would be appreciative.
From the Summary Log:
Code Snippet
Machine : DELL1Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--
Machine : DELL1
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0018_DELL1_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
Error Number : 29503
--
From there, I searched the error logs to find this in the SQL.log
Code Snippet
- Context --
Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Error Code: 1067
MSI (s) (84!D4) [01:48:10:750]: Product: Microsoft SQL Server 2005 -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
.
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Tue Aug 28 01:48:10 2007
Service MSSQL$SQLEXPRESS with parameters '-m SqlSetup -Q -qJapanese_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Tue Aug 28 01:48:10 2007
Service failed unexpectedly (1067)
Error Code: 0x8007042b (1067)
Windows Error Text: The process terminated unexpectedly.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Wed Jun 14 16:29:04 2006
Function Name: sqls::Service::Start
Source Line Number: 301
- Context --
Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Error Code: 1067
MSI (s) (84!D4) [01:48:13:968]: Product: Microsoft SQL Server 2005 -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
.
MSI (s) (84:10) [01:48:14:109]: User policy value 'DisableRollback' is 0
MSI (s) (84:10) [01:48:14:109]: Machine policy value 'DisableRollback' is 0
Action ended 1:48:14: InstallFinalize. Return value 3.
MSI (s) (84:10) [01:48:14:171]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=924585293,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (84:10) [01:48:14:171]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (84:10) [01:48:14:171]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005)
MSI (s) (84:10) [01:48:14:171]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: ActionStart(Name=Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Starting SQL Service: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: ProductInfo(ProductKey={B0F9497C-52B4-4686-8E73-74D866BBDF59},ProductName=Microsoft SQL Server 2005,PackageName=sqlrun_sql.msi,Language=1033,Version=151129058,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=\Setup\,PackageCode={08AD0897-0300-4F7D-A3CC-A0CCEDD42E0D},,,InstanceType=1,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (84:10) [01:48:14:171]: Executing op: ActionStart(Name=Rollback_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Stopping SQL Service: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: CustomActionRollback(Action=Rollback_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_sqlScript,CustomActionData=100Configuring Microsoft SQL Server81062400lpc:DELL1\SQLEXPRESS)
MSI (s) (84:B4) [01:48:14:171]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI571.tmp, Entrypoint: Rollback_sqlScript
Function=Rollback_sqlScript
Doing Action: Rollback_sqlScript
This log does get kind of big, so if you need more information, please feel free to ask
The first link is a cleaned up version of the Personal Starter Kit and the second link is where he can answer your questions. The third link is tutorials for many starter kits. Hope this helps.
http://www.jeremywadsworth.com/
http://forums.asp.net/1003.aspx
http://msdn2.microsoft.com/en-us/library/aa530759.aspx
|||Will I ever need to install SQL EE (right now I'm SQL less)? This error looks really big and I'm not sure exactly how to solve it.|||
EDIT
I don't see how you plan to run an application that needs SQL Server database without running Express. Express Advanced that is almost like the full edition is free. If you plan to develop you can download the Advanced below.
http://msdn2.microsoft.com/en-us/express/bb410792.aspx
|||Still waiting around for an answer to my install errors. I did install mySQL in about 15mins vs 3 full days and counting for SQL Server EE. It's pretty nice...but besides that, still wondering if anyone knows about these SQL EE Errors?|||
You cannot install MySQL and expect to run software created to use SQL Server Here is the thing I have installed the kit without problem a whileback and you are having problem so read those tutorials in my recent post the two for this kit and post in the forum I gave to you.
|||I am very very confused now.I can't install SQL Server Express Edition because I get errors 29503 & -2146885628 during the install process. Thus, SQL Server Express is not installed in my computer.
The links you gave me are troubleshooting tips for the Personal WebKit. Since you gave it too me, I thought I could run it without SQL Server Express Edition but your reply to that makes it sound like I need SQL Server Express Edition which I cannot install due to the errors above. I already install, manually uninstall, etc etc etc. As far as I can tell, during my install process, SQL Server Express Edition just installs maybe 80% of what it should be installing because my summary log says this:
I am assumming because my summary log says "Failed" in the install section, that SQL Server failed to install. I may be wrong and this may be a bug in the summary log.
I am very very confused now. Do I or do I not need to install SQL Server Express Edition first?
|||SQL Server 2005 is the easiest SQL Server to install I have installed 7.0, 2000 and now 2005 on all exist operating systems except Vista, that means server included. Now if you are running XP it comes with System Restore roll your Operating System back by one month if you have restore point that far back. You cannot install this starter kit without SQL Server because I have not seen MySQL versions of it. The link I gave you is where errors for this kit are resolved and you are right your current problem is SQL Server installation so now go roll back the Operating System and try the install again. Now go do some work and post again.|||
I did a search and found a number of possible causes of this error, but the log segment you provided does not provide enough information to really tell what the issue is. For starters, check out the KB article at http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B920114 and see if this applies to your situation.
If that doesn't work, search the log for "ue 3" to find any lines that contain 'Return Value 3' indicating a failure. The several lines above the return value should give you a more specific message about what actually failed to cause the error you're seeing. If that information doesn't point you in an obvious direction, post that snippet to the forum and we can take a look at it.
Mike
install Performance Tools
Hi,
I have looked for some time now and I cannot see how to install the
Performance Tools in a pre installed SQL Server 20005. How do I go about this?
I am unaware of Microsoft Provided Performance tools. Are you by chance
talking about performance monitor? You can launch this via perfmon from the
command line. The DMV's also provide important performance counters.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
news:2131CACB-066A-40F5-A95E-B3EAFE509DB5@.microsoft.com...
> Hi,
> I have looked for some time now and I cannot see how to install the
> Performance Tools in a pre installed SQL Server 20005. How do I go about
> this?
|||Hi,
No. SQL Server has these tool. I belive it is what edition I have. I need
the standard not the workgroup.
Thanks
"Hilary Cotter" wrote:
> I am unaware of Microsoft Provided Performance tools. Are you by chance
> talking about performance monitor? You can launch this via perfmon from the
> command line. The DMV's also provide important performance counters.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
> news:2131CACB-066A-40F5-A95E-B3EAFE509DB5@.microsoft.com...
>
>
|||Hi,
I have upgraded from workgroup to standard and still I cannot find how to
add the sql performanve tools. We have one system that hase the tools on it
that was configured from the start but we cannot seem to add the tools if
they where not installed from the start. Please help.
Thanks
"SteelMillDon" wrote:
> Hi,
> I have looked for some time now and I cannot see how to install the
> Performance Tools in a pre installed SQL Server 20005. How do I go about this?
|||Do you have access to the SQL install media? If so, try running Setup again.
Sorry I can't be specific, I don't know 2005, but at some point during the
install, you should be offered the opportunity to install missing compnents,
such as Performance Tools.
Technosapien
"SteelMillDon" wrote:
[vbcol=seagreen]
> Hi,
> I have upgraded from workgroup to standard and still I cannot find how to
> add the sql performanve tools. We have one system that hase the tools on it
> that was configured from the start but we cannot seem to add the tools if
> they where not installed from the start. Please help.
> Thanks
> "SteelMillDon" wrote:
|||I have tried this but cannot find where this option is. I'm tryin to get
help from microsoft with my msdn support.
"Technosapien" wrote:
[vbcol=seagreen]
> Do you have access to the SQL install media? If so, try running Setup again.
> Sorry I can't be specific, I don't know 2005, but at some point during the
> install, you should be offered the opportunity to install missing compnents,
> such as Performance Tools.
> --
> Technosapien
>
> "SteelMillDon" wrote:
|||Are you looking for SQL Server Profiler and Database Engine Tuning Advisor?
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
"SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
news:C5534832-C3E4-48ED-AABC-3F20E8C5116C@.microsoft.com...[vbcol=seagreen]
>I have tried this but cannot find where this option is. I'm tryin to get
> help from microsoft with my msdn support.
> "Technosapien" wrote:
|||Yes
"Paul A. Mestemaker II [MSFT]" wrote:
> Are you looking for SQL Server Profiler and Database Engine Tuning Advisor?
> Paul A. Mestemaker II
> Program Manager
> Microsoft SQL Server Manageability
> http://blogs.msdn.com/sqlrem/
> "SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
> news:C5534832-C3E4-48ED-AABC-3F20E8C5116C@.microsoft.com...
>
>
|||What SKU of SQL Server are you using? (Express Edition, Workgroup Edition,
Standard Edition, Enterprise Edition, or Developer Edition). I believe
these performance tools are only included in Standard, Enterprise, and
Developer. They should be installed if you check the "Workstation
Components" in setup.
Feature Comparison Matrix:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
With a default installation of the workstation components, you can start
Profiler by running "Profiler90" from the run menu.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
"SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
news:89E6CBD9-FC09-4D3D-B3CB-A1A26EED57F7@.microsoft.com...[vbcol=seagreen]
> Yes
> "Paul A. Mestemaker II [MSFT]" wrote:
|||Standard. Read my past posts for more details
"Paul A. Mestemaker II [MSFT]" wrote:
> What SKU of SQL Server are you using? (Express Edition, Workgroup Edition,
> Standard Edition, Enterprise Edition, or Developer Edition). I believe
> these performance tools are only included in Standard, Enterprise, and
> Developer. They should be installed if you check the "Workstation
> Components" in setup.
> Feature Comparison Matrix:
> http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
> With a default installation of the workstation components, you can start
> Profiler by running "Profiler90" from the run menu.
> Paul A. Mestemaker II
> Program Manager
> Microsoft SQL Server Manageability
> http://blogs.msdn.com/sqlrem/
> "SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
> news:89E6CBD9-FC09-4D3D-B3CB-A1A26EED57F7@.microsoft.com...
>
>
sql
I have looked for some time now and I cannot see how to install the
Performance Tools in a pre installed SQL Server 20005. How do I go about this?
I am unaware of Microsoft Provided Performance tools. Are you by chance
talking about performance monitor? You can launch this via perfmon from the
command line. The DMV's also provide important performance counters.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
news:2131CACB-066A-40F5-A95E-B3EAFE509DB5@.microsoft.com...
> Hi,
> I have looked for some time now and I cannot see how to install the
> Performance Tools in a pre installed SQL Server 20005. How do I go about
> this?
|||Hi,
No. SQL Server has these tool. I belive it is what edition I have. I need
the standard not the workgroup.
Thanks
"Hilary Cotter" wrote:
> I am unaware of Microsoft Provided Performance tools. Are you by chance
> talking about performance monitor? You can launch this via perfmon from the
> command line. The DMV's also provide important performance counters.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
> news:2131CACB-066A-40F5-A95E-B3EAFE509DB5@.microsoft.com...
>
>
|||Hi,
I have upgraded from workgroup to standard and still I cannot find how to
add the sql performanve tools. We have one system that hase the tools on it
that was configured from the start but we cannot seem to add the tools if
they where not installed from the start. Please help.
Thanks
"SteelMillDon" wrote:
> Hi,
> I have looked for some time now and I cannot see how to install the
> Performance Tools in a pre installed SQL Server 20005. How do I go about this?
|||Do you have access to the SQL install media? If so, try running Setup again.
Sorry I can't be specific, I don't know 2005, but at some point during the
install, you should be offered the opportunity to install missing compnents,
such as Performance Tools.
Technosapien
"SteelMillDon" wrote:
[vbcol=seagreen]
> Hi,
> I have upgraded from workgroup to standard and still I cannot find how to
> add the sql performanve tools. We have one system that hase the tools on it
> that was configured from the start but we cannot seem to add the tools if
> they where not installed from the start. Please help.
> Thanks
> "SteelMillDon" wrote:
|||I have tried this but cannot find where this option is. I'm tryin to get
help from microsoft with my msdn support.
"Technosapien" wrote:
[vbcol=seagreen]
> Do you have access to the SQL install media? If so, try running Setup again.
> Sorry I can't be specific, I don't know 2005, but at some point during the
> install, you should be offered the opportunity to install missing compnents,
> such as Performance Tools.
> --
> Technosapien
>
> "SteelMillDon" wrote:
|||Are you looking for SQL Server Profiler and Database Engine Tuning Advisor?
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
"SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
news:C5534832-C3E4-48ED-AABC-3F20E8C5116C@.microsoft.com...[vbcol=seagreen]
>I have tried this but cannot find where this option is. I'm tryin to get
> help from microsoft with my msdn support.
> "Technosapien" wrote:
|||Yes
"Paul A. Mestemaker II [MSFT]" wrote:
> Are you looking for SQL Server Profiler and Database Engine Tuning Advisor?
> Paul A. Mestemaker II
> Program Manager
> Microsoft SQL Server Manageability
> http://blogs.msdn.com/sqlrem/
> "SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
> news:C5534832-C3E4-48ED-AABC-3F20E8C5116C@.microsoft.com...
>
>
|||What SKU of SQL Server are you using? (Express Edition, Workgroup Edition,
Standard Edition, Enterprise Edition, or Developer Edition). I believe
these performance tools are only included in Standard, Enterprise, and
Developer. They should be installed if you check the "Workstation
Components" in setup.
Feature Comparison Matrix:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
With a default installation of the workstation components, you can start
Profiler by running "Profiler90" from the run menu.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
"SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
news:89E6CBD9-FC09-4D3D-B3CB-A1A26EED57F7@.microsoft.com...[vbcol=seagreen]
> Yes
> "Paul A. Mestemaker II [MSFT]" wrote:
|||Standard. Read my past posts for more details
"Paul A. Mestemaker II [MSFT]" wrote:
> What SKU of SQL Server are you using? (Express Edition, Workgroup Edition,
> Standard Edition, Enterprise Edition, or Developer Edition). I believe
> these performance tools are only included in Standard, Enterprise, and
> Developer. They should be installed if you check the "Workstation
> Components" in setup.
> Feature Comparison Matrix:
> http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
> With a default installation of the workstation components, you can start
> Profiler by running "Profiler90" from the run menu.
> Paul A. Mestemaker II
> Program Manager
> Microsoft SQL Server Manageability
> http://blogs.msdn.com/sqlrem/
> "SteelMillDon" <SteelMillDon@.noemail.noemail> wrote in message
> news:89E6CBD9-FC09-4D3D-B3CB-A1A26EED57F7@.microsoft.com...
>
>
sql
Install of SQL express edition with vs2005 pro
I was able to install and use the vs 2005 for the first time today, and it was so far, so good!
However, I would like to know more about how it setup my SQL 2005 Express edition when I installed the full package of vs2005. What I would like to specifically know -- if the instance is using my Windows Authentication, or what the "sa" password might be.
When installing vs2005, it automatically installed SQL Express 2005, without prompting me for setup options on the sql part. Soooo, does is use windows authentication automatically, or some type of default "sa" password.
Very curious to know...
I'm pretty sure that by default it gets installed using Windows Authentication mode, so SA is disabled.
Paul
sqlInstall of SQL express edition with vs2005 pro
I was able to install and use the vs 2005 for the first time today, and it was so far, so good!
However, I would like to know more about how it setup my SQL 2005 Express edition when I installed the full package of vs2005. What I would like to specifically know -- if the instance is using my Windows Authentication, or what the "sa" password might be.
When installing vs2005, it automatically installed SQL Express 2005, without prompting me for setup options on the sql part. Soooo, does is use windows authentication automatically, or some type of default "sa" password.
Very curious to know...
I'm pretty sure that by default it gets installed using Windows Authentication mode, so SA is disabled.
Paul
Monday, March 26, 2012
Install issue with SQL Server 2005 Enterprise
I am having a really hard time installing SQL Server 2005 Enterprise
Edition. My server definitely meets the hardware requirements of the
server. The server OS is Windows 2003 Enterprise R2. The problem
occurs during setup. After checking my system configuration, it goes
to the window that generates a list of items it is going to install (I
believe). Here, as soon as it starts generating the list, it freezes
the whole server and then shuts down. It does this every single time.
Any thoughts or suggestions?
First thing, check the setup log files in C:\Program Files\Microsoft SQL
Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
error info.
Linchi
"CarlosSanchezJr@.gmail.com" wrote:
> I am having a really hard time installing SQL Server 2005 Enterprise
> Edition. My server definitely meets the hardware requirements of the
> server. The server OS is Windows 2003 Enterprise R2. The problem
> occurs during setup. After checking my system configuration, it goes
> to the window that generates a list of items it is going to install (I
> believe). Here, as soon as it starts generating the list, it freezes
> the whole server and then shuts down. It does this every single time.
> Any thoughts or suggestions?
>
|||In addition , if your computer is connected to the network , try unplug
the cable and start an installation
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...[vbcol=seagreen]
> First thing, check the setup log files in C:\Program Files\Microsoft SQL
> Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> error info.
> Linchi
> "CarlosSanchezJr@.gmail.com" wrote:
|||I have checked the log files and did not see anything there that caused
an issue. I also tried the disabling of my network connection and that
also did not work.
I am at a complete loss here. Everything is great until it does the
System Configuration Check. Then it just suddenly freezes the whole
server and I have to do a hard reboot.
Uri Dimant wrote:[vbcol=seagreen]
> In addition , if your computer is connected to the network , try unplug
> the cable and start an installation
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...
|||Never did get this working on 2003 Enterprise R2, however, I tried it
on 2003 Standard R2 and it installed without any problems. Very odd.
CarlosSanchezJr@.gmail.com wrote:[vbcol=seagreen]
> I have checked the log files and did not see anything there that caused
> an issue. I also tried the disabling of my network connection and that
> also did not work.
> I am at a complete loss here. Everything is great until it does the
> System Configuration Check. Then it just suddenly freezes the whole
> server and I have to do a hard reboot.
> Uri Dimant wrote:
Edition. My server definitely meets the hardware requirements of the
server. The server OS is Windows 2003 Enterprise R2. The problem
occurs during setup. After checking my system configuration, it goes
to the window that generates a list of items it is going to install (I
believe). Here, as soon as it starts generating the list, it freezes
the whole server and then shuts down. It does this every single time.
Any thoughts or suggestions?
First thing, check the setup log files in C:\Program Files\Microsoft SQL
Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
error info.
Linchi
"CarlosSanchezJr@.gmail.com" wrote:
> I am having a really hard time installing SQL Server 2005 Enterprise
> Edition. My server definitely meets the hardware requirements of the
> server. The server OS is Windows 2003 Enterprise R2. The problem
> occurs during setup. After checking my system configuration, it goes
> to the window that generates a list of items it is going to install (I
> believe). Here, as soon as it starts generating the list, it freezes
> the whole server and then shuts down. It does this every single time.
> Any thoughts or suggestions?
>
|||In addition , if your computer is connected to the network , try unplug
the cable and start an installation
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...[vbcol=seagreen]
> First thing, check the setup log files in C:\Program Files\Microsoft SQL
> Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> error info.
> Linchi
> "CarlosSanchezJr@.gmail.com" wrote:
|||I have checked the log files and did not see anything there that caused
an issue. I also tried the disabling of my network connection and that
also did not work.
I am at a complete loss here. Everything is great until it does the
System Configuration Check. Then it just suddenly freezes the whole
server and I have to do a hard reboot.
Uri Dimant wrote:[vbcol=seagreen]
> In addition , if your computer is connected to the network , try unplug
> the cable and start an installation
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...
|||Never did get this working on 2003 Enterprise R2, however, I tried it
on 2003 Standard R2 and it installed without any problems. Very odd.
CarlosSanchezJr@.gmail.com wrote:[vbcol=seagreen]
> I have checked the log files and did not see anything there that caused
> an issue. I also tried the disabling of my network connection and that
> also did not work.
> I am at a complete loss here. Everything is great until it does the
> System Configuration Check. Then it just suddenly freezes the whole
> server and I have to do a hard reboot.
> Uri Dimant wrote:
Install issue with SQL Server 2005 Enterprise
I am having a really hard time installing SQL Server 2005 Enterprise
Edition. My server definitely meets the hardware requirements of the
server. The server OS is Windows 2003 Enterprise R2. The problem
occurs during setup. After checking my system configuration, it goes
to the window that generates a list of items it is going to install (I
believe). Here, as soon as it starts generating the list, it freezes
the whole server and then shuts down. It does this every single time.
Any thoughts or suggestions?First thing, check the setup log files in C:\Program Files\Microsoft SQL
Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
error info.
Linchi
"CarlosSanchezJr@.gmail.com" wrote:
> I am having a really hard time installing SQL Server 2005 Enterprise
> Edition. My server definitely meets the hardware requirements of the
> server. The server OS is Windows 2003 Enterprise R2. The problem
> occurs during setup. After checking my system configuration, it goes
> to the window that generates a list of items it is going to install (I
> believe). Here, as soon as it starts generating the list, it freezes
> the whole server and then shuts down. It does this every single time.
> Any thoughts or suggestions?
>|||In addition , if your computer is connected to the network , try unplug
the cable and start an installation
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...
> First thing, check the setup log files in C:\Program Files\Microsoft SQL
> Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> error info.
> Linchi
> "CarlosSanchezJr@.gmail.com" wrote:
>> I am having a really hard time installing SQL Server 2005 Enterprise
>> Edition. My server definitely meets the hardware requirements of the
>> server. The server OS is Windows 2003 Enterprise R2. The problem
>> occurs during setup. After checking my system configuration, it goes
>> to the window that generates a list of items it is going to install (I
>> believe). Here, as soon as it starts generating the list, it freezes
>> the whole server and then shuts down. It does this every single time.
>> Any thoughts or suggestions?
>>|||I have checked the log files and did not see anything there that caused
an issue. I also tried the disabling of my network connection and that
also did not work.
I am at a complete loss here. Everything is great until it does the
System Configuration Check. Then it just suddenly freezes the whole
server and I have to do a hard reboot.
Uri Dimant wrote:
> In addition , if your computer is connected to the network , try unplug
> the cable and start an installation
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...
> > First thing, check the setup log files in C:\Program Files\Microsoft SQL
> > Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> > error info.
> >
> > Linchi
> >
> > "CarlosSanchezJr@.gmail.com" wrote:
> >
> >> I am having a really hard time installing SQL Server 2005 Enterprise
> >> Edition. My server definitely meets the hardware requirements of the
> >> server. The server OS is Windows 2003 Enterprise R2. The problem
> >> occurs during setup. After checking my system configuration, it goes
> >> to the window that generates a list of items it is going to install (I
> >> believe). Here, as soon as it starts generating the list, it freezes
> >> the whole server and then shuts down. It does this every single time.
> >>
> >> Any thoughts or suggestions?
> >>
> >>|||Never did get this working on 2003 Enterprise R2, however, I tried it
on 2003 Standard R2 and it installed without any problems. Very odd.
CarlosSanchezJr@.gmail.com wrote:
> I have checked the log files and did not see anything there that caused
> an issue. I also tried the disabling of my network connection and that
> also did not work.
> I am at a complete loss here. Everything is great until it does the
> System Configuration Check. Then it just suddenly freezes the whole
> server and I have to do a hard reboot.
> Uri Dimant wrote:
> > In addition , if your computer is connected to the network , try unplug
> > the cable and start an installation
> >
> >
> > "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> > news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...
> > > First thing, check the setup log files in C:\Program Files\Microsoft SQL
> > > Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> > > error info.
> > >
> > > Linchi
> > >
> > > "CarlosSanchezJr@.gmail.com" wrote:
> > >
> > >> I am having a really hard time installing SQL Server 2005 Enterprise
> > >> Edition. My server definitely meets the hardware requirements of the
> > >> server. The server OS is Windows 2003 Enterprise R2. The problem
> > >> occurs during setup. After checking my system configuration, it goes
> > >> to the window that generates a list of items it is going to install (I
> > >> believe). Here, as soon as it starts generating the list, it freezes
> > >> the whole server and then shuts down. It does this every single time.
> > >>
> > >> Any thoughts or suggestions?
> > >>
> > >>
Edition. My server definitely meets the hardware requirements of the
server. The server OS is Windows 2003 Enterprise R2. The problem
occurs during setup. After checking my system configuration, it goes
to the window that generates a list of items it is going to install (I
believe). Here, as soon as it starts generating the list, it freezes
the whole server and then shuts down. It does this every single time.
Any thoughts or suggestions?First thing, check the setup log files in C:\Program Files\Microsoft SQL
Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
error info.
Linchi
"CarlosSanchezJr@.gmail.com" wrote:
> I am having a really hard time installing SQL Server 2005 Enterprise
> Edition. My server definitely meets the hardware requirements of the
> server. The server OS is Windows 2003 Enterprise R2. The problem
> occurs during setup. After checking my system configuration, it goes
> to the window that generates a list of items it is going to install (I
> believe). Here, as soon as it starts generating the list, it freezes
> the whole server and then shuts down. It does this every single time.
> Any thoughts or suggestions?
>|||In addition , if your computer is connected to the network , try unplug
the cable and start an installation
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...
> First thing, check the setup log files in C:\Program Files\Microsoft SQL
> Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> error info.
> Linchi
> "CarlosSanchezJr@.gmail.com" wrote:
>> I am having a really hard time installing SQL Server 2005 Enterprise
>> Edition. My server definitely meets the hardware requirements of the
>> server. The server OS is Windows 2003 Enterprise R2. The problem
>> occurs during setup. After checking my system configuration, it goes
>> to the window that generates a list of items it is going to install (I
>> believe). Here, as soon as it starts generating the list, it freezes
>> the whole server and then shuts down. It does this every single time.
>> Any thoughts or suggestions?
>>|||I have checked the log files and did not see anything there that caused
an issue. I also tried the disabling of my network connection and that
also did not work.
I am at a complete loss here. Everything is great until it does the
System Configuration Check. Then it just suddenly freezes the whole
server and I have to do a hard reboot.
Uri Dimant wrote:
> In addition , if your computer is connected to the network , try unplug
> the cable and start an installation
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...
> > First thing, check the setup log files in C:\Program Files\Microsoft SQL
> > Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> > error info.
> >
> > Linchi
> >
> > "CarlosSanchezJr@.gmail.com" wrote:
> >
> >> I am having a really hard time installing SQL Server 2005 Enterprise
> >> Edition. My server definitely meets the hardware requirements of the
> >> server. The server OS is Windows 2003 Enterprise R2. The problem
> >> occurs during setup. After checking my system configuration, it goes
> >> to the window that generates a list of items it is going to install (I
> >> believe). Here, as soon as it starts generating the list, it freezes
> >> the whole server and then shuts down. It does this every single time.
> >>
> >> Any thoughts or suggestions?
> >>
> >>|||Never did get this working on 2003 Enterprise R2, however, I tried it
on 2003 Standard R2 and it installed without any problems. Very odd.
CarlosSanchezJr@.gmail.com wrote:
> I have checked the log files and did not see anything there that caused
> an issue. I also tried the disabling of my network connection and that
> also did not work.
> I am at a complete loss here. Everything is great until it does the
> System Configuration Check. Then it just suddenly freezes the whole
> server and I have to do a hard reboot.
> Uri Dimant wrote:
> > In addition , if your computer is connected to the network , try unplug
> > the cable and start an installation
> >
> >
> > "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> > news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...
> > > First thing, check the setup log files in C:\Program Files\Microsoft SQL
> > > Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> > > error info.
> > >
> > > Linchi
> > >
> > > "CarlosSanchezJr@.gmail.com" wrote:
> > >
> > >> I am having a really hard time installing SQL Server 2005 Enterprise
> > >> Edition. My server definitely meets the hardware requirements of the
> > >> server. The server OS is Windows 2003 Enterprise R2. The problem
> > >> occurs during setup. After checking my system configuration, it goes
> > >> to the window that generates a list of items it is going to install (I
> > >> believe). Here, as soon as it starts generating the list, it freezes
> > >> the whole server and then shuts down. It does this every single time.
> > >>
> > >> Any thoughts or suggestions?
> > >>
> > >>
Install issue with SQL Server 2005 Enterprise
I am having a really hard time installing SQL Server 2005 Enterprise
Edition. My server definitely meets the hardware requirements of the
server. The server OS is Windows 2003 Enterprise R2. The problem
occurs during setup. After checking my system configuration, it goes
to the window that generates a list of items it is going to install (I
believe). Here, as soon as it starts generating the list, it freezes
the whole server and then shuts down. It does this every single time.
Any thoughts or suggestions?First thing, check the setup log files in C:\Program Files\Microsoft SQL
Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
error info.
Linchi
"CarlosSanchezJr@.gmail.com" wrote:
> I am having a really hard time installing SQL Server 2005 Enterprise
> Edition. My server definitely meets the hardware requirements of the
> server. The server OS is Windows 2003 Enterprise R2. The problem
> occurs during setup. After checking my system configuration, it goes
> to the window that generates a list of items it is going to install (I
> believe). Here, as soon as it starts generating the list, it freezes
> the whole server and then shuts down. It does this every single time.
> Any thoughts or suggestions?
>|||In addition , if your computer is connected to the network , try unplug
the cable and start an installation
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...[vbcol=seagreen]
> First thing, check the setup log files in C:\Program Files\Microsoft SQL
> Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> error info.
> Linchi
> "CarlosSanchezJr@.gmail.com" wrote:
>|||I have checked the log files and did not see anything there that caused
an issue. I also tried the disabling of my network connection and that
also did not work.
I am at a complete loss here. Everything is great until it does the
System Configuration Check. Then it just suddenly freezes the whole
server and I have to do a hard reboot.
Uri Dimant wrote:[vbcol=seagreen]
> In addition , if your computer is connected to the network , try unplug
> the cable and start an installation
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...|||Never did get this working on 2003 Enterprise R2, however, I tried it
on 2003 Standard R2 and it installed without any problems. Very odd.
CarlosSanchezJr@.gmail.com wrote:[vbcol=seagreen]
> I have checked the log files and did not see anything there that caused
> an issue. I also tried the disabling of my network connection and that
> also did not work.
> I am at a complete loss here. Everything is great until it does the
> System Configuration Check. Then it just suddenly freezes the whole
> server and I have to do a hard reboot.
> Uri Dimant wrote:sql
Edition. My server definitely meets the hardware requirements of the
server. The server OS is Windows 2003 Enterprise R2. The problem
occurs during setup. After checking my system configuration, it goes
to the window that generates a list of items it is going to install (I
believe). Here, as soon as it starts generating the list, it freezes
the whole server and then shuts down. It does this every single time.
Any thoughts or suggestions?First thing, check the setup log files in C:\Program Files\Microsoft SQL
Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
error info.
Linchi
"CarlosSanchezJr@.gmail.com" wrote:
> I am having a really hard time installing SQL Server 2005 Enterprise
> Edition. My server definitely meets the hardware requirements of the
> server. The server OS is Windows 2003 Enterprise R2. The problem
> occurs during setup. After checking my system configuration, it goes
> to the window that generates a list of items it is going to install (I
> believe). Here, as soon as it starts generating the list, it freezes
> the whole server and then shuts down. It does this every single time.
> Any thoughts or suggestions?
>|||In addition , if your computer is connected to the network , try unplug
the cable and start an installation
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...[vbcol=seagreen]
> First thing, check the setup log files in C:\Program Files\Microsoft SQL
> Server\90\Setup Bootstrap\LOG\Files for where the setup failed and for any
> error info.
> Linchi
> "CarlosSanchezJr@.gmail.com" wrote:
>|||I have checked the log files and did not see anything there that caused
an issue. I also tried the disabling of my network connection and that
also did not work.
I am at a complete loss here. Everything is great until it does the
System Configuration Check. Then it just suddenly freezes the whole
server and I have to do a hard reboot.
Uri Dimant wrote:[vbcol=seagreen]
> In addition , if your computer is connected to the network , try unplug
> the cable and start an installation
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:0A94A25C-0C87-4777-92FF-4F76A5420387@.microsoft.com...|||Never did get this working on 2003 Enterprise R2, however, I tried it
on 2003 Standard R2 and it installed without any problems. Very odd.
CarlosSanchezJr@.gmail.com wrote:[vbcol=seagreen]
> I have checked the log files and did not see anything there that caused
> an issue. I also tried the disabling of my network connection and that
> also did not work.
> I am at a complete loss here. Everything is great until it does the
> System Configuration Check. Then it just suddenly freezes the whole
> server and I have to do a hard reboot.
> Uri Dimant wrote:sql
Friday, March 23, 2012
Install Errors
Hello,
I've been trying to install SQL Server express edition all day and it errors out every time. I've tried it on two different servers and I get the same errors. Here's what the error log says:
2007-04-20 16:37:52.77 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2, v.2825)
2007-04-20 16:37:52.77 Server (c) 2005 Microsoft Corporation.
2007-04-20 16:37:52.77 Server All rights reserved.
2007-04-20 16:37:52.77 Server Server process ID is 1356.
2007-04-20 16:37:52.77 Server Authentication mode is MIXED.
2007-04-20 16:37:52.77 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-04-20 16:37:52.77 Server This instance of SQL Server last reported using a process ID of 1964 at 4/20/2007 4:37:47 PM (local) 4/20/2007 8:37:47 PM (UTC). This is an informational message only; no user action is required.
2007-04-20 16:37:52.77 Server Registry startup parameters:
2007-04-20 16:37:52.77 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-04-20 16:37:52.77 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-04-20 16:37:52.77 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-04-20 16:37:52.77 Server Command Line Startup Parameters:
2007-04-20 16:37:52.77 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\master.mdf
2007-04-20 16:37:52.77 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mastlog.ldf
2007-04-20 16:37:52.77 Server -m SqlSetup
2007-04-20 16:37:52.77 Server SqlSetup
2007-04-20 16:37:52.77 Server -Q
2007-04-20 16:37:52.77 Server -q SQL_Latin1_General_CP1_CI_AS
2007-04-20 16:37:52.77 Server -T 4022
2007-04-20 16:37:52.77 Server -T 3659
2007-04-20 16:37:52.77 Server -T 3610
2007-04-20 16:37:52.77 Server -T 4010
2007-04-20 16:37:52.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-04-20 16:37:52.79 Server Detected 1 CPUs. This is an informational message; no user action is required.
2007-04-20 16:37:52.88 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-04-20 16:37:52.92 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-04-20 16:37:52.93 spid5s Warning ******************
2007-04-20 16:37:52.93 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2007-04-20 16:37:52.93 spid5s Starting up database 'master'.
2007-04-20 16:37:52.93 spid5s Error: 17207, Severity: 16, State: 1.
2007-04-20 16:37:52.93 spid5s FCB:
pen: Operating system error 5(Access is denied.) occurred while creating or opening file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\master.mdf'. Diagnose and correct the operating system error, and retry the operation.
2007-04-20 16:37:52.97 spid5s Error: 17204, Severity: 16, State: 1.
2007-04-20 16:37:52.97 spid5s FCB:pen failed: Could not open file c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\master.mdf for file number 1. OS error: 5(Access is denied.).
2007-04-20 16:37:52.98 spid5s Error: 5120, Severity: 16, State: 101.
2007-04-20 16:37:52.98 spid5s Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\master.mdf". Operating system error 5: "5(Access is denied.)".
2007-04-20 16:37:53.05 spid5s Error: 17207, Severity: 16, State: 1.
2007-04-20 16:37:53.05 spid5s FCB:pen: Operating system error 5(Access is denied.) occurred while creating or opening file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mastlog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2007-04-20 16:37:53.05 spid5s Error: 17204, Severity: 16, State: 1.
2007-04-20 16:37:53.05 spid5s FCB:pen failed: Could not open file c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mastlog.ldf for file number 2. OS error: 5(Access is denied.).
2007-04-20 16:37:53.05 spid5s Error: 5120, Severity: 16, State: 101.
2007-04-20 16:37:53.05 spid5s Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mastlog.ldf". Operating system error 5: "5(Access is denied.)".
What exact steps are you trying to perform here and what log file is this comming from?
Basically this is saying that you don't have permissions to a bunch of files that SQL Express is trying to access, the fact that it's happening on two different computers would suggest that they both share some kind of security policy that is limiting your user account in some way. If this is a corporate computer, check with your IT staff to see what kind of security policies they have running, you need to be a computer administrator to install SQL Express.
Mike
|||I'm logged in as administrator however I had to check the option to add my user to the SQL Server Administrator role in order for the install to work.Now that I got it installed I can't connect, the service is running but the osql command fails every time I try it and Plesk cannot connect to the server to add a database.
Monday, March 12, 2012
InSQL 7.1 - count how many times a tag equals 1 over a specified time period query....
Need help to create a query to count how many times over a specified time the tag(s) equal the value of 1.
'month'=month(datetime),
'YEAR'=YEAR(DATETIME),
TAGVALUE =1,
FREQ = COUNT(*)
FROM AnalogTag at, v_AnalogHistory ah
WHERE DateTime >= "2007/07/01 00:00"
AND DateTime <= "2007/07/31 00:00"
AND ah.TagName in ('PV249_STEP_NO')
AND ah.Value = 1
AND ah.TagName = at.TagName
AND wwRetrievalMode = 'DELTA'
GROUP BY at.TagName, month(DATETIME), YEAR(DATETIME)
Thanks
Gary
Would you please provide some sample data and an example of expected results?
|||SELECT at.TagName,'month'=month(datetime),
'YEAR'=YEAR(DATETIME),
TAGVALUE =1,
FREQ = COUNT(*)
FROM AnalogTag at, v_AnalogHistory ah
WHERE DateTime >= "2007/07/01 00:00"
AND DateTime <= "2007/07/31 00:00"
AND ah.TagName in ('PV249_STEP_NO')
AND ah.Value = 1
AND ah.TagName = at.TagName
AND wwRetrievalMode = 'DELTA'
GROUP BY at.TagName, month(DATETIME), YEAR(DATETIME)
I think I did it, using the above. I need to test a little more.
the value of the tag increments from 1 to 64, my purpose is to count the cycles of the tag.
Thanks
Gary|||
It looks like you have it correct for TagValue = 1; if you are looking to get it for all 64 different values of the tag, it would be something like:
Code Snippet
SELECT at.TagName,
'month'=month(datetime),
'YEAR'=YEAR(DATETIME),
-- TAGVALUE =1,
ah.value as TAGVALUE,
FREQ = COUNT(*)
FROM AnalogTag at, v_AnalogHistory ah
WHERE DateTime >= "2007/07/01 00:00"
AND DateTime <= "2007/07/31 00:00"
AND ah.TagName in ('PV249_STEP_NO')
-- AND ah.Value = 1
AND ah.TagName = at.TagName
AND wwRetrievalMode = 'DELTA'
GROUP BY at.TagName, ah.value, month(DATETIME), YEAR(DATETIME)
Friday, March 9, 2012
Inside a project you lose the control?
I've got a project with 12 packages. One of them runnning and at the same time when I try to alter another one or even add a new task I see that all the tasks on toolbox are disabled.
Why?
I would like to hear a good reason for this behaviour, afaik I don't get the point...
Often the packages in one project call into each other, so if one of them is currently executing - there is a good chance others will be running as well. Although I agree this might be too restrictive sometimes - please file a suggestion to relax this behavior for next version.|||suggestions may be submitted here: https://connect.microsoft.com/feedback/default.aspx?SiteID=68Michael Entin - MSFT wrote:
please file a suggestion to relax this behavior for next version.
Inserts taking longer time
Hello All,
Thanks a Ton for your reply. There would have been no way in the world through which i could have figured this out
. The other thing I want to ask is that how can we disable the caching on our server. I mean could not exactly figure out how did the begin tran and commit solved the purpose. Will be really helpful if you can tell how to disable the caching and hardening and is this safe.
I have SQL Server 2005 installed on my machine and I am firing following query to insert 1500 records into a simple table having just on column.
Declare @.i int
Set @.i=0
While (@.i<1500)
Begin
Insert into test2 values (@.i)
Set @.i=@.i+1
End
Here goes the table definition,
CREATE TABLE [dbo].[test2](
[int] NULL
) ON [PRIMARY]
Now the problem with this is that on one of my server this query is taking just 500ms to run while on my production and other test server this query is taking more than 25 seconds.
Same is the problem with updates. I have checked the configurations of both the servers and found them to be the same. Also there are no indexes defined on either of the tables. I was wondering what can be the possible reason for this to happen. If any of u people has any pointers regarding this, will be really useful
Thanks in advance,
Mitesh
Although this can′t be the possible cause, which recovery models are you using on the databases ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Hey Jens,
Thanks for the pointer but we are using the Full Recovery model on both of my database. I think there is some problem with the server configuration as I have tried this Insert on multiple databases of my server (where the time taken is more) and have got the same output 
|||
You machine is probably caching disk writes so the commits are not actually hardening.Servers are usually configured not to do that so your data is not at risk.
You should wrap your loop with a BEGIN TRAN and COMMIT TRAN.
Declare @.i int
Set @.i=0
Begin Tran
While (@.i<1500)
Begin
Insert into test2 values (@.i)
Set @.i=@.i+1
End
Commit Tran
Hi Mitesh,
I am having a very similar problem:
* I have a crappy testing machine (P3 at 0.5 GHz on Windows NT Server) with SQL 7,
* I have a testing environment running on a Virtual Machine on a pretty descent laptop (Laptop = Celeron @. 1.59 GHz on Windows XP - sorry, low budget -). The Virtual Machine runs Windows 2003 with SQL 2005 Express, with 400 MBytes assigned in RAM.
* The database I work with is created running an SQL script. It has about 15 tables, and as a whole is a quite normalized database.
* I have this application that I did, that updates the database through ODBC.
Now here is the interesting data:
* On my SQL 7, it takes between 2 to 3 seconds to update the database (we are talking about 50 to 100 insert statements) the first time I click on the "save" button. After that is just a matter of a little bit less than a second to update the database every time I click on the "save" button.
* However, on my SQL 2005 environment, it takes about 1 minute. The amount of time does not change much the next time I click "save".
Notes aside:
* Both are empty databases. They only have the table structure.
* The tables are quite normalized. It is ok, it is not a database that it is intended to grow beyond 100 Mbytes.
* "De-normalization" is not an option.
* I changed the size of the database log file from 1 Mbyte to 20 to see if my problem were excesive "check points"... but the behaviour was just the same.
I learned to live with it, after all, Windows XP does not support VM's. In fact, I was rather impressed by the Celeron chip.
But the fact that caught my attention is that, after time went by and I continued using my Virtual Machine, the time got reduced as my database grew up in size. After about 100 "save" operations, It now takes around 10 seconds to save. This suggests me that there is something going on with the indexes...
It is ok, after all, it is just a testing environment.
Hope it helps!!!
Tark Ik
PS: This posting has been posted "AS IS"
|||Hey Peter,Thanks a Ton for your reply. There would have been no way in the world through which i could have figured this out
. The other thing I want to ask is that how can we disable the caching on our server. I mean could not exactly figure out how did the begin tran and commit solved the purpose. Will be really helpful if you can tell how to disable the caching and hardening and is this safe.Friday, February 24, 2012
inserting the current date and time into SQL Server database
I need an SQL string that inserts the current date into a database.
So far I have tried:
SQL = "INSERT INTO X (START_DATE) VALUES('" & Date.Now &"')"
mycomm =
New SqlCommand(sql, myconn)mycomm.ExecuteNonQuery()
However, there is a problem with the SQL command. The problem is related to the date. Is there a way of programatically inserting the current date/time into the SQL database? Language used is VB.
GetDate() is a function in SQL Server that returns the current timestamp. So you can directly use that.
SQL = "INSERT INTO X (START_DATE) VALUES( GetDate())"
Sunday, February 19, 2012
Inserting records and running a stored procedure at the same time?
Hi there..
The target table got these two 'must be set columns', one called DATASET, an
d
one called LXBENUMMER.
Now, when I want to insert data into this target table I need to fill those
two
columns with the new records I'm inserting. DATASET is easy as it'll always
be a
fixed value, however, LXBENUMMER must be set with a number that comes from a
stored procedure.
If I do an exec sp_xal_seqno 1, 'DAT' I get a number back, which must be put
in
LXBENUMMER with the new record.
An example-
insert tbl1
(dataset,lxbenummer,col1,col2,col3,etc)
select 'DAT',**value from stored procedure**, col1, col2, col3, etc
from tbl2
How do I go about this?
I doubt, therefore I might be.Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, data types, etc. in
your schema are. Sample data is also a good idea, along with clear
specifications. It is very hard to debug code when you do not let us
see it.
Also, you do not know that a column is not anything like a field and
that a row is not a record. After 20+ years of doing SQL and charging
a lot of money for consulting work in correctly schemas, this is a
signal that you are really screwed up.|||"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1129947794.955269.92220@.g43g2000cwa.googlegroups.com
> Also, you do not know that a column is not anything like a field and
> that a row is not a record. After 20+ years of doing SQL and charging
Well everywhere I look, row and record is the same and is used interchangeab
le.
Why should I think different? I don't see where I wrote field and compared i
t
with a column; but well you do know better.
> a lot of money for consulting work in correctly schemas, this is a
> signal that you are really screwed up.
Dude, you need to take a break from time to time, instead of throwing dirt a
t
those to aren't "worthy" compared to you. I'd see your point better if you h
ad
kept it nicer.
I'm screwed up if I write nutty SQL? Man, if you think that, you /seriously/
need to take a break from anything relating to computers.
Anyway, I shall post again when I have a DDL ready.
--
I doubt, therefore I might be.|||Kim Noer (kn@.nospam.dk) writes:
> The target table got these two 'must be set columns', one called
> DATASET, and one called LXBENUMMER.
> Now, when I want to insert data into this target table I need to fill
> those two columns with the new records I'm inserting. DATASET is easy as
> it'll always be a fixed value, however, LXBENUMMER must be set with a
> number that comes from a stored procedure.
> If I do an exec sp_xal_seqno 1, 'DAT' I get a number back, which must be
> put in LXBENUMMER with the new record.
General comment: don't use sp_ as the leading charcters in the name of
your objects. This prefix is reserved for SQL Server, and SQL Server will
first look in master for these objects.
> An example-
> insert tbl1
> (dataset,lxbenummer,col1,col2,col3,etc)
> select 'DAT',**value from stored procedure**, col1, col2, col3, etc
> from tbl2
> How do I go about this?
There are number of options, of which some requires you to change
the procedure. I happen to have an article about this on my web site:
http://www.sommarskog.se/share_data.html.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||From your attitude i'd be suprised if anybody outside of education has hired
you in the past couple of years!
You need to bring your skills up-to-date with what business wants now, not
15 years ago.
Times have significantly changed and you seem to have been left behind.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1129947794.955269.92220@.g43g2000cwa.googlegroups.com...
> Please post DDL, so that people do not have to guess what the keys,
> constraints, Declarative Referential Integrity, data types, etc. in
> your schema are. Sample data is also a good idea, along with clear
> specifications. It is very hard to debug code when you do not let us
> see it.
> Also, you do not know that a column is not anything like a field and
> that a row is not a record. After 20+ years of doing SQL and charging
> a lot of money for consulting work in correctly schemas, this is a
> signal that you are really screwed up.
>|||"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1129947794.955269.92220@.g43g2000cwa.googlegroups.com
> Please post DDL, so that people do not have to guess what the keys,
> constraints, Declarative Referential Integrity, data types, etc. in
> your schema are. Sample data is also a good idea, along with clear
> specifications. It is very hard to debug code when you do not let us
> see it.
CREATE TABLE [tbl1] (
[DATASET] [varchar] (3) COLLATE SQL_Danish_Pref_CP1_CI_AS NOT NULL ,
[LXBENUMMER] [int] NOT NULL ,
[col1] [varchar] (30) COLLATE SQL_Danish_Pref_CP1_CI_AS NOT NULL
) ON [PRIMARY]
GO
CREATE TABLE [XALSEQ] (
[SEQID] [int] NOT NULL ,
[DATASET] [varchar] (3) COLLATE SQL_Danish_Pref_CP1_CI_AS NOT NULL ,
[SEQNO] [int] NOT NULL
) ON [PRIMARY]
GO
INSERT INTO XALSEQ
VALUES (0,'DAT',1000)
GO
INSERT INTO tbl1
VALUES ('DAT',1000,'somerandomtext')
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE PROCEDURE sp_xal_seqno @.increment INT, @.dataset CHAR(3) AS
BEGIN TRAN
UPDATE XALSEQ SET SEQNO = SEQNO + @.increment
WHERE DATASET = @.dataset AND SEQID = 0
SELECT SEQNO - @.increment FROM XALSEQ
WHERE DATASET = @.dataset AND SEQID = 0
COMMIT TRAN
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
I doubt, therefore I might be.|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns96F7D40BB5DE7Yazorman@.127.0.0.1
> General comment: don't use sp_ as the leading charcters in the name of
> your objects. This prefix is reserved for SQL Server, and SQL Server
> will first look in master for these objects.
Aye, I name all those I create differently, but alas, I did not get to chose
the
name of the stored procedure, this one comes from MBS themself.
> There are number of options, of which some requires you to change
> the procedure. I happen to have an article about this on my web site:
> http://www.sommarskog.se/share_data.html.
In my second post to Celko, I've included the structure of the tables, the S
P
and tiny amount of sample data, if that helps point me in the correct direct
ion
(I'm going to read up on your article anyway though).
Basically, the whole purpose is to make sure that every single row (or is it
record?) get their very own unique number. It would be exceedingly lovely if
any
solution to this particular problem could be made generic if possible.
Thanks in advance.
--
I doubt, therefore I might be.|||Kim Noer (kn@.nospam.dk) writes:
> Aye, I name all those I create differently, but alas, I did not get to
> chose the name of the stored procedure, this one comes from MBS
> themself.
MBS? That's some third-party software?
> Basically, the whole purpose is to make sure that every single row (or
> is it record?) get their very own unique number. It would be exceedingly
> lovely if any solution to this particular problem could be made generic
> if possible.
It would certainly be more convenient if it was an OUTPUT parameter
rather than a result ser. If you can't change the procedure, you will
have to use INSERT EXEC.
Besides this looks funny:
CREATE TABLE [XALSEQ] (
[SEQID] [int] NOT NULL ,
[DATASET] [varchar] (3) COLLATE SQL_Danish_Pref_CP1_CI_AS NOT NULL ,
[SEQNO] [int] NOT NULL
) ON [PRIMARY]
GO
It doesn't have a primary key?
If there are no indexes on the table, this means that SQL Server will
have to take a out a table lock to give you a sequence number, and thus
no other will be able to get a sequence number simultaneously.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog wrote:
> MBS? That's some third-party software?
Microsoft Business Solution, they bought a company named Navision, which
makes applications that primarily talks flat fileish. In my case the
application uses cursors, a /lot/ of cursors. They do plan to change this,
but that's 2+ years in the future atleast.
I'm trying to insert data from the "outside" of this application, which
means that I can use all kinds of RDBMS tricks.
> It would certainly be more convenient if it was an OUTPUT parameter
> rather than a result ser. If you can't change the procedure, you will
> have to use INSERT EXEC.
I'm sure can write a new, as long as I retain the functionality. Which one
of your methods would you use then?
> It doesn't have a primary key?
> If there are no indexes on the table, this means that SQL Server will
> have to take a out a table lock to give you a sequence number, and
> thus no other will be able to get a sequence number simultaneously.
Maybe they forgot, or the application might not be able to handle such a
situation.
Necessity is the plea for every infringement of human freedom. It is
the argument of tyrants; it is the creed of slaves. -- William Pitt,
1783|||Kim Noer (kn@.nospam.dk) writes:
> I'm sure can write a new, as long as I retain the functionality. Which one
> of your methods would you use then?
OUTPUT parameter.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
The target table got these two 'must be set columns', one called DATASET, an
d
one called LXBENUMMER.
Now, when I want to insert data into this target table I need to fill those
two
columns with the new records I'm inserting. DATASET is easy as it'll always
be a
fixed value, however, LXBENUMMER must be set with a number that comes from a
stored procedure.
If I do an exec sp_xal_seqno 1, 'DAT' I get a number back, which must be put
in
LXBENUMMER with the new record.
An example-
insert tbl1
(dataset,lxbenummer,col1,col2,col3,etc)
select 'DAT',**value from stored procedure**, col1, col2, col3, etc
from tbl2
How do I go about this?
I doubt, therefore I might be.Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, data types, etc. in
your schema are. Sample data is also a good idea, along with clear
specifications. It is very hard to debug code when you do not let us
see it.
Also, you do not know that a column is not anything like a field and
that a row is not a record. After 20+ years of doing SQL and charging
a lot of money for consulting work in correctly schemas, this is a
signal that you are really screwed up.|||"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1129947794.955269.92220@.g43g2000cwa.googlegroups.com
> Also, you do not know that a column is not anything like a field and
> that a row is not a record. After 20+ years of doing SQL and charging
Well everywhere I look, row and record is the same and is used interchangeab
le.
Why should I think different? I don't see where I wrote field and compared i
t
with a column; but well you do know better.
> a lot of money for consulting work in correctly schemas, this is a
> signal that you are really screwed up.
Dude, you need to take a break from time to time, instead of throwing dirt a
t
those to aren't "worthy" compared to you. I'd see your point better if you h
ad
kept it nicer.
I'm screwed up if I write nutty SQL? Man, if you think that, you /seriously/
need to take a break from anything relating to computers.
Anyway, I shall post again when I have a DDL ready.
--
I doubt, therefore I might be.|||Kim Noer (kn@.nospam.dk) writes:
> The target table got these two 'must be set columns', one called
> DATASET, and one called LXBENUMMER.
> Now, when I want to insert data into this target table I need to fill
> those two columns with the new records I'm inserting. DATASET is easy as
> it'll always be a fixed value, however, LXBENUMMER must be set with a
> number that comes from a stored procedure.
> If I do an exec sp_xal_seqno 1, 'DAT' I get a number back, which must be
> put in LXBENUMMER with the new record.
General comment: don't use sp_ as the leading charcters in the name of
your objects. This prefix is reserved for SQL Server, and SQL Server will
first look in master for these objects.
> An example-
> insert tbl1
> (dataset,lxbenummer,col1,col2,col3,etc)
> select 'DAT',**value from stored procedure**, col1, col2, col3, etc
> from tbl2
> How do I go about this?
There are number of options, of which some requires you to change
the procedure. I happen to have an article about this on my web site:
http://www.sommarskog.se/share_data.html.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||From your attitude i'd be suprised if anybody outside of education has hired
you in the past couple of years!
You need to bring your skills up-to-date with what business wants now, not
15 years ago.
Times have significantly changed and you seem to have been left behind.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1129947794.955269.92220@.g43g2000cwa.googlegroups.com...
> Please post DDL, so that people do not have to guess what the keys,
> constraints, Declarative Referential Integrity, data types, etc. in
> your schema are. Sample data is also a good idea, along with clear
> specifications. It is very hard to debug code when you do not let us
> see it.
> Also, you do not know that a column is not anything like a field and
> that a row is not a record. After 20+ years of doing SQL and charging
> a lot of money for consulting work in correctly schemas, this is a
> signal that you are really screwed up.
>|||"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1129947794.955269.92220@.g43g2000cwa.googlegroups.com
> Please post DDL, so that people do not have to guess what the keys,
> constraints, Declarative Referential Integrity, data types, etc. in
> your schema are. Sample data is also a good idea, along with clear
> specifications. It is very hard to debug code when you do not let us
> see it.
CREATE TABLE [tbl1] (
[DATASET] [varchar] (3) COLLATE SQL_Danish_Pref_CP1_CI_AS NOT NULL ,
[LXBENUMMER] [int] NOT NULL ,
[col1] [varchar] (30) COLLATE SQL_Danish_Pref_CP1_CI_AS NOT NULL
) ON [PRIMARY]
GO
CREATE TABLE [XALSEQ] (
[SEQID] [int] NOT NULL ,
[DATASET] [varchar] (3) COLLATE SQL_Danish_Pref_CP1_CI_AS NOT NULL ,
[SEQNO] [int] NOT NULL
) ON [PRIMARY]
GO
INSERT INTO XALSEQ
VALUES (0,'DAT',1000)
GO
INSERT INTO tbl1
VALUES ('DAT',1000,'somerandomtext')
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE PROCEDURE sp_xal_seqno @.increment INT, @.dataset CHAR(3) AS
BEGIN TRAN
UPDATE XALSEQ SET SEQNO = SEQNO + @.increment
WHERE DATASET = @.dataset AND SEQID = 0
SELECT SEQNO - @.increment FROM XALSEQ
WHERE DATASET = @.dataset AND SEQID = 0
COMMIT TRAN
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
I doubt, therefore I might be.|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns96F7D40BB5DE7Yazorman@.127.0.0.1
> General comment: don't use sp_ as the leading charcters in the name of
> your objects. This prefix is reserved for SQL Server, and SQL Server
> will first look in master for these objects.
Aye, I name all those I create differently, but alas, I did not get to chose
the
name of the stored procedure, this one comes from MBS themself.
> There are number of options, of which some requires you to change
> the procedure. I happen to have an article about this on my web site:
> http://www.sommarskog.se/share_data.html.
In my second post to Celko, I've included the structure of the tables, the S
P
and tiny amount of sample data, if that helps point me in the correct direct
ion
(I'm going to read up on your article anyway though).
Basically, the whole purpose is to make sure that every single row (or is it
record?) get their very own unique number. It would be exceedingly lovely if
any
solution to this particular problem could be made generic if possible.
Thanks in advance.
--
I doubt, therefore I might be.|||Kim Noer (kn@.nospam.dk) writes:
> Aye, I name all those I create differently, but alas, I did not get to
> chose the name of the stored procedure, this one comes from MBS
> themself.
MBS? That's some third-party software?
> Basically, the whole purpose is to make sure that every single row (or
> is it record?) get their very own unique number. It would be exceedingly
> lovely if any solution to this particular problem could be made generic
> if possible.
It would certainly be more convenient if it was an OUTPUT parameter
rather than a result ser. If you can't change the procedure, you will
have to use INSERT EXEC.
Besides this looks funny:
CREATE TABLE [XALSEQ] (
[SEQID] [int] NOT NULL ,
[DATASET] [varchar] (3) COLLATE SQL_Danish_Pref_CP1_CI_AS NOT NULL ,
[SEQNO] [int] NOT NULL
) ON [PRIMARY]
GO
It doesn't have a primary key?
If there are no indexes on the table, this means that SQL Server will
have to take a out a table lock to give you a sequence number, and thus
no other will be able to get a sequence number simultaneously.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog wrote:
> MBS? That's some third-party software?
Microsoft Business Solution, they bought a company named Navision, which
makes applications that primarily talks flat fileish. In my case the
application uses cursors, a /lot/ of cursors. They do plan to change this,
but that's 2+ years in the future atleast.
I'm trying to insert data from the "outside" of this application, which
means that I can use all kinds of RDBMS tricks.
> It would certainly be more convenient if it was an OUTPUT parameter
> rather than a result ser. If you can't change the procedure, you will
> have to use INSERT EXEC.
I'm sure can write a new, as long as I retain the functionality. Which one
of your methods would you use then?
> It doesn't have a primary key?
> If there are no indexes on the table, this means that SQL Server will
> have to take a out a table lock to give you a sequence number, and
> thus no other will be able to get a sequence number simultaneously.
Maybe they forgot, or the application might not be able to handle such a
situation.
Necessity is the plea for every infringement of human freedom. It is
the argument of tyrants; it is the creed of slaves. -- William Pitt,
1783|||Kim Noer (kn@.nospam.dk) writes:
> I'm sure can write a new, as long as I retain the functionality. Which one
> of your methods would you use then?
OUTPUT parameter.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Inserting only time (09:00:00) into SQL server
I'm having problems inserting times into my SQL backend through my VB app
I have a access front end that I am wanting to recreate in VB but when i
execute my SQL insert statement instead of 09:00:00 showing in the field,
01/01/1900 09:00:00 or similar shows, i can insert only a date into the date
field 01/01/2005 and it stores how i want. but i cant seperately store the
time the field is set to datetime.
any one have any ideas, also I am getting an error with the SQL statement i
dont think it likes the ' around the time variable but errors if it isnt
there. If i paste the SQL statement into query analyzer with the ' it runs
no problem.
TIA
some sample code is below
strSQL = "INSERT INTO Appointment (Date_Of_Travel, Time_Of_Appointment,
House, Postcode, CMS_Ref, Agent_ID) VALUES ('" & _
DateTrav & "', '" & txtTime & "', '" & txtHouse & "', '" & txtPCode & "', '"
& txtCMS & "', '" & txtAgentID & "');"
Cmd.CommandText = strSQL
Cmd.Executehi steven,
u cannot store the time alone in the datetime obj. it has to be with the
date part. since u have not specified the date , sql server has picked up th
e
default date : 1/1/1900.
optionally u can think of adding the time along with some date and then
ignore the date part , when ever u operate on this field.
anu
"steven scaife" wrote:
> I'm having problems inserting times into my SQL backend through my VB app
> I have a access front end that I am wanting to recreate in VB but when i
> execute my SQL insert statement instead of 09:00:00 showing in the field,
> 01/01/1900 09:00:00 or similar shows, i can insert only a date into the da
te
> field 01/01/2005 and it stores how i want. but i cant seperately store th
e
> time the field is set to datetime.
> any one have any ideas, also I am getting an error with the SQL statement
i
> dont think it likes the ' around the time variable but errors if it isnt
> there. If i paste the SQL statement into query analyzer with the ' it run
s
> no problem.
> TIA
> some sample code is below
> strSQL = "INSERT INTO Appointment (Date_Of_Travel, Time_Of_Appointment,
> House, Postcode, CMS_Ref, Agent_ID) VALUES ('" & _
> DateTrav & "', '" & txtTime & "', '" & txtHouse & "', '" & txtPCode & "',
'"
> & txtCMS & "', '" & txtAgentID & "');"
> Cmd.CommandText = strSQL
> Cmd.Execute
>|||SQL Server doesn't have a TIME datatype. DATETIME always stores both
date and time. Looking at your INSERT statement it seems you have
separate columns for date and time. That doesn't seem like a good idea.
Why use one column instead of two? You can easily separate the date and
time elements when you query the table, or just format it differently
to show only date or only time on screen.
Don't build and execute dynamic SQL strings from user input. It exposes
you to SQL Injection vulnerabilities (Google for it if you don't know).
Data-access code in your client app also increases database maintenance
problems because it forces you to change your application when you make
schema changes. All data access should usually be performed through
parameterized stored procedures.
David Portas
SQL Server MVP
--|||Hi
I'd create stored procedure that accept few parameters
declare @.dt DATETIME,@.t CHAR(5)
SET @.dt=GETDATE()
SET @.t='09:00'
CREATE TABLE #Test
(
col DATETIME
)
INSERT INTO #Test SELECT GETDATE()
INSERT INTO #Test SELECT CAST(CONVERT(CHAR(10),@.dt,112)+@.t AS DATETIME)
SELECT * FROM #Test
"steven scaife" <stevenscaife@.discussions.microsoft.com> wrote in message
news:A60949B8-0E18-46D0-9937-A01761A3FB8D@.microsoft.com...
> I'm having problems inserting times into my SQL backend through my VB app
> I have a access front end that I am wanting to recreate in VB but when i
> execute my SQL insert statement instead of 09:00:00 showing in the field,
> 01/01/1900 09:00:00 or similar shows, i can insert only a date into the
date
> field 01/01/2005 and it stores how i want. but i cant seperately store
the
> time the field is set to datetime.
> any one have any ideas, also I am getting an error with the SQL statement
i
> dont think it likes the ' around the time variable but errors if it isnt
> there. If i paste the SQL statement into query analyzer with the ' it
runs
> no problem.
> TIA
> some sample code is below
> strSQL = "INSERT INTO Appointment (Date_Of_Travel, Time_Of_Appointment,
> House, Postcode, CMS_Ref, Agent_ID) VALUES ('" & _
> DateTrav & "', '" & txtTime & "', '" & txtHouse & "', '" & txtPCode & "',
'"
> & txtCMS & "', '" & txtAgentID & "');"
> Cmd.CommandText = strSQL
> Cmd.Execute
>
I have a access front end that I am wanting to recreate in VB but when i
execute my SQL insert statement instead of 09:00:00 showing in the field,
01/01/1900 09:00:00 or similar shows, i can insert only a date into the date
field 01/01/2005 and it stores how i want. but i cant seperately store the
time the field is set to datetime.
any one have any ideas, also I am getting an error with the SQL statement i
dont think it likes the ' around the time variable but errors if it isnt
there. If i paste the SQL statement into query analyzer with the ' it runs
no problem.
TIA
some sample code is below
strSQL = "INSERT INTO Appointment (Date_Of_Travel, Time_Of_Appointment,
House, Postcode, CMS_Ref, Agent_ID) VALUES ('" & _
DateTrav & "', '" & txtTime & "', '" & txtHouse & "', '" & txtPCode & "', '"
& txtCMS & "', '" & txtAgentID & "');"
Cmd.CommandText = strSQL
Cmd.Executehi steven,
u cannot store the time alone in the datetime obj. it has to be with the
date part. since u have not specified the date , sql server has picked up th
e
default date : 1/1/1900.
optionally u can think of adding the time along with some date and then
ignore the date part , when ever u operate on this field.
anu
"steven scaife" wrote:
> I'm having problems inserting times into my SQL backend through my VB app
> I have a access front end that I am wanting to recreate in VB but when i
> execute my SQL insert statement instead of 09:00:00 showing in the field,
> 01/01/1900 09:00:00 or similar shows, i can insert only a date into the da
te
> field 01/01/2005 and it stores how i want. but i cant seperately store th
e
> time the field is set to datetime.
> any one have any ideas, also I am getting an error with the SQL statement
i
> dont think it likes the ' around the time variable but errors if it isnt
> there. If i paste the SQL statement into query analyzer with the ' it run
s
> no problem.
> TIA
> some sample code is below
> strSQL = "INSERT INTO Appointment (Date_Of_Travel, Time_Of_Appointment,
> House, Postcode, CMS_Ref, Agent_ID) VALUES ('" & _
> DateTrav & "', '" & txtTime & "', '" & txtHouse & "', '" & txtPCode & "',
'"
> & txtCMS & "', '" & txtAgentID & "');"
> Cmd.CommandText = strSQL
> Cmd.Execute
>|||SQL Server doesn't have a TIME datatype. DATETIME always stores both
date and time. Looking at your INSERT statement it seems you have
separate columns for date and time. That doesn't seem like a good idea.
Why use one column instead of two? You can easily separate the date and
time elements when you query the table, or just format it differently
to show only date or only time on screen.
Don't build and execute dynamic SQL strings from user input. It exposes
you to SQL Injection vulnerabilities (Google for it if you don't know).
Data-access code in your client app also increases database maintenance
problems because it forces you to change your application when you make
schema changes. All data access should usually be performed through
parameterized stored procedures.
David Portas
SQL Server MVP
--|||Hi
I'd create stored procedure that accept few parameters
declare @.dt DATETIME,@.t CHAR(5)
SET @.dt=GETDATE()
SET @.t='09:00'
CREATE TABLE #Test
(
col DATETIME
)
INSERT INTO #Test SELECT GETDATE()
INSERT INTO #Test SELECT CAST(CONVERT(CHAR(10),@.dt,112)+@.t AS DATETIME)
SELECT * FROM #Test
"steven scaife" <stevenscaife@.discussions.microsoft.com> wrote in message
news:A60949B8-0E18-46D0-9937-A01761A3FB8D@.microsoft.com...
> I'm having problems inserting times into my SQL backend through my VB app
> I have a access front end that I am wanting to recreate in VB but when i
> execute my SQL insert statement instead of 09:00:00 showing in the field,
> 01/01/1900 09:00:00 or similar shows, i can insert only a date into the
date
> field 01/01/2005 and it stores how i want. but i cant seperately store
the
> time the field is set to datetime.
> any one have any ideas, also I am getting an error with the SQL statement
i
> dont think it likes the ' around the time variable but errors if it isnt
> there. If i paste the SQL statement into query analyzer with the ' it
runs
> no problem.
> TIA
> some sample code is below
> strSQL = "INSERT INTO Appointment (Date_Of_Travel, Time_Of_Appointment,
> House, Postcode, CMS_Ref, Agent_ID) VALUES ('" & _
> DateTrav & "', '" & txtTime & "', '" & txtHouse & "', '" & txtPCode & "',
'"
> & txtCMS & "', '" & txtAgentID & "');"
> Cmd.CommandText = strSQL
> Cmd.Execute
>
Subscribe to:
Posts (Atom)