BIDS and SSMS very slow on Windows XP SP2

Hi,

opening SQL Server Management Studio 2005 or Business Intelligence Development Studio 2005 on my Windows XP SP2 Professional Edition is extremely slow. Espacially in BIDS it take several seconds for each action.

Is anybody aware of this problem? We didn't have those problems on Win2000 so I guess it is XP related.

Any ideas?

Regards

Norbert Bender

http://www.sql-server-performance.com//faq/?f=144|||

I added the /nosplash option but it didn't change anything. It is still very slow. Any other idea?

Regards

Norbert

|||

I would guess sometimes it take forever, when I had that problem I've uninstalled and resinstalled the tools which gave me senisble performance on that aspect.

|||

I would start by making sure you have sufficient memory on the machine. Both SSMS and BIDS have a large number of .NET managed code components. .NET applications use quite a bit of memory, so they are much more performant on machines with lots of memory. SSMS runs fine on my 1.2 GHz P3 laptop, but it has 1GB of RAM.

Next, if you are running SSMS on the same machine as SQL Server, and if this is a development environment, I would limit the amount of RAM available to SQL Server. By default, SQL Server will use every available byte of memory on the machine if it thinks it needs it. This is a good thing for production servers where server performance is everything, but this tends to starve other applications running on the server. On my laptop, I limit the server to 128 MB of RAM, which is sufficient for testing purposes. If you are working with a production server, consider running SSMS or BIDS on a different machine and connecting remotely to the server.

Next, consider what else you are running in the background. If you are running a large number of applications, you might not have a lot of memory left for SSMS or BIDS. If you are running some application that is using the disk drive continuously, that can hurt performance too. The file system runs at very high priority and can monopolize the system if there are lot of reads and writes going on, particularly on single processor machines. My laptop becomes basically unusable while I'm compiling a large code-base, for example.

Last, if possible, make sure your machine can connect to the internet. The .NET runtime validates that the certificates that code is signed with are valid when applications start. Part of this operation requires the runtime to get the list of revoked certificates from the http://crl.microsoft.com website to make sure the code wasn't signed with a revoked certificate. (Some fake certificates were issued in Microsoft's name a few years back, so this is a real concern.) If the runtime can't quickly connect to the website, it can take up to 45 seconds for the operation to time-out completely. You can turn this check off, but it's fairly dangerous to do that on machines that are sometimes connected to the internet.

Hope this helps,
Steve

|||

Thanks for those detailed information. I guess the last issue is it, as the account I am using is not the one, which is allowed to connect to the internet.

I will try this and I will give you feedback asap.

Regards nad thanks

Norbert

|||

Thanks for the hints. I checked the permissions for the account and they can access the internet, so I guess, this isn't the solution. My client has has 1 GB to as RAM and ususally I do not have memory intensive apps running. I think I will reinstall the whole software maybe this helps

Regards

Norbert

BIDS and SSMS very slow on Windows XP SP2

Hi,

opening SQL Server Management Studio 2005 or Business Intelligence Development Studio 2005 on my Windows XP SP2 Professional Edition is extremely slow. Espacially in BIDS it take several seconds for each action.

Is anybody aware of this problem? We didn't have those problems on Win2000 so I guess it is XP related.

Any ideas?

Regards

Norbert Bender

http://www.sql-server-performance.com//faq/?f=144|||

I added the /nosplash option but it didn't change anything. It is still very slow. Any other idea?

Regards

Norbert

|||

I would guess sometimes it take forever, when I had that problem I've uninstalled and resinstalled the tools which gave me senisble performance on that aspect.

|||

I would start by making sure you have sufficient memory on the machine. Both SSMS and BIDS have a large number of .NET managed code components. .NET applications use quite a bit of memory, so they are much more performant on machines with lots of memory. SSMS runs fine on my 1.2 GHz P3 laptop, but it has 1GB of RAM.

