Friday, March 30, 2012
Impact of migration on Windows authenticated SQL user account
domain to the new AD domain. These SQL servers have many
Windows authenticated SQL user account. As I understand,
once the logins have been defined as <NT4
domain>\<username>, we cant change it to <AD
domain>\<username>, unless we delete the logins and
recreate it again?
The article (http://support.microsoft.com/default.aspx?
scid=kb;EN-US;240872) seems to mention the moving of
database from one server to another. However in my case,
the database will remain in the same server, just that
the domain will change...hence affecting all the
previously created Windows authenticated SQL user
accounts.
Is there any step-by-step document on how to do security
translation for these SQL user accounts after the
migration to the new domain?
>--Original Message--
>Message unavailableSomething like this ... it's been awhile ... SQL Server maps SIDS to SQL Se
rver id's. There's a technique/procedure that help to remap these when like
your self domain SIDS don't match up with SQL Server id's. Sorry, but I do
nt' do it often enough to r
emember exactly.
Immediate update/Queued update problem
replication on my test servers. I go through the wizards and create the
publication using the advanced mode and set it up. It appears to work fine.
When I create the subscription, nothing happens. I cannot get the inital
snapshot to work and it will not create the triggers and stored procedures.
Anyone have any ideas?
Connect to your publisher in EM, expand Replication Monitor, expand the
replication agents, expand the distribution agent folder, locate the
distribution agent for your publication, right click on it, select Agent
Properties and change the job owner to sa.
Right click on your distribution agent and restart it. You may have to also
do this for the snapshot agent.
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:5289270A-7B92-45F6-9887-A78D66ACB061@.microsoft.com...
> I'm having a problem creating immediate update/queued update transactional
> replication on my test servers. I go through the wizards and create the
> publication using the advanced mode and set it up. It appears to work
> fine.
> When I create the subscription, nothing happens. I cannot get the inital
> snapshot to work and it will not create the triggers and stored
> procedures.
> Anyone have any ideas?
|||Thank for your help.
I found that there was an issue with the computer name. The computer had
gotten its name changed and after rectifying that the triggers were written.
So.. Now I have a problem on the subscriber writing back in a two phase
commit back to the publisher. I get an error during the insert that indicates
that the sa password cannot connect. I traced the call and I see the call to
openserver where the sa login is used and the password is set as an empty
string. I cannot find where to set the login and password for the writeback.
Could someone help me out?
"Hilary Cotter" wrote:
> Connect to your publisher in EM, expand Replication Monitor, expand the
> replication agents, expand the distribution agent folder, locate the
> distribution agent for your publication, right click on it, select Agent
> Properties and change the job owner to sa.
> Right click on your distribution agent and restart it. You may have to also
> do this for the snapshot agent.
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:5289270A-7B92-45F6-9887-A78D66ACB061@.microsoft.com...
>
>
Wednesday, March 7, 2012
IIS + SQL (Not enough storage is available to complete this operation)
operation) from one of our servers which on win2000 sp 4 iis5.0 (all hotfix
installed) sql server sp4. mdac 2.81. It occures random and we could not
find the error reason. When the error occured the server cpu or mem or I/O
usage is normal and I try to find out from internet and some says check the
mdac verision registery size or oracle etc. they do not indicate our
problem. we use adodb connection to connect sql server and all of them
close after the proccess also all recordset are close and set nothing. The
server transaction is kind of high but there are several indexes so it not
seems a problem there. When IIS restarts the problem solves but all users
sesions are closed. Have you ever met the error before or what can be
problem. Any advice would be helpful
Thanks"tolgay" <tgul@.tgul.com> wrote in message
news:uibNfg0qGHA.4676@.TK2MSFTNGP03.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could not
> find the error reason. When the error occured the server cpu or mem or I/O
> usage is normal and I try to find out from internet and some says check
the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of them
> close after the proccess also all recordset are close and set nothing. The
> server transaction is kind of high but there are several indexes so it not
> seems a problem there. When IIS restarts the problem solves but all users
> sesions are closed. Have you ever met the error before or what can be
> problem. Any advice would be helpful
> Thanks
>
and the event error log says what?|||Do you see any errors in the Event Log (particularly about non-paged or
paged pool depletion)?
Cheers
Ken
"tolgay" <tgul@.tgul.com> wrote in message
news:uibNfg0qGHA.4676@.TK2MSFTNGP03.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
> this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
> hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could not
> find the error reason. When the error occured the server cpu or mem or I/O
> usage is normal and I try to find out from internet and some says check
> the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of them
> close after the proccess also all recordset are close and set nothing. The
> server transaction is kind of high but there are several indexes so it not
> seems a problem there. When IIS restarts the problem solves but all users
> sesions are closed. Have you ever met the error before or what can be
> problem. Any advice would be helpful
> Thanks
>|||"tolgay" <tgul@.tgul.com> wrote in message
news:uibNfg0qGHA.4676@.TK2MSFTNGP03.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
> this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
> hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could not
> find the error reason. When the error occured the server cpu or mem or I/O
> usage is normal and I try to find out from internet and some says check
> the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of them
> close after the proccess also all recordset are close and set nothing. The
> server transaction is kind of high but there are several indexes so it not
> seems a problem there. When IIS restarts the problem solves but all users
> sesions are closed. Have you ever met the error before or what can be
> problem. Any advice would be helpful
How much space is free in your database and the tempdb database? Are the
transaction logs full or not large enough? Are there any errors in the SQL
logs?
kind regards,
Karl Levinson, CISSP, CCSA, MCSE [MS MVP]
--
Microsoft Security FAQ:
http://securityadmin.info|||There is nothing in to event log even a warning also temp db size quite
large and the db transaction log is about 2 gbyte and %75 is free and there
is nothing also in sql server logs.
Thanks
"tolgay" <tgul@.tgul.com> wrote in message
news:uibNfg0qGHA.4676@.TK2MSFTNGP03.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could not
> find the error reason. When the error occured the server cpu or mem or I/O
> usage is normal and I try to find out from internet and some says check
the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of them
> close after the proccess also all recordset are close and set nothing. The
> server transaction is kind of high but there are several indexes so it not
> seems a problem there. When IIS restarts the problem solves but all users
> sesions are closed. Have you ever met the error before or what can be
> problem. Any advice would be helpful
> Thanks
>
IIS + SQL (Not enough storage is available to complete this operation)
operation) from one of our servers which on win2000 sp 4 iis5.0 (all hotfix
installed) sql server sp4. mdac 2.81. It occures random and we could not
find the error reason. When the error occured the server cpu or mem or I/O
usage is normal and I try to find out from internet and some says check the
mdac verision registery size or oracle etc. they do not indicate our
problem. we use adodb connection to connect sql server and all of them
close after the proccess also all recordset are close and set nothing. The
server transaction is kind of high but there are several indexes so it not
seems a problem there. When IIS restarts the problem solves but all users
sesions are closed. Have you ever met the error before or what can be
problem. Any advice would be helpful
Thanks"tolgay" <tgul@.tgul.com> wrote in message
news:uibNfg0qGHA.4676@.TK2MSFTNGP03.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could not
> find the error reason. When the error occured the server cpu or mem or I/O
> usage is normal and I try to find out from internet and some says check
the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of them
> close after the proccess also all recordset are close and set nothing. The
> server transaction is kind of high but there are several indexes so it not
> seems a problem there. When IIS restarts the problem solves but all users
> sesions are closed. Have you ever met the error before or what can be
> problem. Any advice would be helpful
> Thanks
>
and the event error log says what?|||Do you see any errors in the Event Log (particularly about non-paged or
paged pool depletion)?
Cheers
Ken
"tolgay" <tgul@.tgul.com> wrote in message
news:uibNfg0qGHA.4676@.TK2MSFTNGP03.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
> this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
> hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could not
> find the error reason. When the error occured the server cpu or mem or I/O
> usage is normal and I try to find out from internet and some says check
> the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of them
> close after the proccess also all recordset are close and set nothing. The
> server transaction is kind of high but there are several indexes so it not
> seems a problem there. When IIS restarts the problem solves but all users
> sesions are closed. Have you ever met the error before or what can be
> problem. Any advice would be helpful
> Thanks
>|||"tolgay" <tgul@.tgul.com> wrote in message
news:uibNfg0qGHA.4676@.TK2MSFTNGP03.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
> this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
> hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could not
> find the error reason. When the error occured the server cpu or mem or I/O
> usage is normal and I try to find out from internet and some says check
> the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of them
> close after the proccess also all recordset are close and set nothing. The
> server transaction is kind of high but there are several indexes so it not
> seems a problem there. When IIS restarts the problem solves but all users
> sesions are closed. Have you ever met the error before or what can be
> problem. Any advice would be helpful
How much space is free in your database and the tempdb database? Are the
transaction logs full or not large enough? Are there any errors in the SQL
logs?
--
kind regards,
Karl Levinson, CISSP, CCSA, MCSE [MS MVP]
--
Microsoft Security FAQ:
http://securityadmin.info|||There is nothing in to event log even a warning also temp db size quite
large and the db transaction log is about 2 gbyte and %75 is free and there
is nothing also in sql server logs.
Thanks
"tolgay" <tgul@.tgul.com> wrote in message
news:uibNfg0qGHA.4676@.TK2MSFTNGP03.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could not
> find the error reason. When the error occured the server cpu or mem or I/O
> usage is normal and I try to find out from internet and some says check
the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of them
> close after the proccess also all recordset are close and set nothing. The
> server transaction is kind of high but there are several indexes so it not
> seems a problem there. When IIS restarts the problem solves but all users
> sesions are closed. Have you ever met the error before or what can be
> problem. Any advice would be helpful
> Thanks
>|||Sometimes we got an error (Not enough storage is available to complete
this
operation) from one of our servers which on win2000 sp 4 iis5.0 (all
hotfix
installed) sql server sp4. mdac 2.81. It occures random and we could not
find the error reason. When the error occured the server cpu or mem or I/O
usage is normal and I try to find out from internet and some says check
the
mdac verision registery size or oracle etc. they do not indicate our
problem. we use adodb connection to connect sql server and all of them
close after the proccess also all recordset are close and set nothing. The
server transaction is kind of high but there are several indexes so it not
seems a problem there. When IIS restarts the problem solves but all users
sesions are closed. Have you ever met the error before or what can be
problem. Any advice would be helpful
There is nothing in to event log even a warning also temp db size quite
large and the db transaction log is about 2 gbyte and %75 is free and there
is nothing also in sql server logs.|||tolgay wrote:
> Sometimes we got an error (Not enough storage is available to
> complete this
> operation) from one of our servers which on win2000 sp 4 iis5.0 (all
> hotfix
> installed) sql server sp4. mdac 2.81. It occures random and we could
> not find the error reason. When the error occured the server cpu or
> mem or I/O usage is normal and I try to find out from internet and
> some says check the
> mdac verision registery size or oracle etc. they do not indicate our
> problem. we use adodb connection to connect sql server and all of
> them close after the proccess also all recordset are close and set
> nothing. The server transaction is kind of high but there are
> several indexes so it not seems a problem there. When IIS restarts
> the problem solves but all users sesions are closed. Have you ever
> met the error before or what can be problem. Any advice would be
> helpful
> There is nothing in to event log even a warning also temp db size
> quite large and the db transaction log is about 2 gbyte and %75 is
> free and there is nothing also in sql server logs.
We were seeing this problem and tracked ours back to a huge number of
active directory groups - we use the following in a .reg file to
increase the size - works ok after reboot then - it affected all sorts
of things - we couldnt add a pc to the domain without seeing this error.
Copy the following into notepad and save with name of your choosing,
ours in mtsize.reg then run it to make the change in the registry.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parame
ters]
"MaxTokenSize"=dword:00010000
Sunday, February 19, 2012
Ignoring Source Field
I am implementing a Transactional Replication btwn two SQL 2000 servers, which is using Data Transform services (DTS package) to manipulate the data. I need to ignore a source column from replication but that column field value needs to be appended with other field column.
For ex. Let two source fields be named FirstName and LastName. In the target database i need to merge those field values into a Single field called CustomerName. Also i don't want the two source fields to be replicated in the target.
I tried to ignore the field by unchecking the Column Transformation and Mapping screen, but then unable to append the field value to the other field.
Is there any other way to do the above?
Thanks in advance.
urs,
T. Jayakumar
I don't think there is a way to use a field in a transformation but not include it in the package data.
Phil Garding