"Renaming package" dialog

I created a new SSIS solution, right-clicked the default name "Package.dtsx" (under SSIS Packages), then renamed it. A dialog appears asking "Do you want to rename the package object as well"?

What are they referring to and what are the consequences of doing/not doing so?

Barkingdog

In Visual Studio you rename a file - the *.dtsx file. However, the SSIS package is an object in the file. So if you don't rename the object you could have a package file called MySuperPackage.dtsx containing a package object called MyOldPackage. Try saying no to the dialog once and check the name property of the package in the properties window - select the package by clicking in the background of the object expolorer.

Analysis Services has the same issue with cubes and other objects. The objects are defined in XML and have a name property - which can be different from the filename of the xml.

For this reason, when renaming packages, you should use the designer - do not just rename them in the file system.

Donald

>2G ram & Standard Edition supported?

We have SQLServer standard edition running on a machine
with 2.2G of RAM. The sales faq appears to indicate that
SQLServer is not supported on a machine with more than 2G
of RAM. Is this the case?
Thanks,
Simon
http://www.microsoft.com/sql/howtobuy/faq.asp
Q. What is the maximum amount of RAM supported by SQL
Server 2000?
A. SQL Server 2000 Standard Edition supports up to 2
gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
supports up to 64 GB of RAM.Simon
http://support.microsoft.com/defaul...kb;en-us;274750
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...

quote:

---

> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>

---

|||SQL Server Standard Edition is "supported" on machines with > 2GB, meaning
that MS will still give you technical support if you run it this way.
However Standard Edition only "supports" 2GB of RAM, meaning it will not use
more even if the machine has more installed.
To get SQL Server to use more than 2GB RAM you need the Enterprise Edition.
Note that the OS and other programs on that server could utilize the RAM,
like Analysis Services, Reporting Services or Notification Services.
Mike Kruchten
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...

quote:

---

> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>

---

>2G ram & Standard Edition supported?

We have SQLServer standard edition running on a machine
with 2.2G of RAM. The sales faq appears to indicate that
SQLServer is not supported on a machine with more than 2G
of RAM. Is this the case?
Thanks,
Simon
--
http://www.microsoft.com/sql/howtobuy/faq.asp
Q. What is the maximum amount of RAM supported by SQL
Server 2000?
A. SQL Server 2000 Standard Edition supports up to 2
gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
supports up to 64 GB of RAM.Simon
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...
> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>|||SQL Server Standard Edition is "supported" on machines with > 2GB, meaning
that MS will still give you technical support if you run it this way.
However Standard Edition only "supports" 2GB of RAM, meaning it will not use
more even if the machine has more installed.
To get SQL Server to use more than 2GB RAM you need the Enterprise Edition.
Note that the OS and other programs on that server could utilize the RAM,
like Analysis Services, Reporting Services or Notification Services.
Mike Kruchten
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...
> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>

#Deleted appears in all SQL2000 linked tables in Access2003

I have a database on a SQL2000 server that I am trying to connect for viewin
g
in Access 2003 with the client running Windows 2000. I have created the
connection, but when I try to view the tables, I get "#Deleted" in all the
rows, for both tables. I installed the latest MS Jet Driver to no avail. I
also stumbled upon a posting stating that Access does not recognize BigInt a
s
a UID. Is this correct? Is there a workaround without having to mod the SQ
L
tables? I can open the tables fine with Sun's OpenOffice. Any help greatly
appreciated.It's an Access issue that can be caused by several things
such as using a float as the index or as part of the index
or having nulls as values in part of the index. And there
was an issue when using Bigints with some data sources as
well which wouldn't map correctly but that was corrected in
one of the Jet service packs. Make sure you have the latest
service pack for Jet.
-Sue
On Tue, 11 Apr 2006 05:39:01 -0700, Seth
<Seth@.discussions.microsoft.com> wrote:

>I have a database on a SQL2000 server that I am trying to connect for viewi
ng
>in Access 2003 with the client running Windows 2000. I have created the
>connection, but when I try to view the tables, I get "#Deleted" in all the
>rows, for both tables. I installed the latest MS Jet Driver to no avail.
I
>also stumbled upon a posting stating that Access does not recognize BigInt
as
>a UID. Is this correct? Is there a workaround without having to mod the S
QL
>tables? I can open the tables fine with Sun's OpenOffice. Any help greatl
y
>appreciated.