SQL Remove Old Backups: machine

Showing posts with label machine. Show all posts

Thursday, March 22, 2012

32 bit SQLDMO code on a 64 bit server

Should an application written in VB6 and early bound to SQL Server 2000
SQLDMO run on a machine with 64 bit SQL Server 2000 installed?
We update SQL databases with a custom written in house VB6 app. What would
be involved in getting this program to run in this environment?
Thanks for any input.Hi
VB 6 is a 32 bit applicatzion and will not run on 64 bit Itanium I/II's as
the Itanium is a lot different in architecture to the existing 32 bit
processor.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Scott Duckworth" wrote:

> Should an application written in VB6 and early bound to SQL Server 2000
> SQLDMO run on a machine with 64 bit SQL Server 2000 installed?
> We update SQL databases with a custom written in house VB6 app. What would
> be involved in getting this program to run in this environment?
> Thanks for any input.
>
>|||Thanks for the info.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:DF34C2FB-F59D-48F8-BBA5-D57339C384B9@.microsoft.com...
> Hi
> VB 6 is a 32 bit applicatzion and will not run on 64 bit Itanium I/II's as
> the Itanium is a lot different in architecture to the existing 32 bit
> processor.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Scott Duckworth" wrote:
>
would|||There is such a thing as WOW64 hosts 32-bit Windows applications. If you are
not running Windows Server 2003 SP1, you should use the IA32 extension
layer.
However Microsoft does not support running the SQL Server 2000 tools in
WOW64 on Itanium, which does not mean it does not work, it does.
So you would have to install the 32-bit client tools on your Itanium, which
will get you SQL-DMO, then you need your VB6 application and VB6 runtime.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:DF34C2FB-F59D-48F8-BBA5-D57339C384B9@.microsoft.com...
> Hi
> VB 6 is a 32 bit applicatzion and will not run on 64 bit Itanium I/II's as
> the Itanium is a lot different in architecture to the existing 32 bit
> processor.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Scott Duckworth" wrote:
>

32 bit CLR-code and 64 bit SQLServer

Hello,
is it possible to deploy CLR-code developed with a 32 bit VS.NET on a
32 bit machine to a 64 bit SQLServer?
Thanks
Tobias"Paletti" <Tobias@.Olbort.de> wrote in news:1135757756.405122.308810
@.o13g2000cwo.googlegroups.com:

> is it possible to deploy CLR-code developed with a 32 bit VS.NET on a
> 32 bit machine to a 64 bit SQLServer?
As long as the 32 bit is CLR 2.0 and built with the AnyCPU flag (or the 64-
bit CPU flag).
Niels
****************************************
**********
* Niels Berglund
* http://staff.develop.com/nielsb
* nielsb@.no-spam.develop.com
* "A First Look at SQL Server 2005 for Developers"
* http://www.awprofessional.com/title/0321180593
****************************************
**********

Thursday, March 8, 2012

2147467259 - [DBNETLIB][ConnectionWrite (send()).]General network

I Have SQL Express installed on 17 ships. Each ship has a VB6 Client
application using OLEDB to connect to the database on local machine. Other
workstations on network also connect - we think without error. The error
above is thrown on 4 of the 17 ships. The workstations acting as the file
server are supposed to be identical (Windows XP).
We have been assured that all poer save settings on LAN Card and motherboard
have been disabled.
If I google on this error, I get over 100 hits going back several years !
Ideas to fix have included turning off connection pooling and using TCPIP
instead of Named Pipes on client workstation where database server and
application are running.
Any other ideas on what could cause this, or why 13 machines are OK, but 4
are not ? Thanks.
Mark StoryPerhaps watching this might help:
http://support.microsoft.com/kb/875285/
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
"Mark Story" <MarkStory@.discussions.microsoft.com> wrote in message
news:E02C9E86-1EF3-40CD-8487-57B18A02BFCA@.microsoft.com...
>I Have SQL Express installed on 17 ships. Each ship has a VB6 Client
> application using OLEDB to connect to the database on local machine. Other
> workstations on network also connect - we think without error. The error
> above is thrown on 4 of the 17 ships. The workstations acting as the file
> server are supposed to be identical (Windows XP).
> We have been assured that all poer save settings on LAN Card and
> motherboard
> have been disabled.
> If I google on this error, I get over 100 hits going back several years !
> Ideas to fix have included turning off connection pooling and using TCPIP
> instead of Named Pipes on client workstation where database server and
> application are running.
> Any other ideas on what could cause this, or why 13 machines are OK, but 4
> are not ? Thanks.
>
> --
> Mark Story

