Hi,
right now we use the SQL 2000 Server Developer Edition to
make tests, but we would like to buy SQL 2000 Server. Does
the SQL 2000 Server STandard Edition include all the
WIZARDS that are also included with the Developer or
Enterprise Edition (when I highlight a database in
Enterprise Manager, go to "Tools" and "Wizards").
Can anyone help?
Thanks for reply.
BodoAll the wizards are included in Standard Edition as well. The differences
between Standard and Enterprise Edition are mostly in the high-end
performance and availabilty areas, like clustered servers, indexed views
etc.
For an overview see the topic "Features Supported by the Editions of SQL
Server 2000" in Books Online.
--
Jacco Schalkwijk MCDBA, MCSD, MCSE
Database Administrator
Eurostop Ltd.
"bodo" <bodobecker@.hotmail.com> wrote in message
news:0b6501c36d6b$b90a15c0$a601280a@.phx.gbl...
> Hi,
> right now we use the SQL 2000 Server Developer Edition to
> make tests, but we would like to buy SQL 2000 Server. Does
> the SQL 2000 Server STandard Edition include all the
> WIZARDS that are also included with the Developer or
> Enterprise Edition (when I highlight a database in
> Enterprise Manager, go to "Tools" and "Wizards").
> Can anyone help?
> Thanks for reply.
> Bodo|||Hello Bodo !
Differences could be seen here:
http://www.microsoft.com/sql/evaluation/features/choosing.asp
HTH, Jens Süßmeyer.|||Hi Jacco,
thanks for your help!
Brgds Bodo
>--Original Message--
>All the wizards are included in Standard Edition as well.
The differences
>between Standard and Enterprise Edition are mostly in the
high-end
>performance and availabilty areas, like clustered
servers, indexed views
>etc.
>For an overview see the topic "Features Supported by the
Editions of SQL
>Server 2000" in Books Online.
>--
>Jacco Schalkwijk MCDBA, MCSD, MCSE
>Database Administrator
>Eurostop Ltd.
>
>"bodo" <bodobecker@.hotmail.com> wrote in message
>news:0b6501c36d6b$b90a15c0$a601280a@.phx.gbl...
>> Hi,
>> right now we use the SQL 2000 Server Developer Edition
to
>> make tests, but we would like to buy SQL 2000 Server.
Does
>> the SQL 2000 Server STandard Edition include all the
>> WIZARDS that are also included with the Developer or
>> Enterprise Edition (when I highlight a database in
>> Enterprise Manager, go to "Tools" and "Wizards").
>> Can anyone help?
>> Thanks for reply.
>> Bodo
>
>.
>
Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts
Tuesday, March 27, 2012
Archiving database for reporting
HI,
I have a database on sql server 2005 ent edition with about 300 000
new records every day. I must keep data in production database about
two months, but there are a lot of reporting activities which are
interrupting normal functioning of production server and there is also
requirement to query historical data(about 1 year) with reports. I
must add new data to the archive database every day. Additionally two
months old data in the production database can change (delete, update)
and that also must be reflected in archive database. So basically I
must insert new data, update changed date and delete deleted data from
production database into archive database but also keep about 1 year
of data in archive database. Then I can separately optimize archive
database for reporting. What is the best way to satisfy all that
requirements. I am thinking about SSIS.SSIS will work. You could also consider a small trigger on the main table
that will put the key values into a holding table when
inserts/updates/deletes occur so you can very quickly make the necessary
changes to the historical records when <2mth old data is modified.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"OgnjenT" <OgnjenT@.gmail.com> wrote in message
news:3f74847e-97c1-4a69-bbb8-17813ccc2cbb@.u10g2000prn.googlegroups.com...
> HI,
> I have a database on sql server 2005 ent edition with about 300 000
> new records every day. I must keep data in production database about
> two months, but there are a lot of reporting activities which are
> interrupting normal functioning of production server and there is also
> requirement to query historical data(about 1 year) with reports. I
> must add new data to the archive database every day. Additionally two
> months old data in the production database can change (delete, update)
> and that also must be reflected in archive database. So basically I
> must insert new data, update changed date and delete deleted data from
> production database into archive database but also keep about 1 year
> of data in archive database. Then I can separately optimize archive
> database for reporting. What is the best way to satisfy all that
> requirements. I am thinking about SSIS.|||Hi
SSIS can be a good choice.
Also
>also keep about 1 year
> of data in archive database.
DELETE FROM tbl WHERE dt <DATEADD(Year,-1,GETDATE())
> I must keep data in production database about
> two months, b
Create a job and schedule it on day period
I must keep data in production database about
INSERT INTO arch. tbl (..) SELECT ... FROM prod WHERE dt >='19000101' AND
dt<=DATEADD(month,-2,GETDATE())
>Additionally two
> months old data in the production database can change (delete, update)
> and that also must be reflected in archive database.
Here, I'd suggest you to create a trigger or (take a look at OUTPUT clause)
and flag or whatever modified data
"OgnjenT" <OgnjenT@.gmail.com> wrote in message
news:3f74847e-97c1-4a69-bbb8-17813ccc2cbb@.u10g2000prn.googlegroups.com...
> HI,
> I have a database on sql server 2005 ent edition with about 300 000
> new records every day. I must keep data in production database about
> two months, but there are a lot of reporting activities which are
> interrupting normal functioning of production server and there is also
> requirement to query historical data(about 1 year) with reports. I
> must add new data to the archive database every day. Additionally two
> months old data in the production database can change (delete, update)
> and that also must be reflected in archive database. So basically I
> must insert new data, update changed date and delete deleted data from
> production database into archive database but also keep about 1 year
> of data in archive database. Then I can separately optimize archive
> database for reporting. What is the best way to satisfy all that
> requirements. I am thinking about SSIS.|||On Feb 7, 9:03=A0am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
> SSIS can be a good choice.
> Also
> >also keep about 1 year
> > of data in archive database.
> DELETE FROM tbl WHERE dt <DATEADD(Year,-1,GETDATE())
> > I must keep data in production database about
> > two months, b
> =A0 =A0 Create a job and schedule it on day period
> =A0I must keep data in production database about
> INSERT INTO arch. tbl (..) SELECT ... FROM prod WHERE dt >=3D'19000101' AN=D
> dt<=3DDATEADD(month,-2,GETDATE())
> >Additionally two
> > months old data in the production database can change (delete, update)
> > and that also must be reflected in archive database.
> Here, I'd suggest =A0you to create a trigger or (take a look at OUTPUT cla=use)
> and flag or whatever modified data
> "OgnjenT" <Ognj...@.gmail.com> wrote in message
> news:3f74847e-97c1-4a69-bbb8-17813ccc2cbb@.u10g2000prn.googlegroups.com...
>
> > HI,
> > I have a database on sql server 2005 ent edition with about 300 000
> > new records every day. I must keep data in production database about
> > two months, but there are a lot of reporting activities which are
> > interrupting normal functioning of production server and there is also
> > requirement to query historical data(about 1 year) with reports. I
> > must add new data to the archive database every day. Additionally two
> > months old data in the production database can change (delete, update)
> > and that also must be reflected in archive database. So basically I
> > must insert new data, update changed date and delete deleted data from
> > production database into archive database but also keep about 1 year
> > of data in archive database. Then I can separately optimize archive
> > database for reporting. What is the best way to satisfy all that
> > requirements. I am thinking about SSIS.- Hide quoted text -
> - Show quoted text -
Problem with triger is when I clean data older then two month it will
delete data in archive database too. Also I must then put the triger
on the other tables because of the referential integrity in the
archive database.
>INSERT INTO arch. tbl (..) SELECT ... FROM prod WHERE dt >=3D'19000101' AND=
>dt<=3DDATEADD(month,-2,GETDATE())
I can't do that because I must have to synchronize production and
archive database every day because every night I mast have a dozen of
reports.
I decided to have archive database because of different way of queries
for normal processing and for reporting and I don't wont reporting
have so mutch influence on normaln work. So it is not only archiving
data but creating separate database for reporting so I can put some
more indexes, indexed views and in the same time my insert and updates
will still be fast in the production database. Also production server
doesn't have to hold data older than two months so it is better to
clean it so my queries woold be faster.
Is it maybe ok to delete data older than two months from archive
database every night and insert that data from production database. It
seems to me that it will be faster than check every row in production
database and then update archive database if row is updated, delete if
deleted. The esiest of course is to insert new rows.
Maybe before that bulk delete and insert it wood be smart to drop all
indexes, indexed views and constraint and recreate it after. But I
must do all that for about 15 minutes.
I have a database on sql server 2005 ent edition with about 300 000
new records every day. I must keep data in production database about
two months, but there are a lot of reporting activities which are
interrupting normal functioning of production server and there is also
requirement to query historical data(about 1 year) with reports. I
must add new data to the archive database every day. Additionally two
months old data in the production database can change (delete, update)
and that also must be reflected in archive database. So basically I
must insert new data, update changed date and delete deleted data from
production database into archive database but also keep about 1 year
of data in archive database. Then I can separately optimize archive
database for reporting. What is the best way to satisfy all that
requirements. I am thinking about SSIS.SSIS will work. You could also consider a small trigger on the main table
that will put the key values into a holding table when
inserts/updates/deletes occur so you can very quickly make the necessary
changes to the historical records when <2mth old data is modified.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"OgnjenT" <OgnjenT@.gmail.com> wrote in message
news:3f74847e-97c1-4a69-bbb8-17813ccc2cbb@.u10g2000prn.googlegroups.com...
> HI,
> I have a database on sql server 2005 ent edition with about 300 000
> new records every day. I must keep data in production database about
> two months, but there are a lot of reporting activities which are
> interrupting normal functioning of production server and there is also
> requirement to query historical data(about 1 year) with reports. I
> must add new data to the archive database every day. Additionally two
> months old data in the production database can change (delete, update)
> and that also must be reflected in archive database. So basically I
> must insert new data, update changed date and delete deleted data from
> production database into archive database but also keep about 1 year
> of data in archive database. Then I can separately optimize archive
> database for reporting. What is the best way to satisfy all that
> requirements. I am thinking about SSIS.|||Hi
SSIS can be a good choice.
Also
>also keep about 1 year
> of data in archive database.
DELETE FROM tbl WHERE dt <DATEADD(Year,-1,GETDATE())
> I must keep data in production database about
> two months, b
Create a job and schedule it on day period
I must keep data in production database about
INSERT INTO arch. tbl (..) SELECT ... FROM prod WHERE dt >='19000101' AND
dt<=DATEADD(month,-2,GETDATE())
>Additionally two
> months old data in the production database can change (delete, update)
> and that also must be reflected in archive database.
Here, I'd suggest you to create a trigger or (take a look at OUTPUT clause)
and flag or whatever modified data
"OgnjenT" <OgnjenT@.gmail.com> wrote in message
news:3f74847e-97c1-4a69-bbb8-17813ccc2cbb@.u10g2000prn.googlegroups.com...
> HI,
> I have a database on sql server 2005 ent edition with about 300 000
> new records every day. I must keep data in production database about
> two months, but there are a lot of reporting activities which are
> interrupting normal functioning of production server and there is also
> requirement to query historical data(about 1 year) with reports. I
> must add new data to the archive database every day. Additionally two
> months old data in the production database can change (delete, update)
> and that also must be reflected in archive database. So basically I
> must insert new data, update changed date and delete deleted data from
> production database into archive database but also keep about 1 year
> of data in archive database. Then I can separately optimize archive
> database for reporting. What is the best way to satisfy all that
> requirements. I am thinking about SSIS.|||On Feb 7, 9:03=A0am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
> SSIS can be a good choice.
> Also
> >also keep about 1 year
> > of data in archive database.
> DELETE FROM tbl WHERE dt <DATEADD(Year,-1,GETDATE())
> > I must keep data in production database about
> > two months, b
> =A0 =A0 Create a job and schedule it on day period
> =A0I must keep data in production database about
> INSERT INTO arch. tbl (..) SELECT ... FROM prod WHERE dt >=3D'19000101' AN=D
> dt<=3DDATEADD(month,-2,GETDATE())
> >Additionally two
> > months old data in the production database can change (delete, update)
> > and that also must be reflected in archive database.
> Here, I'd suggest =A0you to create a trigger or (take a look at OUTPUT cla=use)
> and flag or whatever modified data
> "OgnjenT" <Ognj...@.gmail.com> wrote in message
> news:3f74847e-97c1-4a69-bbb8-17813ccc2cbb@.u10g2000prn.googlegroups.com...
>
> > HI,
> > I have a database on sql server 2005 ent edition with about 300 000
> > new records every day. I must keep data in production database about
> > two months, but there are a lot of reporting activities which are
> > interrupting normal functioning of production server and there is also
> > requirement to query historical data(about 1 year) with reports. I
> > must add new data to the archive database every day. Additionally two
> > months old data in the production database can change (delete, update)
> > and that also must be reflected in archive database. So basically I
> > must insert new data, update changed date and delete deleted data from
> > production database into archive database but also keep about 1 year
> > of data in archive database. Then I can separately optimize archive
> > database for reporting. What is the best way to satisfy all that
> > requirements. I am thinking about SSIS.- Hide quoted text -
> - Show quoted text -
Problem with triger is when I clean data older then two month it will
delete data in archive database too. Also I must then put the triger
on the other tables because of the referential integrity in the
archive database.
>INSERT INTO arch. tbl (..) SELECT ... FROM prod WHERE dt >=3D'19000101' AND=
>dt<=3DDATEADD(month,-2,GETDATE())
I can't do that because I must have to synchronize production and
archive database every day because every night I mast have a dozen of
reports.
I decided to have archive database because of different way of queries
for normal processing and for reporting and I don't wont reporting
have so mutch influence on normaln work. So it is not only archiving
data but creating separate database for reporting so I can put some
more indexes, indexed views and in the same time my insert and updates
will still be fast in the production database. Also production server
doesn't have to hold data older than two months so it is better to
clean it so my queries woold be faster.
Is it maybe ok to delete data older than two months from archive
database every night and insert that data from production database. It
seems to me that it will be faster than check every row in production
database and then update archive database if row is updated, delete if
deleted. The esiest of course is to insert new rows.
Maybe before that bulk delete and insert it wood be smart to drop all
indexes, indexed views and constraint and recreate it after. But I
must do all that for about 15 minutes.
Thursday, March 22, 2012
April 2005 CTP On Virtual PC 2004
Hello, I have installed the SQL Server 2005 april CTP on a Virtual PC running Win2003 standard edition. The Management Studio appears to be corrupted and it says that "no such interface supported". This happens only on the VPC. On the main workstation running XP the Management Studio is fine.
The same issue arises with the ISO i downloaded from MSDN as well as a copy of the DVD given out at a MS developer event in Reading, U.K recently.
Does this ring a bell with anyone? has this surfaced for anyone else?
TIA
BenjyFor a faster response I suggest you post this to the SQL Server Tools General forum.
Dan
Monday, March 19, 2012
Applying SP2 for SQL 2005 Enterprise Edition (on 64 bit windows)
Hello,
I'm experiencing some issues with applying SP2. I'm getting a failure for the database engine (on two instances that have been installed on a server). I've noticed in the forum that a few others have had some issues in this area as well. The slightly strange thing is that if I check the version of SQL Server on each instance it is telling me that SP2 has been installed:
9.00.3042.00 SP2 Enterprise Edition (64-bit)
So, the logs tell me I have a failed upgrade, but SQL is telling me it has been upgraded.
Any help would be appreciated.
--
from SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Fri Jun 22 11:52:44 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (1C:98) [11:52:44:201]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:201]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 11:52:44: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
the end of that file has the following information:
MSI (s) (1C:98) [11:52:44:701]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Service Pack 2 for SQL Server Database Services 2005 (64-bit) ENU (KB921896)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 1729
MSI (s) (1C:98) [11:52:44:701]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed.
MSI (s) (1C:98) [11:52:44:748]: Attempting to delete file C:\WINDOWS\Installer\3cda1ca.msp
MSI (s) (1C:98) [11:52:44:794]: Cleaning up uninstalled install packages, if any exist
MSI (s) (1C:98) [11:52:44:794]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\3cda1ca.msp'
MSI (s) (1C:98) [11:52:44:794]: MainEngineThread is returning 1603
MSI (s) (1C:94) [11:52:44:794]: Destroying RemoteAPI object.
MSI (s) (1C:BC) [11:52:44:794]: Custom Action Manager thread ending.
=== Logging stopped: 22/06/2007 11:52:44 ===
MSI (c) (60:AC) [11:52:44:841]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (60:AC) [11:52:44:841]: MainEngineThread is returning 1603
=== Verbose logging stopped: 22/06/2007 11:52:44 ===
Did you had a chance to look at
http://support.microsoft.com/default.aspx/kb/933945|||I have had a look at that but wasn't certain that it applied as it was for an earlier fix. I am thinking about trying to install the critical update for SP2 to see if that helps (http://support.microsoft.com/?kbid=934458). I haven't tried that, but am about to. If that works I will update this thread.
From Summary.txt from existing SP2 installation attempt:
-
Product : Database Services (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : Database Services (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
...and at the end of the file:
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29537
|||I tried applying the critical update for SP2 (http://support.microsoft.com/?kbid=934458).
I basically got very, very similar symptons to what I expereienced when installing SP2.
The logs tell me that the process was not successful for the database engine(s) and I am still getting different error messages per instance. Some logs are included:
-
Summary.txt
-
Product Installation Status
Product : SQL Server Database Services 2005 (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : SQL Server Database Services 2005 (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
-
SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
-
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='1802' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:43:40 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1802' GetLastError='0'>
MSI (s) (84:90) [16:43:40:476]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:476]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:43:40: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:43:40: INSTALL. Return value 3.
--
SQL9_Hotfix_KB934458_sqlrun_sql.msp_0.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:45:13 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (84:28) [16:45:13:713]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:713]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:45:13: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:45:13: INSTALL. Return value 3.
--
If I then check what version files are at, sqlservr.exe is at version 2005.90.3054.0 and Microsoft.SqlServer.MaintenancePlanTasks.dll is at version 9.0.3054.0.
select @.@.version is returning "Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)"
So does this mean that the logs are not correct and SP2 and the updates have been successfully applied?
|||Could you check the version of Binaries ? sqlservr.exe|||Associated Hotfix Build: 3159
File version: 2005.090.3054.00
Product Version: 9.00.3054.00
This is for both instances. So, it looks as though the database engine got upgraded successfully - but the logs are telling me otherwise!
|||Exactly.
Applying SP2 for SQL 2005 Enterprise Edition (on 64 bit windows)
Hello,
I'm experiencing some issues with applying SP2. I'm getting a failure for the database engine (on two instances that have been installed on a server). I've noticed in the forum that a few others have had some issues in this area as well. The slightly strange thing is that if I check the version of SQL Server on each instance it is telling me that SP2 has been installed:
9.00.3042.00 SP2 Enterprise Edition (64-bit)
So, the logs tell me I have a failed upgrade, but SQL is telling me it has been upgraded.
Any help would be appreciated.
--
from SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Fri Jun 22 11:52:44 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (1C:98) [11:52:44:201]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:201]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 11:52:44: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
the end of that file has the following information:
MSI (s) (1C:98) [11:52:44:701]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Service Pack 2 for SQL Server Database Services 2005 (64-bit) ENU (KB921896)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 1729
MSI (s) (1C:98) [11:52:44:701]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed.
MSI (s) (1C:98) [11:52:44:748]: Attempting to delete file C:\WINDOWS\Installer\3cda1ca.msp
MSI (s) (1C:98) [11:52:44:794]: Cleaning up uninstalled install packages, if any exist
MSI (s) (1C:98) [11:52:44:794]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\3cda1ca.msp'
MSI (s) (1C:98) [11:52:44:794]: MainEngineThread is returning 1603
MSI (s) (1C:94) [11:52:44:794]: Destroying RemoteAPI object.
MSI (s) (1C:BC) [11:52:44:794]: Custom Action Manager thread ending.
=== Logging stopped: 22/06/2007 11:52:44 ===
MSI (c) (60:AC) [11:52:44:841]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (60:AC) [11:52:44:841]: MainEngineThread is returning 1603
=== Verbose logging stopped: 22/06/2007 11:52:44 ===
Did you had a chance to look at
http://support.microsoft.com/default.aspx/kb/933945|||I have had a look at that but wasn't certain that it applied as it was for an earlier fix. I am thinking about trying to install the critical update for SP2 to see if that helps (http://support.microsoft.com/?kbid=934458). I haven't tried that, but am about to. If that works I will update this thread.
From Summary.txt from existing SP2 installation attempt:
-
Product : Database Services (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : Database Services (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
...and at the end of the file:
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29537
|||I tried applying the critical update for SP2 (http://support.microsoft.com/?kbid=934458).
I basically got very, very similar symptons to what I expereienced when installing SP2.
The logs tell me that the process was not successful for the database engine(s) and I am still getting different error messages per instance. Some logs are included:
-
Summary.txt
-
Product Installation Status
Product : SQL Server Database Services 2005 (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : SQL Server Database Services 2005 (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
-
SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
-
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='1802' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:43:40 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1802' GetLastError='0'>
MSI (s) (84:90) [16:43:40:476]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:476]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:43:40: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:43:40: INSTALL. Return value 3.
--
SQL9_Hotfix_KB934458_sqlrun_sql.msp_0.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:45:13 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (84:28) [16:45:13:713]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:713]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:45:13: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:45:13: INSTALL. Return value 3.
--
If I then check what version files are at, sqlservr.exe is at version 2005.90.3054.0 and Microsoft.SqlServer.MaintenancePlanTasks.dll is at version 9.0.3054.0.
select @.@.version is returning "Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)"
So does this mean that the logs are not correct and SP2 and the updates have been successfully applied?
|||Could you check the version of Binaries ? sqlservr.exe|||Associated Hotfix Build: 3159
File version: 2005.090.3054.00
Product Version: 9.00.3054.00
This is for both instances. So, it looks as though the database engine got upgraded successfully - but the logs are telling me otherwise!
|||Exactly.
Thursday, March 8, 2012
application_role
I am using SQL Server 2005 Enterprise Edition. I am a little confused on
setting up a Application role. Where do I make users a member of the role?
Is there a good explaination of this somewhere."Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:%23$WW46i%23HHA.600@.TK2MSFTNGP05.phx.gbl...
>I am using SQL Server 2005 Enterprise Edition. I am a little confused on
>setting up a Application role. Where do I make users a member of the role?
>Is there a good explaination of this somewhere.
>
You don't add users to app roles. App roles are intended as a way of
identifying an application rather than a user.
http://msdn2.microsoft.com/en-us/library/ms190998.aspx
--
David Portas|||Users don't belong to application roles. The application connects to the
database then executes the sp_setapprole procedure to get permissions.
Check this link out...
http://msdn2.microsoft.com/en-us/library/ms190998.aspx
Geoff Chovaz
MCTS: SQL Server 2005
MCITP: Database Administrator
MCITP: Database Developer
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:%23$WW46i%23HHA.600@.TK2MSFTNGP05.phx.gbl...
>I am using SQL Server 2005 Enterprise Edition. I am a little confused on
>setting up a Application role. Where do I make users a member of the role?
>Is there a good explaination of this somewhere.
>|||In SQLS 2005 there are better alternatives, which are explained in
Erland Sommarskog's excellent paper, Giving Permissions through Stored
Procedures, http://www.sommarskog.se/grantperm.html.
-mary
On Tue, 18 Sep 2007 14:59:18 -0500, "Tom Reis" <reistom@.cdnet.cod.edu>
wrote:
>I am using SQL Server 2005 Enterprise Edition. I am a little confused on
>setting up a Application role. Where do I make users a member of the role?
>Is there a good explaination of this somewhere.
>
setting up a Application role. Where do I make users a member of the role?
Is there a good explaination of this somewhere."Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:%23$WW46i%23HHA.600@.TK2MSFTNGP05.phx.gbl...
>I am using SQL Server 2005 Enterprise Edition. I am a little confused on
>setting up a Application role. Where do I make users a member of the role?
>Is there a good explaination of this somewhere.
>
You don't add users to app roles. App roles are intended as a way of
identifying an application rather than a user.
http://msdn2.microsoft.com/en-us/library/ms190998.aspx
--
David Portas|||Users don't belong to application roles. The application connects to the
database then executes the sp_setapprole procedure to get permissions.
Check this link out...
http://msdn2.microsoft.com/en-us/library/ms190998.aspx
Geoff Chovaz
MCTS: SQL Server 2005
MCITP: Database Administrator
MCITP: Database Developer
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:%23$WW46i%23HHA.600@.TK2MSFTNGP05.phx.gbl...
>I am using SQL Server 2005 Enterprise Edition. I am a little confused on
>setting up a Application role. Where do I make users a member of the role?
>Is there a good explaination of this somewhere.
>|||In SQLS 2005 there are better alternatives, which are explained in
Erland Sommarskog's excellent paper, Giving Permissions through Stored
Procedures, http://www.sommarskog.se/grantperm.html.
-mary
On Tue, 18 Sep 2007 14:59:18 -0500, "Tom Reis" <reistom@.cdnet.cod.edu>
wrote:
>I am using SQL Server 2005 Enterprise Edition. I am a little confused on
>setting up a Application role. Where do I make users a member of the role?
>Is there a good explaination of this somewhere.
>
Wednesday, March 7, 2012
Application Role and SQL Express (2005)
Hello,
Can I confirm whether pooling=false in the connection string is still required for SQL Server 2005 (Express Edition)?
Various google searches say pooling has to be turned off for SQL Server 2000, but I was just wondering whether it is still a limitation for SQL Server 2005
Thanks
John
Hi,could you please show of these link in google which point out that pooling should be disabled ? You can enable this for sure in SQL Server.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||
Hi,
Here's one
http://solidqualitylearning.com/Blogs/dejan/archive/2006/11/10/3487.aspx
I did say, "still required", but perhaps I should have made it clear that most google searches get to SQL Server 2000.
I am having problems with pooling on...
If pooling is off, I execute sp_setapprole after every time I do an Open.
I assume with pooling on, I should execute it just once, the first time I open for the same connection string.
Thanks
John
|||http://msdn2.microsoft.com/en-us/8xx3tyca(VS.80).aspx & http://databases.aspfaq.com/database/how-do-i-enable-or-disable-connection-pooling.html
FYI.
|||If you want to use pooling with application roles, then you should use sp_unsetapprole to unset the approle before returning the connection to the pool. If you cannot enforce this, then you should disable pooling when using application roles. This holds for both SQL Server and SQL Server Express.
Thanks
Laurentiu
Application Role and SQL Express (2005)
Hello,
Can I confirm whether pooling=false in the connection string is still required for SQL Server 2005 (Express Edition)?
Various google searches say pooling has to be turned off for SQL Server 2000, but I was just wondering whether it is still a limitation for SQL Server 2005
Thanks
John
Hi,could you please show of these link in google which point out that pooling should be disabled ? You can enable this for sure in SQL Server.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||
Hi,
Here's one
http://solidqualitylearning.com/Blogs/dejan/archive/2006/11/10/3487.aspx
I did say, "still required", but perhaps I should have made it clear that most google searches get to SQL Server 2000.
I am having problems with pooling on...
If pooling is off, I execute sp_setapprole after every time I do an Open.
I assume with pooling on, I should execute it just once, the first time I open for the same connection string.
Thanks
John
|||http://msdn2.microsoft.com/en-us/8xx3tyca(VS.80).aspx & http://databases.aspfaq.com/database/how-do-i-enable-or-disable-connection-pooling.html
FYI.
|||If you want to use pooling with application roles, then you should use sp_unsetapprole to unset the approle before returning the connection to the pool. If you cannot enforce this, then you should disable pooling when using application roles. This holds for both SQL Server and SQL Server Express.
Thanks
Laurentiu
Saturday, February 25, 2012
Application insist open SQL Server 2005 while the host still with SQL Server 2000
I don't know why my application on the internet try to access the SQL Server 2005, when the host still having the 2000 edition. I put the following connection string:
Data Source=##DBSERVER##;Initial Catalog=##DBNAME##;User ID=##DBUSER##;Password=##DBPASSWORD##;
Isn't everything fine with that? I created the table by host but dosen't work. I'm wondering if can I conect straight with Data Base, without register in the server, like with mdb?
This is the error that I'm getting.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Hi,
I'd like to know if the ##DBSERVER## you refer to is a correct database name with the desired SQL Server 2000. If you have multiple instance of SQL Server installed on that server, in order to access the correct one, you need to specify the instance name, if that's not the default instance, like "Data Source=DBServer\InstanceName".
For this specific error message, you can also check the following KB article for troubleshooting.
http://support.microsoft.com/kb/914277/en-us
Friday, February 24, 2012
application failed. when clicked on the sqlexpr.exe file.
Hello
I have the sql server 2005 express edition. the software stops during the setup and gives me a "failed" message. All other software of express edition are working fine. I am getting the problem only when I am dealing with sql server 2005 express edition. I made sure to deleate all the old version of sql server. uninstalled all the sql server files which were in my computer prior to download the new one. However I am still in troulbe.
As someone suggested that one should uninstale the sqlmsi file so I did that too. Still samething. Any help please......
Hi,
The event log should give you a clue what happened, eventually during the initial startup of the service.
Make sure that the SQL Server Service could start up properly. In the near püast a often and common error was that the rights provided within the SQL Server service was not priviledged to aquire the sufficient permissions for starting. So either make sure that you are using a account for starting the service which is priviledged to start as a service. Normally, Local System should be enough to start (commonly used), a (for me) better way is (if you have a domain context) is to use a domain account.
Some of the advantages are:
-There is much more security granularity over a domain account than over a system account
-If you later need network ressources you won′t get them with a Local System Account and have to switch to a domain account.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Appending Records to the Existing MS SQL EXPRESS SERVER Table.
Dear All,
I am Using MS SQL EXPRESS SERVER .I have installed all tools available to Express Edition site.
Now I have created my database on this .I have imported a table from my MS ACCESS database (Using ODBC Datasource).This table contains 10,000 records ,
Now I want to append 1 more access Table(5500 records) to the existing table having same fields.
How to do this.Can any body tell me?
Thanks and Regards
mukesh
Hi mukesh,
You can append the imported records into the existing table using SQL Server import & Export Wizard.
1.Select Your database from SQL Server Management Studio
2.Right Click on Database and go to the Task->Import Data menu Item
3. SQL Server Import & Export Wizard will be open., choose ur data source. as MicrosoftAccess, and select the MDB file
4.Press Next to Move onChoose a Destination Page, and select your Database Name from dropdown
5.Press Next to Move onSpecity Table Copy or QueryPage, and selectcopy data from one or more tables or viewradio button.
6. Press Next to Move onSelect Source Table and View , Select your Source Table , and Destination Table and then pressEdit button,Column Mappings dialog box will be open, chooseAppend rows to the destination tabelradion button option ( it will append the new records with existing records, in your case ur new 5500 records will be apended with existing 10,000 records )
7Press Next, and then Press Finish.Import Process will be started.
Thanks
Best Regards,
Muhammad AKhtar Shiekh
SQL Server Import & Export Wizard
|||Hi mukesh,
The way you imported the first table just load the second table but with a different name i.e Table2 to the same database and then you can use the query
Lets Table_1 is having 10000
Table_2 is having 5500
----------------
Insert into Table_1
Select * from Table_2
----------------
the simplest way to do the stuff...
Satya
Thanks Mr.Akhhttar
But sir in management studio I can't find "Import and Export option" there r these option,"detach","shrink","backup","restore"& generate scripts.
thanks and regards
mukesh
|||Thanks a lot,Mr.Satya
Monday, February 13, 2012
App server unable to connect to SQL Server 2000 developer edition on localhost.
Anyone encounter differences between SQL2K EE and SQL2K Dev Editon?
FAILS
--
Machine_A [App Server] <-- JDBC --> Machine_A\SQL2K_Dev_Ed..db
Error: "com.inet.tds.SQLException: Connection refused"
When app server on Machine_A attempts to connect to database on
Machine_A the conenction is refused.
SUCCEEDS
---
Machine_A [App Server] <-- JDBC --> Machine_B\SQL2K_EE..db
When app server on Machine_A attempts to connect to database on
Machine_B the conenction succeeds and the app server runs normally.
JDBC driver: com.inet.tds.TdsDriver
jdbc:inetdae7:locahost:1433
I don't believe the app server is exhausting the 10-connection max on
SQL2K developer edition (there is a 10-connection limit imposed on the
developer edition, correct?)
LBlbunet@.hotmail.com (LB) wrote in message news:<35e1fa55.0404062027.3635b8b9@.posting.google.com>...
> Anyone encounter differences between SQL2K EE and SQL2K Dev Editon?
> FAILS
> --
> Machine_A [App Server] <-- JDBC --> Machine_A\SQL2K_Dev_Ed..db
> Error: "com.inet.tds.SQLException: Connection refused"
> When app server on Machine_A attempts to connect to database on
> Machine_A the conenction is refused.
>
> SUCCEEDS
> ---
> Machine_A [App Server] <-- JDBC --> Machine_B\SQL2K_EE..db
>
> When app server on Machine_A attempts to connect to database on
> Machine_B the conenction succeeds and the app server runs normally.
> JDBC driver: com.inet.tds.TdsDriver
> jdbc:inetdae7:locahost:1433
> I don't believe the app server is exhausting the 10-connection max on
> SQL2K developer edition (there is a 10-connection limit imposed on the
> developer edition, correct?)
> LB
There is no connection limit in Developer Edition - it's Enterprise
Edition with a different licence.
I don't know exactly what "Connection refused" means, but you might
want to check the SQL Server logs for failed logins, and also test
your username/password combination with osql.exe or whatever, just to
make sure it works correctly. You could also check the authentication
modes on the two servers (Windows or Mixed), to see if they are the
same - username/password works only in Mixed mode, if that's what
you're using.
Simon|||sql@.hayes.ch (Simon Hayes) wrote in message news:<60cd0137.0404070120.39c31661@.posting.google.com>...
... [See first post for text that appeared here]
> There is no connection limit in Developer Edition - it's Enterprise
> Edition with a different licence.
> I don't know exactly what "Connection refused" means, but you might
> want to check the SQL Server logs for failed logins, and also test
> your username/password combination with osql.exe or whatever, just to
> make sure it works correctly. You could also check the authentication
> modes on the two servers (Windows or Mixed), to see if they are the
> same - username/password works only in Mixed mode, if that's what
> you're using.
> Simon
Thanks for the feedback.
LB
Subscribe to:
Posts (Atom)