Hello,
After one of my clients had to close down his business, he has asked me to
liquidate some items to cover my unpaid invoices. One of those items is a
copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
installed/activated. This is OEM and it was purchased with a new server. Am
I correct in my assumption that I have to sell the software and the original
server together? Can I even sell it at all?
Any help appreciated.
Thanks,
ATL IT Guy
I'm pretty sure you can sell the server along with the OEM software that came
with it. At least I've worked with companies that have done so. But you are
correct, you can't sell that copy of SQL Server without the server it came
on. I would verify with the server vendor or a MS license reseller like CDW
or someone simliar before you do anything though.
"ATL IT Guy" wrote:
> Hello,
> After one of my clients had to close down his business, he has asked me to
> liquidate some items to cover my unpaid invoices. One of those items is a
> copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
> installed/activated. This is OEM and it was purchased with a new server. Am
> I correct in my assumption that I have to sell the software and the original
> server together? Can I even sell it at all?
> Any help appreciated.
> Thanks,
> ATL IT Guy
Showing posts with label clients. Show all posts
Showing posts with label clients. Show all posts
Friday, March 30, 2012
Question about selling license
Hello,
After one of my clients had to close down his business, he has asked me to
liquidate some items to cover my unpaid invoices. One of those items is a
copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
installed/activated. This is OEM and it was purchased with a new server. A
m
I correct in my assumption that I have to sell the software and the original
server together? Can I even sell it at all?
Any help appreciated.
Thanks,
ATL IT GuyI'm pretty sure you can sell the server along with the OEM software that cam
e
with it. At least I've worked with companies that have done so. But you are
correct, you can't sell that copy of SQL Server without the server it came
on. I would verify with the server vendor or a MS license reseller like CDW
or someone simliar before you do anything though.
"ATL IT Guy" wrote:
> Hello,
> After one of my clients had to close down his business, he has asked me to
> liquidate some items to cover my unpaid invoices. One of those items is a
> copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
> installed/activated. This is OEM and it was purchased with a new server.
Am
> I correct in my assumption that I have to sell the software and the origin
al
> server together? Can I even sell it at all?
> Any help appreciated.
> Thanks,
> ATL IT Guy
After one of my clients had to close down his business, he has asked me to
liquidate some items to cover my unpaid invoices. One of those items is a
copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
installed/activated. This is OEM and it was purchased with a new server. A
m
I correct in my assumption that I have to sell the software and the original
server together? Can I even sell it at all?
Any help appreciated.
Thanks,
ATL IT GuyI'm pretty sure you can sell the server along with the OEM software that cam
e
with it. At least I've worked with companies that have done so. But you are
correct, you can't sell that copy of SQL Server without the server it came
on. I would verify with the server vendor or a MS license reseller like CDW
or someone simliar before you do anything though.
"ATL IT Guy" wrote:
> Hello,
> After one of my clients had to close down his business, he has asked me to
> liquidate some items to cover my unpaid invoices. One of those items is a
> copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
> installed/activated. This is OEM and it was purchased with a new server.
Am
> I correct in my assumption that I have to sell the software and the origin
al
> server together? Can I even sell it at all?
> Any help appreciated.
> Thanks,
> ATL IT Guy
Question about selling license
Hello,
After one of my clients had to close down his business, he has asked me to
liquidate some items to cover my unpaid invoices. One of those items is a
copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
installed/activated. This is OEM and it was purchased with a new server. Am
I correct in my assumption that I have to sell the software and the original
server together? Can I even sell it at all?
Any help appreciated.
Thanks,
ATL IT GuyI'm pretty sure you can sell the server along with the OEM software that came
with it. At least I've worked with companies that have done so. But you are
correct, you can't sell that copy of SQL Server without the server it came
on. I would verify with the server vendor or a MS license reseller like CDW
or someone simliar before you do anything though.
"ATL IT Guy" wrote:
> Hello,
> After one of my clients had to close down his business, he has asked me to
> liquidate some items to cover my unpaid invoices. One of those items is a
> copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
> installed/activated. This is OEM and it was purchased with a new server. Am
> I correct in my assumption that I have to sell the software and the original
> server together? Can I even sell it at all?
> Any help appreciated.
> Thanks,
> ATL IT Guy
After one of my clients had to close down his business, he has asked me to
liquidate some items to cover my unpaid invoices. One of those items is a
copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
installed/activated. This is OEM and it was purchased with a new server. Am
I correct in my assumption that I have to sell the software and the original
server together? Can I even sell it at all?
Any help appreciated.
Thanks,
ATL IT GuyI'm pretty sure you can sell the server along with the OEM software that came
with it. At least I've worked with companies that have done so. But you are
correct, you can't sell that copy of SQL Server without the server it came
on. I would verify with the server vendor or a MS license reseller like CDW
or someone simliar before you do anything though.
"ATL IT Guy" wrote:
> Hello,
> After one of my clients had to close down his business, he has asked me to
> liquidate some items to cover my unpaid invoices. One of those items is a
> copy of MS SQL 2005 Workgroup 32 bit. Still shrink wrapped and never
> installed/activated. This is OEM and it was purchased with a new server. Am
> I correct in my assumption that I have to sell the software and the original
> server together? Can I even sell it at all?
> Any help appreciated.
> Thanks,
> ATL IT Guy
Wednesday, March 28, 2012
Question about querying across servers
Hi,
We have 8 sites running each one a SQL Server.
Clients can connect to any of these sites to get information.
Now we want to have an 'extra site'. Clients that connect to this site
will be able to get information from the previous 8 sites. I mean, this
extra site, will contain all the data of the other 8 sites.
Ex.
Site 1 has a table called 'Persons' with a record called 'John'
Site 3 has a table called 'Persons' with a record 'Peter'
If I query for all persons on site 1, I get 'John'
However, If I query for all persons in that extra site, I get 'John' and
'Peter'
1. What is the best way to do this? I have been looking at linked
servers but it's not clear to me... I'm not sure if this is a solution.
2. Should I transfer all the data phisically from Site1->Extra Site,
Site2->Extra site... ?
3. On the other hand, how do I distinguish primary keys? Let's suppose that
primary key for 'John' on site 1 is 1000, and 'Peter' on site 3 is also
1000. Could this cause some problems?
Thanks a lot.Will the New sites will be added on a periodic basis , or the developer is
adding settings for new sites ?
U can use linked servers for this process than replication
first register the link server , then in queries use the
linkserver..dbname.table for querying
thanks
"Star" wrote:
> Hi,
> We have 8 sites running each one a SQL Server.
> Clients can connect to any of these sites to get information.
> Now we want to have an 'extra site'. Clients that connect to this site
> will be able to get information from the previous 8 sites. I mean, this
> extra site, will contain all the data of the other 8 sites.
> Ex.
> Site 1 has a table called 'Persons' with a record called 'John'
> Site 3 has a table called 'Persons' with a record 'Peter'
> If I query for all persons on site 1, I get 'John'
> However, If I query for all persons in that extra site, I get 'John' and
> 'Peter'
> 1. What is the best way to do this? I have been looking at linked
> servers but it's not clear to me... I'm not sure if this is a solution.
> 2. Should I transfer all the data phisically from Site1->Extra Site,
> Site2->Extra site... ?
> 3. On the other hand, how do I distinguish primary keys? Let's suppose tha
t
> primary key for 'John' on site 1 is 1000, and 'Peter' on site 3 is also
> 1000. Could this cause some problems?
> Thanks a lot.
>
We have 8 sites running each one a SQL Server.
Clients can connect to any of these sites to get information.
Now we want to have an 'extra site'. Clients that connect to this site
will be able to get information from the previous 8 sites. I mean, this
extra site, will contain all the data of the other 8 sites.
Ex.
Site 1 has a table called 'Persons' with a record called 'John'
Site 3 has a table called 'Persons' with a record 'Peter'
If I query for all persons on site 1, I get 'John'
However, If I query for all persons in that extra site, I get 'John' and
'Peter'
1. What is the best way to do this? I have been looking at linked
servers but it's not clear to me... I'm not sure if this is a solution.
2. Should I transfer all the data phisically from Site1->Extra Site,
Site2->Extra site... ?
3. On the other hand, how do I distinguish primary keys? Let's suppose that
primary key for 'John' on site 1 is 1000, and 'Peter' on site 3 is also
1000. Could this cause some problems?
Thanks a lot.Will the New sites will be added on a periodic basis , or the developer is
adding settings for new sites ?
U can use linked servers for this process than replication
first register the link server , then in queries use the
linkserver..dbname.table for querying
thanks
"Star" wrote:
> Hi,
> We have 8 sites running each one a SQL Server.
> Clients can connect to any of these sites to get information.
> Now we want to have an 'extra site'. Clients that connect to this site
> will be able to get information from the previous 8 sites. I mean, this
> extra site, will contain all the data of the other 8 sites.
> Ex.
> Site 1 has a table called 'Persons' with a record called 'John'
> Site 3 has a table called 'Persons' with a record 'Peter'
> If I query for all persons on site 1, I get 'John'
> However, If I query for all persons in that extra site, I get 'John' and
> 'Peter'
> 1. What is the best way to do this? I have been looking at linked
> servers but it's not clear to me... I'm not sure if this is a solution.
> 2. Should I transfer all the data phisically from Site1->Extra Site,
> Site2->Extra site... ?
> 3. On the other hand, how do I distinguish primary keys? Let's suppose tha
t
> primary key for 'John' on site 1 is 1000, and 'Peter' on site 3 is also
> 1000. Could this cause some problems?
> Thanks a lot.
>
Subscribe to:
Posts (Atom)