2008 Kids not playing well together?

I have Orcas (VisualStudio 2008) and Katmai (SQL Server 2008) installed on the same machine, but Orcas will not allow me to add a data connection to the Katmai database. It goes through the wizard and the connection tests okay, but then I get a message saying it doesn't support anything above SQL Server 2005.

Is there some sort of update for Orcas that will allow me to use my Katmai databases?

Thanks,
Todd
Did you try using an OLEDB connection ? I did not try that on my own, but it should be worth a try.

Jens K. Suessmeyer

http://www.sqlserver2005.de
|||Orcas will support Katmai in a later Orcas CTP. For now, you cannot connect with Orcas to Katmai.

2008 Kids not playing well together?

Is there some sort of update for Orcas that will allow me to use my Katmai databases?

Thanks,
Todd
Did you try using an OLEDB connection ? I did not try that on my own, but it should be worth a try.

Jens K. Suessmeyer

http://www.sqlserver2005.de
|||Orcas will support Katmai in a later Orcas CTP. For now, you cannot connect with Orcas to Katmai.

Tuesday, March 6, 2012

2005Management Studio

We have SQL 2005 -- Yukon 9.00.852 running on one machine.

Couple of days ago it is working fine and I am using the Object explorer in Management studio. Know suddnly all the database are gone from object explorer and I only can not see the server name and no database under it.

How I can bring all the database backu in Object explort--management studio.

From command line I can access all the databases. They are up and running fine.

Please email me at consultant_5400@.yahoo.com.

Did you already try File->Connect Object Explorer?

Sayed Ibrahim Hashimi
www.sedodream.com
|||

Yes I try that , It did not work, I also try to register the server again and it also did not not work.

May be best option is to install Management studio only again. But we have one database on it.

Thanks

|||Did you check the error logs and tempdb size? In SQL2000, full tempdb would be a reason for databases not displaying in EM - perhaps this is the same in SQL2005? Just an idea...|||

Hi,

Please can you let me know if it is a temp database issue how to fix that.

I already restart the services, But still it is not showing us databases in EM.

2005/2000 question!