Next, if you are running SSMS on the same machine as SQL Server, and if this is a development environment, I would limit the amount of RAM available to SQL Server. By default, SQL Server will use every available byte of memory on the machine if it thinks it needs it. This is a good thing for production servers where server performance is everything, but this tends to starve other applications running on the server. On my laptop, I limit the server to 128 MB of RAM, which is sufficient for testing purposes. If you are working with a production server, consider running SSMS or BIDS on a different machine and connecting remotely to the server.

Next, consider what else you are running in the background. If you are running a large number of applications, you might not have a lot of memory left for SSMS or BIDS. If you are running some application that is using the disk drive continuously, that can hurt performance too. The file system runs at very high priority and can monopolize the system if there are lot of reads and writes going on, particularly on single processor machines. My laptop becomes basically unusable while I'm compiling a large code-base, for example.

Last, if possible, make sure your machine can connect to the internet. The .NET runtime validates that the certificates that code is signed with are valid when applications start. Part of this operation requires the runtime to get the list of revoked certificates from the http://crl.microsoft.com website to make sure the code wasn't signed with a revoked certificate. (Some fake certificates were issued in Microsoft's name a few years back, so this is a real concern.) If the runtime can't quickly connect to the website, it can take up to 45 seconds for the operation to time-out completely. You can turn this check off, but it's fairly dangerous to do that on machines that are sometimes connected to the internet.

Hope this helps,
Steve

|||

Thanks for those detailed information. I guess the last issue is it, as the account I am using is not the one, which is allowed to connect to the internet.

I will try this and I will give you feedback asap.

Regards nad thanks

Norbert

|||

Thanks for the hints. I checked the permissions for the account and they can access the internet, so I guess, this isn't the solution. My client has has 1 GB to as RAM and ususally I do not have memory intensive apps running. I think I will reinstall the whole software maybe this helps

Regards

Norbert

BIDS and SSMS very slow on Windows XP SP2

Hi,

opening SQL Server Management Studio 2005 or Business Intelligence Development Studio 2005 on my Windows XP SP2 Professional Edition is extremely slow. Espacially in BIDS it take several seconds for each action.

Is anybody aware of this problem? We didn't have those problems on Win2000 so I guess it is XP related.

Any ideas?

Regards

Norbert Bender

http://www.sql-server-performance.com//faq/?f=144|||

I added the /nosplash option but it didn't change anything. It is still very slow. Any other idea?

Regards

Norbert

|||

I would guess sometimes it take forever, when I had that problem I've uninstalled and resinstalled the tools which gave me senisble performance on that aspect.

|||

I would start by making sure you have sufficient memory on the machine. Both SSMS and BIDS have a large number of .NET managed code components. .NET applications use quite a bit of memory, so they are much more performant on machines with lots of memory. SSMS runs fine on my 1.2 GHz P3 laptop, but it has 1GB of RAM.

Next, if you are running SSMS on the same machine as SQL Server, and if this is a development environment, I would limit the amount of RAM available to SQL Server. By default, SQL Server will use every available byte of memory on the machine if it thinks it needs it. This is a good thing for production servers where server performance is everything, but this tends to starve other applications running on the server. On my laptop, I limit the server to 128 MB of RAM, which is sufficient for testing purposes. If you are working with a production server, consider running SSMS or BIDS on a different machine and connecting remotely to the server.

Next, consider what else you are running in the background. If you are running a large number of applications, you might not have a lot of memory left for SSMS or BIDS. If you are running some application that is using the disk drive continuously, that can hurt performance too. The file system runs at very high priority and can monopolize the system if there are lot of reads and writes going on, particularly on single processor machines. My laptop becomes basically unusable while I'm compiling a large code-base, for example.

Last, if possible, make sure your machine can connect to the internet. The .NET runtime validates that the certificates that code is signed with are valid when applications start. Part of this operation requires the runtime to get the list of revoked certificates from the http://crl.microsoft.com website to make sure the code wasn't signed with a revoked certificate. (Some fake certificates were issued in Microsoft's name a few years back, so this is a real concern.) If the runtime can't quickly connect to the website, it can take up to 45 seconds for the operation to time-out completely. You can turn this check off, but it's fairly dangerous to do that on machines that are sometimes connected to the internet.

