BETWEEN A AND F

Hi All.
Intervals on varchar fields.
I just want to pick all customers from my DB who has Customernames starting
with A, b, c, d, e, f. Some kind of BETWEEN A AND F. (Starting letters).
Any ideas.
Even better. I have the query ... WHERE CustomerName LIKE @.CustomerName. Is
there any combinations of %, <, > or any other characters that can give me
all customers between A and F. (E.g...WHERE CustomerName LIKE 'A-F' or
something...
Thanx all
GeirLook up wildcards in the books online; you basically want a variation
of :
WHERE CustomerName Like '[a-f]%'
Stu|||Just what I was looking for. Thanx a lot!
Still learning.....:-)
-gh
"Stu" <stuart.ainsworth@.gmail.com> wrote in message
news:1126525507.534946.152760@.f14g2000cwb.googlegroups.com...
> Look up wildcards in the books online; you basically want a variation
> of :
> WHERE CustomerName Like '[a-f]%'
> Stu
>|||Been there :)
Books Online will be your best friend if you're trying to learn the
distinctive characteristics of SQL Server. Of course, if means you
have to know what you're looking for because it's an encyclopedia, not
a textbook.
Stu

Bestpractice for varying outputformat

Hello

I need an advice for an easy maintainable and highly flexible solution using SSIS. We're supplying our customers with an exportservice. The data is extracted from different tables, all with the same tableschema, fairly easy to create a foreach-container and iterate through the tablenames and extract data and use a flatfile destination to write it to...

But the not so easy part is to have different exportformats and still be using only one package. I could maybe use different ConnectionManagers for the FlatFileDestination, but that's not a very easy maintainable solution in my world. Our Customers will soon demand a webinterface where they can select necessary columns and apply different formatting for example they would demand the datetime to be '2006-12-24' or maybe '12/24/2006' etc. for alot of the available columns.

Any good suggestion on how to accomplish such a task?

Kind regards

Dot.Help any advices?

Best way to upgrade for SQLServer2000 standard to Enterprice

Hi all.
One of our customers need SQL to run on more than 2GB of memory. They are
running on SQL2000 standard edition and therefor need to upgrade to
Enterprice edition. Is it just to install then new CD's over the old system
or do we need to do it as a reinstall of the server and some backup/restore
of the database? Our customers talked about some wizards to do this. Any
"best practice" advice anyone?
Thanx
GeirGeir ,
it's really simple. Just run the setup select the option upgrade and if
necessary add some (new) components. It shouldn't take more tha 2
minutes and if I there's no need to reapply service packs.
But as always, make sure you have a backup of all your databases
including the system databases before you start.
Markus|||Hi
The amount of memory you can use also depends on the version of the OS you
are using, which you haven't specified.
If you haven't already check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
http://www.sql-server-performance.com/awe_memory.asp
http://support.microsoft.com/kb/274750
You should be able to install over your existing system, make sure that you
have backups of all your databases and a recovery plan for each stage in the
process, so that you know exactly how to get your system back up and running
in the event of problems being encountered.
John
"Geir Holme" wrote:
> Hi all.
> One of our customers need SQL to run on more than 2GB of memory. They are
> running on SQL2000 standard edition and therefor need to upgrade to
> Enterprice edition. Is it just to install then new CD's over the old system
> or do we need to do it as a reinstall of the server and some backup/restore
> of the database? Our customers talked about some wizards to do this. Any
> "best practice" advice anyone?
> Thanx
> Geir
>
>

Best way to upgrade for SQLServer2000 standard to Enterprice

Hi all.
One of our customers need SQL to run on more than 2GB of memory. They are
running on SQL2000 standard edition and therefor need to upgrade to
Enterprice edition. Is it just to install then new CD's over the old system
or do we need to do it as a reinstall of the server and some backup/restore
of the database? Our customers talked about some wizards to do this. Any
"best practice" advice anyone?
Thanx
GeirGeir ,
it's really simple. Just run the setup select the option upgrade and if
necessary add some (new) components. It shouldn't take more tha 2
minutes and if I there's no need to reapply service packs.
But as always, make sure you have a backup of all your databases
including the system databases before you start.
Markus|||Hi
The amount of memory you can use also depends on the version of the OS you
are using, which you haven't specified.
If you haven't already check out:
http://msdn.microsoft.com/library/d...br />
8dbn.asp
http://www.sql-server-performance.com/awe_memory.asp
http://support.microsoft.com/kb/274750
You should be able to install over your existing system, make sure that you
have backups of all your databases and a recovery plan for each stage in the
process, so that you know exactly how to get your system back up and running
in the event of problems being encountered.
John
"Geir Holme" wrote:

> Hi all.
> One of our customers need SQL to run on more than 2GB of memory. They are
> running on SQL2000 standard edition and therefor need to upgrade to
> Enterprice edition. Is it just to install then new CD's over the old syste
m
> or do we need to do it as a reinstall of the server and some backup/restor
e
> of the database? Our customers talked about some wizards to do this. Any
> "best practice" advice anyone?
> Thanx
> Geir
>
>|||Geir ,
it's really simple. Just run the setup select the option upgrade and if
necessary add some (new) components. It shouldn't take more tha 2
minutes and if I there's no need to reapply service packs.
But as always, make sure you have a backup of all your databases
including the system databases before you start.
Markus|||Hi
The amount of memory you can use also depends on the version of the OS you
are using, which you haven't specified.
If you haven't already check out:
http://msdn.microsoft.com/library/d...br />
8dbn.asp
http://www.sql-server-performance.com/awe_memory.asp
http://support.microsoft.com/kb/274750
You should be able to install over your existing system, make sure that you
have backups of all your databases and a recovery plan for each stage in the
process, so that you know exactly how to get your system back up and running
in the event of problems being encountered.
John
"Geir Holme" wrote:

> Hi all.
> One of our customers need SQL to run on more than 2GB of memory. They are
> running on SQL2000 standard edition and therefor need to upgrade to
> Enterprice edition. Is it just to install then new CD's over the old syste
m
> or do we need to do it as a reinstall of the server and some backup/restor
e
> of the database? Our customers talked about some wizards to do this. Any
> "best practice" advice anyone?
> Thanx
> Geir
>
>

Best way to extract part of a db and deploy it

Hi,
I'm using MSSQL2k and I have some customers in a customer table. I want to write a webapp and offer them the possibility to teach them using the app while having telephone contact with them. They can use the app on my server for some time and add data to it.
After a while when someone wants to buy the app I would like to distribute the app as an Intranet app to their own server and let them have the data they already have wrote into the db on my server.
Because there will be some customers with much data I'd like some guidance in how to plan the database to easily extract their own data and create a new db polutated with their data.
KennethThe easiest way that comes to mind would be to add some sort ofcustomer identifer to the primary database, and when you're ready toexport, run a script that copies the rows with that customer identiferfrom the primary database to a blank model database specific for thatcustomer.
All you'd have to do is write the script one, and them plug in the customer identifer when you're ready to export.