Hi I have both sql 2005 and 2000 installed on a machine. When I start
management studio it can connect to legacy 2000 databases. What I want to do
is create a new database with all of the 2005 attributes. Is there a way to
put management studio in a mode where it will create a new 2005 database and
have all of the 2005 features with 2000 still on the machine?
thanks.
--
Paul G
Software engineer.SQL Server 2000 and SQL Server 2005 can coexist on the same machine
without problem, but only one can be the default instance. The
default instance is the one that will be referenced when only the
computer name is supplied. There can be one or more named instances
for each version of SQL Server, but referencing those requires
computer_name\instance_name.
Having said that, Management Studio can work with any instance of 2000
or 2005. Open the Registered Servers window and make sure there is an
entry for every instance on the machine. When you want to create a
new database "with all of the 2005 attributes", choose a SQL Server
2005 instance from this list, right click and choose Connect / Object
Explorer. In the Object Explorer window, right-click on Databases in
a 2005 instance and choose New.
Roy Harvey
Beacon Falls, CT
On Mon, 24 Sep 2007 09:02:08 -0700, Paul
<Paul@.discussions.microsoft.com> wrote:
>Hi I have both sql 2005 and 2000 installed on a machine. When I start
>management studio it can connect to legacy 2000 databases. What I want to do
>is create a new database with all of the 2005 attributes. Is there a way to
>put management studio in a mode where it will create a new 2005 database and
>have all of the 2005 features with 2000 still on the machine?
>thanks.|||On Mon, 24 Sep 2007 09:02:08 -0700, Paul wrote:
>Hi I have both sql 2005 and 2000 installed on a machine. When I start
>management studio it can connect to legacy 2000 databases. What I want to do
>is create a new database with all of the 2005 attributes. Is there a way to
>put management studio in a mode where it will create a new 2005 database and
>have all of the 2005 features with 2000 still on the machine?
>thanks.
Hi Paul,
I have both SQL Server 2000 and SQL Server 2005 running on my machine,
and I use SSMS to connect to both. When connected to SQL Server 2005, I
can use all the new features. When connected to SQL Server 2000, I am
obviously limited to the old feature set.
So if you connect SSMS to your SQL Server 2005 instance, you should be
able to create new SQL Server 2005 databases without problems.
--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis|||Hi I did not see an entry for the 2005 instance. I also opened the SQL
Server Configuartion manager and it lists the following, 1. SQL Server 2005
services, 2. SQL Server 2005 Network config, 3. SQL Native client config.
Wondering if there is something I missed in the installation?
thanks.
--
Paul G
Software engineer.
"Roy Harvey (SQL Server MVP)" wrote:
> SQL Server 2000 and SQL Server 2005 can coexist on the same machine
> without problem, but only one can be the default instance. The
> default instance is the one that will be referenced when only the
> computer name is supplied. There can be one or more named instances
> for each version of SQL Server, but referencing those requires
> computer_name\instance_name.
> Having said that, Management Studio can work with any instance of 2000
> or 2005. Open the Registered Servers window and make sure there is an
> entry for every instance on the machine. When you want to create a
> new database "with all of the 2005 attributes", choose a SQL Server
> 2005 instance from this list, right click and choose Connect / Object
> Explorer. In the Object Explorer window, right-click on Databases in
> a 2005 instance and choose New.
> Roy Harvey
> Beacon Falls, CT
> On Mon, 24 Sep 2007 09:02:08 -0700, Paul
> <Paul@.discussions.microsoft.com> wrote:
> >Hi I have both sql 2005 and 2000 installed on a machine. When I start
> >management studio it can connect to legacy 2000 databases. What I want to do
> >is create a new database with all of the 2005 attributes. Is there a way to
> >put management studio in a mode where it will create a new 2005 database and
> >have all of the 2005 features with 2000 still on the machine?
> >thanks.
>

Saturday, February 25, 2012

2005 SP2 Install Would complete

Hi,

I have a problem with my SQL Server 2005 instance after trying to install SP2.

My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.

I installed Express SP2 and this installed without a hitch.

Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.

It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.

I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.

I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.

Please Help!

Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix

Thanks,

Peter Saddow

|||

There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.

|||

Microsoft SQL Server 2005 Service Pack 2 Setup

Feature Selection

This setup program detected the following SQL Server 2005 features. Select the program

features that you would like to update. To see the details of a feature, click on the feature.

O Setup Support Files

X MSSQLSERVER

X Database Services

X Analysis Services Language ENU

X Reporting Services Platform x86

O SQLEXPRESS Edition DEVELOPER

O Database Services Status Upgraded

O Notification Services

O Integration Services

O SQL Server Native Client

O Client Components

O MSXML 6.0 Parser

O SQLXML4

O Backward Compatibility

O Microsoft SQL Server VSS Writer

|||

After the previous screen I select next, then make sure Windows Authentication is selected then click next again.

Your account information could not be verified.

Press Ok to return to Authentication Mode screen to determine the reason for failure.

For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.

After I click Ok & Back the Feature Selection screen shows details of:

Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.

And it shows a status of:

Not Valid

|||

I am getting the same issue.. can you help? When i am trying to install SP2

Your account information could not be verified.

Press Ok to return to Authentication Mode screen to determine the reason for failure.

For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.