Hope this helps,
Steve

|||

Thanks for those detailed information. I guess the last issue is it, as the account I am using is not the one, which is allowed to connect to the internet.

I will try this and I will give you feedback asap.

Regards nad thanks

Norbert

|||

Thanks for the hints. I checked the permissions for the account and they can access the internet, so I guess, this isn't the solution. My client has has 1 GB to as RAM and ususally I do not have memory intensive apps running. I think I will reinstall the whole software maybe this helps

Regards

Norbert

Better to backup up all server databases or backup system databases separately from databa

Gurus,
Running SQL Server 2005 SP2 and using named instances. I am having lots of
important application databases on my server these days. My question is
this. Is it better to back up all server databases in one maintenance plan
or backup system databases separately from databases?
Spin
I don't think it matters one way or another. But then it depends on what
issues you may be struggling with.
If you have scheduling issues running a single maintenance plan, break it up
into multiple plans. Personally, I prefer dealing system databases
separately. In particular, when you are dealing relatively large user
databases, you may not want to use the MS maintenance plans and may choose to
schedule their backups in your own schduler for better flexibility.
Linchi
Linchi
"Spin" wrote:

> Gurus,
> Running SQL Server 2005 SP2 and using named instances. I am having lots of
> important application databases on my server these days. My question is
> this. Is it better to back up all server databases in one maintenance plan
> or backup system databases separately from databases?
> --
> Spin
>

Better to backup up all server databases or backup system databases separately from databa

Gurus,
Running SQL Server 2005 SP2 and using named instances. I am having lots of
important application databases on my server these days. My question is
this. Is it better to back up all server databases in one maintenance plan
or backup system databases separately from databases?
--
SpinI don't think it matters one way or another. But then it depends on what
issues you may be struggling with.
If you have scheduling issues running a single maintenance plan, break it up
into multiple plans. Personally, I prefer dealing system databases
separately. In particular, when you are dealing relatively large user
databases, you may not want to use the MS maintenance plans and may choose to
schedule their backups in your own schduler for better flexibility.
Linchi
Linchi
"Spin" wrote:
> Gurus,
> Running SQL Server 2005 SP2 and using named instances. I am having lots of
> important application databases on my server these days. My question is
> this. Is it better to back up all server databases in one maintenance plan
> or backup system databases separately from databases?
> --
> Spin
>

Best way to apply SP3 in Replication

We have a Pub, Dist and Sub Server all running under SP2 with worm update and are looking to apply SP3a . Replication is transactional with heavy usage . What is the best sequence to apply SP3
can it be spread out in 3 weekends or has to be done all together ?
ThanksI don't know why you have to spread the upgrade into three weekends. It shouldn't take that long unless you have many db servers. The SP3 upgrade I did to all db servers, with some minor problems of course, was done in one weekend. We are fully replicated environment. You need to shut down all subscriptions or just stop the SQL Agent on the subscriber(assuming it is a pull), no need to shut down the machine tough. The you shut down the Distributor, if it is on a different machine. Apply SP3 on Publisher first, then Distributor, and Subscriber. Remember to uncheck to autostart SQL Agent so replication agents won't get started incidently. After finished applying SP3, turn the replication back on. If you a certain agents fails, reintialize it. Good Luck.|||Reason is that databses are really huge and We had occasion when SP3 failed on us leaving dbs in SP2.5 LOL . then we spaend 3 hrs with Msoft and installed the SP3 in Debug mode . I am being careful because we get a window between 1:Am to 5:AM only to do any changes and is too short to do all three if something doesn't go well

Thanks|||Thanks ..

Anything specific to do on Publisher other than Backups / Agent Auto-run to manual (and disabling on dist and Subs.)|||With transactional replication, the proper sequence should be distributor, publisher, and subscriber. The distributor should always be upgraded first. Please refer to SQL 2000 books online <\Installing SQL Server\Upgrading to SQL Server 2000: Overview\ Replication and upgrading> for details.|||I will definately follow the guidelines !