Concatenate 2 date fields to show long date

How can I concatenate 2 fields (both declared as datetime) to show them in long date format.
I tried placing a hidden text box with each individual field formatted as long date. This works. However when I try joining these 2 fields in a new text box I get invlaid expression using the following syntax:
me.hidDateFrom.Value & me.HidDateTo.Value

This seems like an easy feat, but obviously not...

Thanks for any pointers.

You have to explain this better. Are you trying to get 2 column values (both datetime type) in one TextBox control by simply concatenating the string values? You may want to show what the column values are in your table as well as what you expect to see within the TextBox.|||

OK.

I'm trying to concatenate to datetime parameter values so that I get:
Report for the period 15 March 2006 to 20 March 2006.
15 March 2006 being the data returned from the startDate parameter whose value using this example is 15/03/2006 and 20 March 2006 being the data returned from the EndDate parameter whose value using this example is 20/03/2006.

I need to format the 2 datetime parameters to long dates AFTER input to show in a text box.
Hope this is more clear.

Complicated Licensing Question

We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
CPU box. Along with this, we are hoping to upgrade to SQL Server 2005 within
a year after the hardware upgrade.
The only reason we are currently running SQL Server 2000 Enterprise is
because our server has over 2 GB of memory. In 2005, the 2 GB memory
limitation has been removed for the Standard Edition so we are moving over to
the Standard Edition when we upgrade in a year.
So currently, we are looking to add two more SQL Server 2000 Ent licenses
for the addtional CPUs. Can I buy two SQL Server Standard licenses and use
the downgrade rights to temporarily run 2000 Enterprise?
"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
The best thing you can do is contact a Microsoft licensing specialist:
http://www.microsoft.com/licensing/index/worldwide.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
I never got an answer to taht when I asked a similar question, directly to
Microsoft.
BUT, they are the only ones who can really answer that.
Any advice given here, unless by an official MS person is worth what you're
paying for it.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
|||"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
So your question is can buy a SQL 2005 Standard License ($5,999 per proc,
retail) to and use it to run SQL 2000 Enterprise Edition ($25,000 per proc,
retail). Sounds unlikely.
David
|||"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ej3Tc2RXHHA.1432@.TK2MSFTNGP02.phx.gbl...
>
> "licensing_confusion" <licensing_confusion@.discussions.microsoft.com>
> wrote in message
> news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> So your question is can buy a SQL 2005 Standard License ($5,999 per proc,
> retail) to and use it to run SQL 2000 Enterprise Edition ($25,000 per
> proc, retail). Sounds unlikely.
> David
I think that's his question, which is similar to the case we had. 2
node-cluster with 8 gig of ram with 2 CPUs each.
Wanted to upgrade to 4 CPUs.
We're running SQL 2000, but plan on updating to SQL 2005.
Now, SQL 2005 Standard works on that config, but 2000 requires Enterprise.
So kind of puts some folks in a bind. :-/

Complicated Licensing Question

We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
CPU box. Along with this, we are hoping to upgrade to SQL Server 2005 withi
n
a year after the hardware upgrade.
The only reason we are currently running SQL Server 2000 Enterprise is
because our server has over 2 GB of memory. In 2005, the 2 GB memory
limitation has been removed for the Standard Edition so we are moving over t
o
the Standard Edition when we upgrade in a year.
So currently, we are looking to add two more SQL Server 2000 Ent licenses
for the addtional CPUs. Can I buy two SQL Server Standard licenses and use
the downgrade rights to temporarily run 2000 Enterprise?"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
The best thing you can do is contact a Microsoft licensing specialist:
http://www.microsoft.com/licensing/index/worldwide.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
I never got an answer to taht when I asked a similar question, directly to
Microsoft.
BUT, they are the only ones who can really answer that.
Any advice given here, unless by an official MS person is worth what you're
paying for it.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
So your question is can buy a SQL 2005 Standard License ($5,999 per proc,
retail) to and use it to run SQL 2000 Enterprise Edition ($25,000 per proc,
retail). Sounds unlikely.
David|||"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ej3Tc2RXHHA.1432@.TK2MSFTNGP02.phx.gbl...
>
> "licensing_confusion" <licensing_confusion@.discussions.microsoft.com>
> wrote in message
> news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> So your question is can buy a SQL 2005 Standard License ($5,999 per proc,
> retail) to and use it to run SQL 2000 Enterprise Edition ($25,000 per
> proc, retail). Sounds unlikely.
> David
I think that's his question, which is similar to the case we had. 2
node-cluster with 8 gig of ram with 2 CPUs each.
Wanted to upgrade to 4 CPUs.
We're running SQL 2000, but plan on updating to SQL 2005.
Now, SQL 2005 Standard works on that config, but 2000 requires Enterprise.
So kind of puts some folks in a bind. :-/

Complicated Licensing Question