2005 SP2 Install Failed, and Now SQL Server is Unusable. - (SQL9_Hotfix_KB921896_sqlrun_sql.msp.

Hi,

I have a problem with my SQL Server 2005 instance after trying to install SP2.

My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.

I installed Express SP2 and this installed without a hitch.

I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.

Please Help!

Thanks,

Peter Saddow

|||

MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

|||

Microsoft SQL Server 2005 Service Pack 2 Setup

Feature Selection

This setup program detected the following SQL Server 2005 features. Select the program

features that you would like to update. To see the details of a feature, click on the feature.

O Setup Support Files

X MSSQLSERVER

X Database Services

X Analysis Services Language ENU

X Reporting Services Platform x86

O SQLEXPRESS Edition DEVELOPER

O Database Services Status Upgraded

O Notification Services

O Integration Services

O SQL Server Native Client

O Client Components

O MSXML 6.0 Parser

O SQLXML4

O Backward Compatibility

O Microsoft SQL Server VSS Writer

|||

After the previous screen I select next, then make sure Windows Authentication is selected then click next again.

Your account information could not be verified.

Press Ok to return to Authentication Mode screen to determine the reason for failure.

For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.

After I click Ok & Back the Feature Selection screen shows details of:

Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.

And it shows a status of:

Not Valid

|||

I am getting the same issue.. can you help? When i am trying to install SP2

Your account information could not be verified.

Press Ok to return to Authentication Mode screen to determine the reason for failure.

For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.

2005 SP2 Install Failed, and Now SQL Server is Unusable. - (SP2 Install Screen Shot)

Hi,

I have a problem with my SQL Server 2005 instance after trying to install SP2.

My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.

I installed Express SP2 and this installed without a hitch.

I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.

Please Help!

Thanks,

Peter Saddow

|||

MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

|||

Microsoft SQL Server 2005 Service Pack 2 Setup

Feature Selection

This setup program detected the following SQL Server 2005 features. Select the program

features that you would like to update. To see the details of a feature, click on the feature.

O Setup Support Files

X MSSQLSERVER

X Database Services

X Analysis Services Language ENU

X Reporting Services Platform x86

O SQLEXPRESS Edition DEVELOPER

O Database Services Status Upgraded

O Notification Services

O Integration Services

O SQL Server Native Client

O Client Components

O MSXML 6.0 Parser

O SQLXML4

O Backward Compatibility

O Microsoft SQL Server VSS Writer

|||

After the previous screen I select next, then make sure Windows Authentication is selected then click next again.

Your account information could not be verified.

Press Ok to return to Authentication Mode screen to determine the reason for failure.

For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.

After I click Ok & Back the Feature Selection screen shows details of:

Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.

And it shows a status of:

Not Valid

|||

I am getting the same issue.. can you help? When i am trying to install SP2

Your account information could not be verified.

Press Ok to return to Authentication Mode screen to determine the reason for failure.

For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.

2005 SP2 Install Failed, and Now SQL Server is Unusable.

Hi,

I have a problem with my SQL Server 2005 instance after trying to install SP2.

My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.

I installed Express SP2 and this installed without a hitch.

I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.

Please Help!

Thanks,

Peter Saddow

|||

MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.

|||

Microsoft SQL Server 2005 Service Pack 2 Setup

Feature Selection

This setup program detected the following SQL Server 2005 features. Select the program

features that you would like to update. To see the details of a feature, click on the feature.

O Setup Support Files

X MSSQLSERVER

X Database Services

X Analysis Services Language ENU

X Reporting Services Platform x86

O SQLEXPRESS Edition DEVELOPER

O Database Services Status Upgraded

O Notification Services

O Integration Services

O SQL Server Native Client

O Client Components

O MSXML 6.0 Parser

O SQLXML4

O Backward Compatibility

O Microsoft SQL Server VSS Writer

|||

After the previous screen I select next, then make sure Windows Authentication is selected then click next again.

Your account information could not be verified.

Press Ok to return to Authentication Mode screen to determine the reason for failure.

For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.

After I click Ok & Back the Feature Selection screen shows details of:

Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.

And it shows a status of:

Not Valid

|||

I am getting the same issue.. can you help? When i am trying to install SP2

Your account information could not be verified.

Press Ok to return to Authentication Mode screen to determine the reason for failure.

For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.

Friday, February 24, 2012

2005 slower than 2000?

Admittedly I'm evaluating 2005 in a virtual machine but I'm comparing it to
an older machine:
2005 thinks it has 1Gb and 1 cpu on a host which has 2GB, 2 2.4Ghz Amd64's,
raid0. it runs in boosted priority when active.
2000 is on an older single Amd64 2Ghz, 1Gb, single sata drive.
A very ugly query built by selections on a web page is parsed and
parameterized.
on 2000 it runs in a couple seconds against a few thousand rows joining lots
of tables, varying by the selections made.
on 2005 it takes twice as long for the identical query. all other software
variables are identical. the db is a copy from 2000. stats updated. tried
with both compatibility levels.
I'm thinking I'll wait for 9.1 or 9.2 before I make the move.br (br@.discussions.microsoft.com) writes:
> Admittedly I'm evaluating 2005 in a virtual machine but I'm comparing it
> to an older machine:
> 2005 thinks it has 1Gb and 1 cpu on a host which has 2GB, 2 2.4Ghz
> Amd64's, raid0. it runs in boosted priority when active. 2000 is on an
> older single Amd64 2Ghz, 1Gb, single sata drive.
> A very ugly query built by selections on a web page is parsed and
> parameterized. on 2000 it runs in a couple seconds against a few
> thousand rows joining lots of tables, varying by the selections made.
> on 2005 it takes twice as long for the identical query. all other
> software variables are identical. the db is a copy from 2000. stats
> updated. tried with both compatibility levels.
> I'm thinking I'll wait for 9.1 or 9.2 before I make the move.
Before you do that... The database on SQL 2005, is that a copy of the
database from SQL 2000? In such case, did you run UPDATE STATISTICS
WITH FULLSCAN on all table (or just sp_updatestats if you prefer)? When
you restore a database from SQL 2000, all statistics are invalidated,
this can be an important reason for difference in performance.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Did you install SQL Server Standard/Enterprise Edition or Express Edition?
Express edition is limited by design to 1 CPU, 1 GB RAM, and 4 GB database
size.
There are server and database configuration settings that can impact
performance:
http://www.sql-server-performance.c...ance_audit5.asp
Analyze the execution plan and performance monitor logs to determine what
exactly is going on.
http://msdn.microsoft.com/library/d... />
1_5pde.asp
http://www.informit.com/guides/cont...&seqNum=28&rl=1
BTY, what is "9.1 or 9.2" ?
"br" <br@.discussions.microsoft.com> wrote in message
news:2C96E892-1713-4486-8DE6-B0E56AEF29C3@.microsoft.com...
> Admittedly I'm evaluating 2005 in a virtual machine but I'm comparing it
> to
> an older machine:
> 2005 thinks it has 1Gb and 1 cpu on a host which has 2GB, 2 2.4Ghz
> Amd64's,
> raid0. it runs in boosted priority when active.
> 2000 is on an older single Amd64 2Ghz, 1Gb, single sata drive.
> A very ugly query built by selections on a web page is parsed and
> parameterized.
> on 2000 it runs in a couple seconds against a few thousand rows joining
> lots
> of tables, varying by the selections made.
> on 2005 it takes twice as long for the identical query. all other software
> variables are identical. the db is a copy from 2000. stats updated. tried
> with both compatibility levels.
> I'm thinking I'll wait for 9.1 or 9.2 before I make the move.
>|||Thanks guys,
It's the developer version. Roughly equivalent to standard.
The stats are updated.
I'm figuring I'll have to re-optimize for 2005, so I don't mind waiting for
a fix rev or two.
But thanks for the links. I'll check them out.
"JT" wrote:

> Did you install SQL Server Standard/Enterprise Edition or Express Edition?
> Express edition is limited by design to 1 CPU, 1 GB RAM, and 4 GB database
> size.
> There are server and database configuration settings that can impact
> performance:
> http://www.sql-server-performance.c...ance_audit5.asp
> Analyze the execution plan and performance monitor logs to determine what
> exactly is going on.
> http://msdn.microsoft.com/library/d...>
n_1_5pde.asp
> http://www.informit.com/guides/cont...&seqNum=28&rl=1
> BTY, what is "9.1 or 9.2" ?
> "br" <br@.discussions.microsoft.com> wrote in message
> news:2C96E892-1713-4486-8DE6-B0E56AEF29C3@.microsoft.com...
>
>|||Sorry, missed that. Means one or two revisions to Sql2005, which I'm
considering to be Sql Server 9.
"JT" wrote:
> BTY, what is "9.1 or 9.2" ?|||Try testing again in an environment other than a virtual machine (MS Virtual
PC ?). There may be VM session settings limiting RAM and CPU usage. Also,
SQL Server is optimized to work directly with the OS and hardware, and a VM
session is an abstraction layer.
"br" <br@.discussions.microsoft.com> wrote in message
news:9C34254A-E671-4E1D-84BF-E586D5A74830@.microsoft.com...
> Thanks guys,
> It's the developer version. Roughly equivalent to standard.
> The stats are updated.
> I'm figuring I'll have to re-optimize for 2005, so I don't mind waiting
> for
> a fix rev or two.
> But thanks for the links. I'll check them out.
> "JT" wrote:
>|||There are a lot of people using 2005 today with no broad based complaints
about performance. You are perhaps thinking that a future service pack will
include performance optimizations for a vitual machine environment? ;-)
"br" <br@.discussions.microsoft.com> wrote in message
news:4A3878EB-4E4B-491F-9C3B-5A81F2FC8510@.microsoft.com...
> Sorry, missed that. Means one or two revisions to Sql2005, which I'm
> considering to be Sql Server 9.
> "JT" wrote:
>|||True... ok, some w

end when I have a free morning I'll put it on a real
machine.
"JT" wrote:

> ...a VM session is an abstraction layer.
>

2005 Reporting Services Configuration Issues

Hi All -

I am trying to configure reporting services on virtual machine but unable to succeed. I never touched this topic before SQL Server 2005. The left hand side options in Reporting Services Configuration Manager such as Server Status, Virtual Directories, Web Identity works fine but it fails in Database Setup section

Here are the details:

AppServer: SQL Server 2005 Reporting Services & Client components build# 2153 (with SP1 & SP1 hotfix)

going to apply SP2 and Add-on component after the configuration

DBServer: SQL Server 2005 Database Services & Client components build# 2153 (with SP1 & SP1 hotfix)

OS: Windows 2003 Server with SP1

IIS version on AppServer: 6

I have SQL 2005 Reporting services and 2005 Database Engine on 2 different machines.

Here is the error message I am receiving when I try to apply the script in "Database Setup" section of Reporting Services Configuration Manager

It did not log any errors in SQL Server however it shows a warning message in Event Log

Event Log message - "The RSReportServer.config file has been modified."

Configuration Manager error message - It shows me "Create a Grants Rights Script" task failed

"System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String machine)
at ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String dbServer)
at ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String connectionString, String server, String database, ConfigurationCredentialsType credsType, String account, String password, Boolean upgrade, String dbVersion)"