We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
CPU box. Along with this, we are hoping to upgrade to SQL Server 2005 within
a year after the hardware upgrade.
The only reason we are currently running SQL Server 2000 Enterprise is
because our server has over 2 GB of memory. In 2005, the 2 GB memory
limitation has been removed for the Standard Edition so we are moving over to
the Standard Edition when we upgrade in a year.
So currently, we are looking to add two more SQL Server 2000 Ent licenses
for the addtional CPUs. Can I buy two SQL Server Standard licenses and use
the downgrade rights to temporarily run 2000 Enterprise?"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
The best thing you can do is contact a Microsoft licensing specialist:
http://www.microsoft.com/licensing/index/worldwide.mspx
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
I never got an answer to taht when I asked a similar question, directly to
Microsoft.
BUT, they are the only ones who can really answer that.
Any advice given here, unless by an official MS person is worth what you're
paying for it.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||"licensing_confusion" <licensing_confusion@.discussions.microsoft.com> wrote
in message news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a 4
> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
> within
> a year after the hardware upgrade.
> The only reason we are currently running SQL Server 2000 Enterprise is
> because our server has over 2 GB of memory. In 2005, the 2 GB memory
> limitation has been removed for the Standard Edition so we are moving over
> to
> the Standard Edition when we upgrade in a year.
> So currently, we are looking to add two more SQL Server 2000 Ent licenses
> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
> use
> the downgrade rights to temporarily run 2000 Enterprise?
So your question is can buy a SQL 2005 Standard License ($5,999 per proc,
retail) to and use it to run SQL 2000 Enterprise Edition ($25,000 per proc,
retail). Sounds unlikely.
David|||"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ej3Tc2RXHHA.1432@.TK2MSFTNGP02.phx.gbl...
>
> "licensing_confusion" <licensing_confusion@.discussions.microsoft.com>
> wrote in message
> news:0D3492D5-F10D-435D-8FC0-293BCB09C94F@.microsoft.com...
>> We are currently upgrading our 2 CPU SQL Server 2000 Enterprise box to a
>> 4
>> CPU box. Along with this, we are hoping to upgrade to SQL Server 2005
>> within
>> a year after the hardware upgrade.
>> The only reason we are currently running SQL Server 2000 Enterprise is
>> because our server has over 2 GB of memory. In 2005, the 2 GB memory
>> limitation has been removed for the Standard Edition so we are moving
>> over to
>> the Standard Edition when we upgrade in a year.
>> So currently, we are looking to add two more SQL Server 2000 Ent licenses
>> for the addtional CPUs. Can I buy two SQL Server Standard licenses and
>> use
>> the downgrade rights to temporarily run 2000 Enterprise?
> So your question is can buy a SQL 2005 Standard License ($5,999 per proc,
> retail) to and use it to run SQL 2000 Enterprise Edition ($25,000 per
> proc, retail). Sounds unlikely.
> David
I think that's his question, which is similar to the case we had. 2
node-cluster with 8 gig of ram with 2 CPUs each.
Wanted to upgrade to 4 CPUs.
We're running SQL 2000, but plan on updating to SQL 2005.
Now, SQL 2005 Standard works on that config, but 2000 requires Enterprise.
So kind of puts some folks in a bind. :-/

Compatibility Level

Clicking "Details" from the drop-down menu that lists all the databases in
the Query Analyzer (in SQL Server 2000) pops out a dialog box where all the
databases are listed along with their Compatibility Level. What is this
Compatibility Level? Does this mean backward compatibility i.e. SQL Server
2000's compatibility with SQL Server 7.0? Also why is the Compatibility
Level for all databases 70 - what does it signify? Why not some number other
than 70?
Installing SQL Server 7.0 along with SQL Server 2000 on the same machine -
is that a sane approach or should such a situation be avoided? What problems
could arise if both versions of SQL Server are installed on the same
machine?
Thanks,
Arpan>> What is this Compatibility Level? <<
It is a DBMS specific internal value, that keep certain database behaviors
to be compatible with the specified DBMS version. The values are 80, 70, 65,
or 60 for SQL 2000, SQL 7.0, SQL 6.5 and SQL 6.0 respectively.
For example when you upgrade SQL Server from version 6.5 to version 7.0, the
compatibility will not get updated. You will have to use the procedure
sp_dbcmptlevel to get it to 70. Without this compatibility level, certain
features specific to SQL 7.0 like TOP clause will not work properly. See
details about sp_dbcmptlevel in SQL Server Books Online.
>> Also why is the Compatibility Level for all databases 70 - what does it
signify? Why not some number other than 70? <<
It simply means, this level is specific to SQL Server version 7.0.
>> Installing SQL Server 7.0 along with SQL Server 2000 on the same
machine - is that a sane approach or should such ... <<
You can keep an installation of SQL Server version 7.0 intact on your
computer and also install a named instance of SQL Server 2000 on the same
computer. Details on how to proceed can be found in SQL Server Books Online.
--
- Anith
( Please reply to newsgroups only )|||Thanks, Anith, for your input. What do you mean by "named instance" of SQL
Server 2000?
Regards,
Arpan
"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:OuiU2ODlDHA.2244@.TK2MSFTNGP12.phx.gbl...
> >> What is this Compatibility Level? <<
> It is a DBMS specific internal value, that keep certain database behaviors
> to be compatible with the specified DBMS version. The values are 80, 70,
65,
> or 60 for SQL 2000, SQL 7.0, SQL 6.5 and SQL 6.0 respectively.
> For example when you upgrade SQL Server from version 6.5 to version 7.0,
the
> compatibility will not get updated. You will have to use the procedure
> sp_dbcmptlevel to get it to 70. Without this compatibility level, certain
> features specific to SQL 7.0 like TOP clause will not work properly. See
> details about sp_dbcmptlevel in SQL Server Books Online.
> >> Also why is the Compatibility Level for all databases 70 - what does it
> signify? Why not some number other than 70? <<
> It simply means, this level is specific to SQL Server version 7.0.
> >> Installing SQL Server 7.0 along with SQL Server 2000 on the same
> machine - is that a sane approach or should such ... <<
> You can keep an installation of SQL Server version 7.0 intact on your
> computer and also install a named instance of SQL Server 2000 on the same
> computer. Details on how to proceed can be found in SQL Server Books
Online.
> --
> - Anith
> ( Please reply to newsgroups only )
>|||Refer to :
http://msdn.microsoft.com/library/en-us/architec/8_ar_cs_9i5u.asp
--
- Anith
( Please reply to newsgroups only )