I have captured the screenshot, let me know if I can send this.

One of my friends suggested the following and I have tried the first option but could not work - Option I)

Our account that is used for database connection should have

1) public and RSExecRole roles for the ReportServerDatabase.

2) RSExecRole roles for the master, msdb , and ReportServerTempDB databases.

Else - Option II)

we can run the Reporting Service Windows Service under the local System Account and then the credentials type for the database set up would be Service credentials. This way we would have more permission.

Did anyone face this problem? how should I resolve this?

Anyone have steps to follow as I feel of missing something in the configuration steps?

Any information/ suggestions/ pointer on this are higly appreciated.

Thanks in advance !!

-Satya

We were getting this error and found that the dbo.role was not the owner of the dbo.schema. When we made that change we were able to update the database. When we originally installed and had problems with the remote database we had to make sure that database had windows authentication only.|||

TWe also escalated this issue to Microsoft Product Support Service and they suggested the following:

The account that is used for database connection should have

1) public and RSExecRole roles for the ReportServerDatabase.

2) RSExecRole roles for the master, msdb , and ReportServerTempDB databases.

Else we can run the Reporting Service Windows Service under the local System Account and then the credentials type for the database set up would be Service credentials. This way we would have more permission.

but before we had a work around however you will still find the script showing error in Reporting Services configuration manager.

We have generated the login script and executed thru' Management Studio. Verified the account permission as mentioned above.

Just ignore the error message that you see in Configuration Manager -

Configuration Manager error message - "System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))