Hello,
I am trying to setup a push subscription between two SQL 2000 Servers using
the Push Subscription Wizard through Enterprise Manager. After clicking
"Finish" at the end of the wizard, Enterprise Manager hangs at the first
step "Enabling this server as a subscriber". Can anyone help me identify
the problem, I can't see anything in the logs.
Thanks,
Ben Gibson
Ben,
additionally, you could use sp_who2 and dbcc inputbuffer(spid) as per usual
to get some more info.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Monday, March 26, 2012
Push subscription failing
SQL Server Enterprise Manager encountered errors creating push subscriptions
for the following Subscribers:
JANUS: Error 208: Invalid object name 'sysextendedarticlesview'.
The error above shows up each time that I attempt to push the subscription.
THe view sysextendedarticlesview exist in the publisher database. DOes
anybody know how to fix this thing? THanks
issue this on the subscriber in the subscription database.
create view dbo.sysextendedarticlesview
as
select * from sysarticles
union all
select artid, NULL, creation_script, NULL, description,
dest_object, NULL, NULL, NULL, name, objid, pubid,
pre_creation_cmd, status, NULL, type, NULL,
schema_option, dest_owner from sysschemaarticles
go
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pete Ocasio" <pete.ocasio@.execupay.com> wrote in message
news:OKRoJYKsEHA.2788@.TK2MSFTNGP09.phx.gbl...
> SQL Server Enterprise Manager encountered errors creating push
subscriptions
> for the following Subscribers:
> JANUS: Error 208: Invalid object name 'sysextendedarticlesview'.
> The error above shows up each time that I attempt to push the
subscription.
> THe view sysextendedarticlesview exist in the publisher database. DOes
> anybody know how to fix this thing? THanks
>
sql
for the following Subscribers:
JANUS: Error 208: Invalid object name 'sysextendedarticlesview'.
The error above shows up each time that I attempt to push the subscription.
THe view sysextendedarticlesview exist in the publisher database. DOes
anybody know how to fix this thing? THanks
issue this on the subscriber in the subscription database.
create view dbo.sysextendedarticlesview
as
select * from sysarticles
union all
select artid, NULL, creation_script, NULL, description,
dest_object, NULL, NULL, NULL, name, objid, pubid,
pre_creation_cmd, status, NULL, type, NULL,
schema_option, dest_owner from sysschemaarticles
go
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pete Ocasio" <pete.ocasio@.execupay.com> wrote in message
news:OKRoJYKsEHA.2788@.TK2MSFTNGP09.phx.gbl...
> SQL Server Enterprise Manager encountered errors creating push
subscriptions
> for the following Subscribers:
> JANUS: Error 208: Invalid object name 'sysextendedarticlesview'.
> The error above shows up each time that I attempt to push the
subscription.
> THe view sysextendedarticlesview exist in the publisher database. DOes
> anybody know how to fix this thing? THanks
>
sql
push subscribe problem(String data, right truncation)
os : windows2000 server
sql : sql2000 enterprise edition
mdac version is same each other.. version 2.8
i have two sql server(devsrv and parkchangsoon)
i configured the transaction replication
parkchangsoon : publisher,distributer
devsrv : subscriber
articles are 10 of all tables and 10 of all procedures
at first
the snapshot agent status is succss and the last action is "the snapshot of
24 articles have created"
after that
the distributer agent is pushing to devsrv (subscriber system)
but the distributer agent status is fail and the last action is "could not
bulk copy to 'jobs' table"
so..
i saw the distributer agent error information
publisher(P) : parkchangsoon agent(A) : PARKCHANGSOON-albaroot_3th-DEVSRV-5
publish(U) : albaroot_3th subscribe : DEVSRV:albaroot_3th
error message(E) : could not bulk copy to 'jobs' table
last command (V) : select * from workey_jobs where 1=1
error infomation(E) : String data, right truncation
source : DEVSRV(ODBC); eror number : 22001
below is the schema of the jobs table
CREATE TABLE [devuser].[Jobs] (
[seq] [int] IDENTITY (1, 1) NOT NULL ,
[title] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[findPrsn] [tinyint] NOT NULL ,
[ageZn] [varchar] (50) COLLATE Korean_Wansung_CI_AS NULL ,
[applyRght] [varchar] (4000) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[emplrId] [varchar] (30) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[readCnt] [int] NOT NULL ,
[sido] [tinyint] NOT NULL ,
[workTyp] [char] (8) COLLATE Korean_Wansung_CI_AS NULL ,
[applyDcmnt] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[findYmd2] [smalldatetime] NOT NULL ,
[gugun] [tinyint] NOT NULL ,
[finishYmd] [bit] NOT NULL ,
[ymd] [smalldatetime] NOT NULL ,
[particular] [char] (1) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[position] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[makeup_color] [bit] NOT NULL ,
[makeup_icon] [bit] NOT NULL ,
[makeup_marquee] [bit] NOT NULL ,
[logo] [varchar] (50) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[endymd] [smalldatetime] NOT NULL ,
[jobtype1] [tinyint] NULL ,
[jobtype2] [tinyint] NULL ,
[jobtype3] [tinyint] NULL ,
[paytype] [char] (4) COLLATE Korean_Wansung_CI_AS NULL ,
[pay1] [int] NULL ,
[pay2] [bit] NULL ,
[suprise] [tinyint] NULL ,
[ts] [timestamp] NULL ,
[visible] [bit] NULL ,
[createdYmd] [smalldatetime] NULL ,
[msrepl_tran_version] [uniqueidentifier] NOT NULL
) ON [PRIMARY]
GO
nonclustered primary key is seq column
how can i solve this problem?
any suggestion?
help...
thanks
On each article can you ensure that the collation is sent over - this is a
checkbox option on the article properties, snapshot tab.
Regards,
Paul Ibison
|||thanks for replying.~
on the article properties, snapshot tab..
those three options are checked..
Includes declared referential integrity
clustered index
non clustered index
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:us917DwbEHA.2760@.TK2MSFTNGP09.phx.gbl...
> On each article can you ensure that the collation is sent over - this is a
> checkbox option on the article properties, snapshot tab.
> Regards,
> Paul Ibison
>
|||OK - select the collation checkbox for each table and
reinitialize - hopefully this will remove the truncation
issue which may be due to different codepages.
Regards,
Paul Ibison
sql : sql2000 enterprise edition
mdac version is same each other.. version 2.8
i have two sql server(devsrv and parkchangsoon)
i configured the transaction replication
parkchangsoon : publisher,distributer
devsrv : subscriber
articles are 10 of all tables and 10 of all procedures
at first
the snapshot agent status is succss and the last action is "the snapshot of
24 articles have created"
after that
the distributer agent is pushing to devsrv (subscriber system)
but the distributer agent status is fail and the last action is "could not
bulk copy to 'jobs' table"
so..
i saw the distributer agent error information
publisher(P) : parkchangsoon agent(A) : PARKCHANGSOON-albaroot_3th-DEVSRV-5
publish(U) : albaroot_3th subscribe : DEVSRV:albaroot_3th
error message(E) : could not bulk copy to 'jobs' table
last command (V) : select * from workey_jobs where 1=1
error infomation(E) : String data, right truncation
source : DEVSRV(ODBC); eror number : 22001
below is the schema of the jobs table
CREATE TABLE [devuser].[Jobs] (
[seq] [int] IDENTITY (1, 1) NOT NULL ,
[title] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[findPrsn] [tinyint] NOT NULL ,
[ageZn] [varchar] (50) COLLATE Korean_Wansung_CI_AS NULL ,
[applyRght] [varchar] (4000) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[emplrId] [varchar] (30) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[readCnt] [int] NOT NULL ,
[sido] [tinyint] NOT NULL ,
[workTyp] [char] (8) COLLATE Korean_Wansung_CI_AS NULL ,
[applyDcmnt] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[findYmd2] [smalldatetime] NOT NULL ,
[gugun] [tinyint] NOT NULL ,
[finishYmd] [bit] NOT NULL ,
[ymd] [smalldatetime] NOT NULL ,
[particular] [char] (1) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[position] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[makeup_color] [bit] NOT NULL ,
[makeup_icon] [bit] NOT NULL ,
[makeup_marquee] [bit] NOT NULL ,
[logo] [varchar] (50) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[endymd] [smalldatetime] NOT NULL ,
[jobtype1] [tinyint] NULL ,
[jobtype2] [tinyint] NULL ,
[jobtype3] [tinyint] NULL ,
[paytype] [char] (4) COLLATE Korean_Wansung_CI_AS NULL ,
[pay1] [int] NULL ,
[pay2] [bit] NULL ,
[suprise] [tinyint] NULL ,
[ts] [timestamp] NULL ,
[visible] [bit] NULL ,
[createdYmd] [smalldatetime] NULL ,
[msrepl_tran_version] [uniqueidentifier] NOT NULL
) ON [PRIMARY]
GO
nonclustered primary key is seq column
how can i solve this problem?
any suggestion?
help...
thanks
On each article can you ensure that the collation is sent over - this is a
checkbox option on the article properties, snapshot tab.
Regards,
Paul Ibison
|||thanks for replying.~
on the article properties, snapshot tab..
those three options are checked..
Includes declared referential integrity
clustered index
non clustered index
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:us917DwbEHA.2760@.TK2MSFTNGP09.phx.gbl...
> On each article can you ensure that the collation is sent over - this is a
> checkbox option on the article properties, snapshot tab.
> Regards,
> Paul Ibison
>
|||OK - select the collation checkbox for each table and
reinitialize - hopefully this will remove the truncation
issue which may be due to different codepages.
Regards,
Paul Ibison
Friday, March 23, 2012
Purging Transaction Log
I am trying to purge the logfile (ldf) for our database.
I thought I had done it in the past through Enterprise
Manager by clicking the database, selecting
AllTasks/Shrink Database and then reducing the size of the
transaction log to its minimum. The logfile is currently
150 MB. I specified to shrink it to the minimum (8 MB).
It told me that it succeeded but the size is not changing.
Is this the appropriate way to reduce the log size?
THanks,
-RobYou must back up the log if you are in Full Recovery Mode prior to
shrinking...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Rob C" <robnocspam@.ctnosoftwarespam.com> wrote in message
news:0a4701c3bf26$c8d635d0$a401280a@.phx.gbl...
> I am trying to purge the logfile (ldf) for our database.
> I thought I had done it in the past through Enterprise
> Manager by clicking the database, selecting
> AllTasks/Shrink Database and then reducing the size of the
> transaction log to its minimum. The logfile is currently
> 150 MB. I specified to shrink it to the minimum (8 MB).
> It told me that it succeeded but the size is not changing.
> Is this the appropriate way to reduce the log size?
> THanks,
> -Rob|||Hi Rob,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
Our MVP, Wayne had provided a good explanation of how to shrink the log
file.
I just want to add some more information of this part.
When SQL Server finishes backing up the transaction log, it automatically
truncates the inactive portion of the transaction log. This inactive
portion contains completed transactions and so is no longer used during the
recovery process. Conversely, the active portion of the transaction log
contains transactions that are still running and have not yet completed.
SQL Server reuses this truncated, inactive space in the transaction log
instead of allowing the transaction log to continue to grow and use more
space. That is why although you use Enterprise Manager to set the log file
size, but it remains the same. You shoud backup it first to let it become
inactive.
Although the transaction log may be truncated manually, it is strongly
recommended that you do not do this, as it breaks the log backup chain.
Until a full database backup is created, the database is not protected from
media failure. Use manual log truncation only in very special
circumstances, and create a full database backup as soon as practical.
The ending point of the inactive portion of the transaction log, and hence
the truncation point, is the earliest of the following events:
1)The most recent checkpoint.
2)The start of the oldest active transaction, which is a transaction that
has not yet been committed or rolled back.
This represents the earliest point to which SQL Server would have to roll
back transactions during recovery.
3)The start of the oldest transaction that involves objects published for
replication whose changes have not been replicated yet. This represents the
earliest point that SQL Server still has to replicate.
You can refer to SQL Server Books on Line (BOL) for more information for
active portion and inactive portion of log files and some DBCC commands to
carry out log truncation by searching :
"Truncating the Transaction Log" in the BOL
I hope will be helpful to resolve your question. If you still have any
questions, please feel free to post any new message here, I am ready to
offer you further help.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Thank you both fo you replies.
I was able to successfully shrink the log once I ran the
backup process on the transaction logfile.
I also appreciated the explanation behind it.
Regards,
-Rob
>--Original Message--
>Hi Rob,
>Thank you for using MSDN Newsgroup! It's my pleasure to
assist you with
>your issue.
>Our MVP, Wayne had provided a good explanation of how to
shrink the log
>file.
>I just want to add some more information of this part.
>When SQL Server finishes backing up the transaction log,
it automatically
>truncates the inactive portion of the transaction log.
This inactive
>portion contains completed transactions and so is no
longer used during the
>recovery process. Conversely, the active portion of the
transaction log
>contains transactions that are still running and have not
yet completed.
>SQL Server reuses this truncated, inactive space in the
transaction log
>instead of allowing the transaction log to continue to
grow and use more
>space. That is why although you use Enterprise Manager to
set the log file
>size, but it remains the same. You shoud backup it first
to let it become
>inactive.
>Although the transaction log may be truncated manually,
it is strongly
>recommended that you do not do this, as it breaks the log
backup chain.
>Until a full database backup is created, the database is
not protected from
>media failure. Use manual log truncation only in very
special
>circumstances, and create a full database backup as soon
as practical.
>The ending point of the inactive portion of the
transaction log, and hence
>the truncation point, is the earliest of the following
events:
>1)The most recent checkpoint.
>2)The start of the oldest active transaction, which is a
transaction that
>has not yet been committed or rolled back.
>This represents the earliest point to which SQL Server
would have to roll
>back transactions during recovery.
>3)The start of the oldest transaction that involves
objects published for
>replication whose changes have not been replicated yet.
This represents the
>earliest point that SQL Server still has to replicate.
>You can refer to SQL Server Books on Line (BOL) for
more information for
>active portion and inactive portion of log files and some
DBCC commands to
>carry out log truncation by searching :
>"Truncating the Transaction Log" in the BOL
>I hope will be helpful to resolve your question. If you
still have any
>questions, please feel free to post any new message here,
I am ready to
>offer you further help.
>Best regards
>Baisong Wei
>Microsoft Online Support
>----
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and
confers no rights.
>Please reply to newsgroups only. Thanks.
>.
>|||How does one manually truncate a transaction log?|||Hi Gayle,
Thank you for using MSDN Newsgroup!
You can manually truncate the trasaction log. Please refer to the following
article for detailed information:
http://support.microsoft.com/?id=272318
If you still have question, please post new message here and I am ready to
help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Thank you for replying! The drive where the transaction log resides -
drive L - ran out of space (the transaction log is 97GB). This has,
naturally, made it to where we cannot access our databases through
Enterprise Manager. When we try to open Query Analyzer, it times out
but then still shows a query window with the Master database selected,
but we cannot change from the Master to any of our application's
databases. We tried to do the following via Query Analyzer anyway:
backup database (to the S drive, which had space)
backup log with truncate_only
dbcc shrinkfile on the log file
backup database
We let it run ("Processing query batch") for an hour before we stopped
it. We assume that it didn't work because it was trying to write to
the transaction log but couldn't. Is that correct? Does SQL write
administrative queries (like backup statements) to the transaction
log? We know now what we need to do to prevent the transaction log
from outgrowing its space and we're going to try to set up an alert so
that SQL will page us when the log gets too big.
I guess what I'd like to know is, should our preventive measures fail
and the log's drive fill up again, what is the best approach to take?
Thank you for any info you can share.sql
I thought I had done it in the past through Enterprise
Manager by clicking the database, selecting
AllTasks/Shrink Database and then reducing the size of the
transaction log to its minimum. The logfile is currently
150 MB. I specified to shrink it to the minimum (8 MB).
It told me that it succeeded but the size is not changing.
Is this the appropriate way to reduce the log size?
THanks,
-RobYou must back up the log if you are in Full Recovery Mode prior to
shrinking...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Rob C" <robnocspam@.ctnosoftwarespam.com> wrote in message
news:0a4701c3bf26$c8d635d0$a401280a@.phx.gbl...
> I am trying to purge the logfile (ldf) for our database.
> I thought I had done it in the past through Enterprise
> Manager by clicking the database, selecting
> AllTasks/Shrink Database and then reducing the size of the
> transaction log to its minimum. The logfile is currently
> 150 MB. I specified to shrink it to the minimum (8 MB).
> It told me that it succeeded but the size is not changing.
> Is this the appropriate way to reduce the log size?
> THanks,
> -Rob|||Hi Rob,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
Our MVP, Wayne had provided a good explanation of how to shrink the log
file.
I just want to add some more information of this part.
When SQL Server finishes backing up the transaction log, it automatically
truncates the inactive portion of the transaction log. This inactive
portion contains completed transactions and so is no longer used during the
recovery process. Conversely, the active portion of the transaction log
contains transactions that are still running and have not yet completed.
SQL Server reuses this truncated, inactive space in the transaction log
instead of allowing the transaction log to continue to grow and use more
space. That is why although you use Enterprise Manager to set the log file
size, but it remains the same. You shoud backup it first to let it become
inactive.
Although the transaction log may be truncated manually, it is strongly
recommended that you do not do this, as it breaks the log backup chain.
Until a full database backup is created, the database is not protected from
media failure. Use manual log truncation only in very special
circumstances, and create a full database backup as soon as practical.
The ending point of the inactive portion of the transaction log, and hence
the truncation point, is the earliest of the following events:
1)The most recent checkpoint.
2)The start of the oldest active transaction, which is a transaction that
has not yet been committed or rolled back.
This represents the earliest point to which SQL Server would have to roll
back transactions during recovery.
3)The start of the oldest transaction that involves objects published for
replication whose changes have not been replicated yet. This represents the
earliest point that SQL Server still has to replicate.
You can refer to SQL Server Books on Line (BOL) for more information for
active portion and inactive portion of log files and some DBCC commands to
carry out log truncation by searching :
"Truncating the Transaction Log" in the BOL
I hope will be helpful to resolve your question. If you still have any
questions, please feel free to post any new message here, I am ready to
offer you further help.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Thank you both fo you replies.
I was able to successfully shrink the log once I ran the
backup process on the transaction logfile.
I also appreciated the explanation behind it.
Regards,
-Rob
>--Original Message--
>Hi Rob,
>Thank you for using MSDN Newsgroup! It's my pleasure to
assist you with
>your issue.
>Our MVP, Wayne had provided a good explanation of how to
shrink the log
>file.
>I just want to add some more information of this part.
>When SQL Server finishes backing up the transaction log,
it automatically
>truncates the inactive portion of the transaction log.
This inactive
>portion contains completed transactions and so is no
longer used during the
>recovery process. Conversely, the active portion of the
transaction log
>contains transactions that are still running and have not
yet completed.
>SQL Server reuses this truncated, inactive space in the
transaction log
>instead of allowing the transaction log to continue to
grow and use more
>space. That is why although you use Enterprise Manager to
set the log file
>size, but it remains the same. You shoud backup it first
to let it become
>inactive.
>Although the transaction log may be truncated manually,
it is strongly
>recommended that you do not do this, as it breaks the log
backup chain.
>Until a full database backup is created, the database is
not protected from
>media failure. Use manual log truncation only in very
special
>circumstances, and create a full database backup as soon
as practical.
>The ending point of the inactive portion of the
transaction log, and hence
>the truncation point, is the earliest of the following
events:
>1)The most recent checkpoint.
>2)The start of the oldest active transaction, which is a
transaction that
>has not yet been committed or rolled back.
>This represents the earliest point to which SQL Server
would have to roll
>back transactions during recovery.
>3)The start of the oldest transaction that involves
objects published for
>replication whose changes have not been replicated yet.
This represents the
>earliest point that SQL Server still has to replicate.
>You can refer to SQL Server Books on Line (BOL) for
more information for
>active portion and inactive portion of log files and some
DBCC commands to
>carry out log truncation by searching :
>"Truncating the Transaction Log" in the BOL
>I hope will be helpful to resolve your question. If you
still have any
>questions, please feel free to post any new message here,
I am ready to
>offer you further help.
>Best regards
>Baisong Wei
>Microsoft Online Support
>----
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and
confers no rights.
>Please reply to newsgroups only. Thanks.
>.
>|||How does one manually truncate a transaction log?|||Hi Gayle,
Thank you for using MSDN Newsgroup!
You can manually truncate the trasaction log. Please refer to the following
article for detailed information:
http://support.microsoft.com/?id=272318
If you still have question, please post new message here and I am ready to
help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Thank you for replying! The drive where the transaction log resides -
drive L - ran out of space (the transaction log is 97GB). This has,
naturally, made it to where we cannot access our databases through
Enterprise Manager. When we try to open Query Analyzer, it times out
but then still shows a query window with the Master database selected,
but we cannot change from the Master to any of our application's
databases. We tried to do the following via Query Analyzer anyway:
backup database (to the S drive, which had space)
backup log with truncate_only
dbcc shrinkfile on the log file
backup database
We let it run ("Processing query batch") for an hour before we stopped
it. We assume that it didn't work because it was trying to write to
the transaction log but couldn't. Is that correct? Does SQL write
administrative queries (like backup statements) to the transaction
log? We know now what we need to do to prevent the transaction log
from outgrowing its space and we're going to try to set up an alert so
that SQL will page us when the log gets too big.
I guess what I'd like to know is, should our preventive measures fail
and the log's drive fill up again, what is the best approach to take?
Thank you for any info you can share.sql
Wednesday, March 21, 2012
Purchasing SQL Server 2005
I have been tasked with determining which edition of SQL server 2005 to purchase for my business.
We currently have SQL server 2005 Enterprise Edition, although due to the spec of our laptops (operating system) we cannot install the full version of this on our laptops (2gb database capped limit)
The laptop specification is:
1.66 Ghz Intel Centrino Duo
1 Gb Ram
60 Gb HDD
Microsoft Windows XP Profressional Version 2002, SP2 (64 bit?)
I believe the Standard Edition will enable us to have an uncapped SQL Server 2005 database limit on the laptops.
Alternatively, please could anybody advise which edition should be purchased
Many thanks
You haven't mentioned about what kind of business you have and wanted to use SQL Server.
I believe you can look into Workgroup edition or SQLExpress of SQL and still I would like to know the size of userbase & database.
|||I am an Analyst and I need to analyse 5gb + of financial data.
Would Standard edition or Developer edition not suffice?
|||Then Standard edition should do the job, to handle the application.Monday, March 12, 2012
Pull subscription creation error
Upon creating a new Pull Subscription on a Subscriber, I kept on getting
the error message "SQL Server enterprise Manager could not create a pull
subscription to publication 'XXXX' Error 14234: The specified '@.server' is
invalid(valid values are returned by sp_helpserver). Where did I go wrong
and what is the problem? Thanks.
Georgi,
you could check that the server names haven't been altered:
Use Master
go
Select @.@.Servername
This should return your current server name but if it
returns NULL then try:
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thank you. I checked but both publisher and subscriber have server names
other than NULL ...
Let me explain more my situation.
I want to make replication of database over internet, i want to use VPN. I
already setuped the VPN service so it gives IP-s that are not within the
range of the local network and are fixed for the server and for the
connections.
I was trying to make push subscription because it seemed to me that it's
easier to implement. So the subscription was successefuly added , the
snapshot agent generated snapshot but then this snapshot was not
automatically applied on Subscriber and the distributor agent cried out that
"objects are missing at subscriber". I don't know how to apply the
subscription manually, i tried to change it's path via Alternate
subscription location but it didn't helped. So i abandoned the push
subscription and now i'm trying to make pull subscription. I don't know if
i'm not missing someting of the security privilegies of the logins used, or
maybe must declare the servers in Remote Servers?
I'm quite confused with all this Replication stuff, i'm still new to it.
I've looked to the Replication section in SQL Server online but i can't find
solutions of this delicate problems (maybe it's written somewhere i'm still
reading ). Can you give me link(s) to some other comprehensive sources of
information, maybe good HOWTOS?
Thank you in advance
Georgi Peshterski
"Paul Ibison" <Paul.Ibison@.pygmalion.com> wrote in message
news:eRZf%23mUjFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Georgi,
> you could check that the server names haven't been altered:
> Use Master
> go
> Select @.@.Servername
> This should return your current server name but if it
> returns NULL then try:
> Use Master
> go
> Sp_DropServer 'OldName'
> GO
> Use Master
> go
> Sp_Addserver 'NewName', 'local'
> GO
> Stop and Start SQL Services
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
the error message "SQL Server enterprise Manager could not create a pull
subscription to publication 'XXXX' Error 14234: The specified '@.server' is
invalid(valid values are returned by sp_helpserver). Where did I go wrong
and what is the problem? Thanks.
Georgi,
you could check that the server names haven't been altered:
Use Master
go
Select @.@.Servername
This should return your current server name but if it
returns NULL then try:
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thank you. I checked but both publisher and subscriber have server names
other than NULL ...
Let me explain more my situation.
I want to make replication of database over internet, i want to use VPN. I
already setuped the VPN service so it gives IP-s that are not within the
range of the local network and are fixed for the server and for the
connections.
I was trying to make push subscription because it seemed to me that it's
easier to implement. So the subscription was successefuly added , the
snapshot agent generated snapshot but then this snapshot was not
automatically applied on Subscriber and the distributor agent cried out that
"objects are missing at subscriber". I don't know how to apply the
subscription manually, i tried to change it's path via Alternate
subscription location but it didn't helped. So i abandoned the push
subscription and now i'm trying to make pull subscription. I don't know if
i'm not missing someting of the security privilegies of the logins used, or
maybe must declare the servers in Remote Servers?
I'm quite confused with all this Replication stuff, i'm still new to it.
I've looked to the Replication section in SQL Server online but i can't find
solutions of this delicate problems (maybe it's written somewhere i'm still
reading ). Can you give me link(s) to some other comprehensive sources of
information, maybe good HOWTOS?
Thank you in advance
Georgi Peshterski
"Paul Ibison" <Paul.Ibison@.pygmalion.com> wrote in message
news:eRZf%23mUjFHA.3300@.TK2MSFTNGP15.phx.gbl...
> Georgi,
> you could check that the server names haven't been altered:
> Use Master
> go
> Select @.@.Servername
> This should return your current server name but if it
> returns NULL then try:
> Use Master
> go
> Sp_DropServer 'OldName'
> GO
> Use Master
> go
> Sp_Addserver 'NewName', 'local'
> GO
> Stop and Start SQL Services
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
Pull Subscription
I am setting up a pull subscription and I keep getting an error
message:
"SQL Server Enterprise Manger could not create a pull subscription to
publication 'XX'. Error 14053: Cannot load the DLL replincrementlsn
extended procedure, or one of the DLLs it references. ..."
Any suggestions on how to resolve this error. Thanks in advance.
Hi,
I feel that there is some installation issues. Did you install any service
packs recently whicgh didnt completed fully?Check for the procedures
sp_replincrementlsn and sp_replincrementlsn_internal (Extended proc) in
MASTER database.
If the procedures are not there then create it by scripting it out from some
other SQL servers and try
setting up the subscription again.
Thanks
Hari
MCDBA
"Scott" <scott@.jucovics.com> wrote in message
news:3fe08b2e.0406291147.18387555@.posting.google.c om...
> I am setting up a pull subscription and I keep getting an error
> message:
> "SQL Server Enterprise Manger could not create a pull subscription to
> publication 'XX'. Error 14053: Cannot load the DLL replincrementlsn
> extended procedure, or one of the DLLs it references. ..."
> Any suggestions on how to resolve this error. Thanks in advance.
|||Scott,
if you did a custom install, you need to have selected Replication Support.
If you have installed a service pack, check that it fully installed - have a
look at sqlsp.log file from the c:\windows directory this might shed some
light on any failed actions during the sp installation.
HTH,
Paul Ibison
|||"Hari" <hari_prasad_k@.hotmail.com> wrote in message news:<uKJ#q6mXEHA.3612@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
> Hi,
> I feel that there is some installation issues. Did you install any service
> packs recently whicgh didnt completed fully?Check for the procedures
> sp_replincrementlsn and sp_replincrementlsn_internal (Extended proc) in
> MASTER database.
> If the procedures are not there then create it by scripting it out from some
> other SQL servers and try
> setting up the subscription again.
> --
> Thanks
> Hari
> MCDBA
> "Scott" <scott@.jucovics.com> wrote in message
> news:3fe08b2e.0406291147.18387555@.posting.google.c om...
I tried to script out he sp_replincmentlsn and since it is an extended
stored procedure I'm not sure how? I tried various methods and when I
tried to create the extended stored proc manually, it said it is
"already an object in the database" even though I cannot see it under
the Master database. I do see "sp_replincrementlsn_internal", I'm
trying to rerun the SQL SERVER SP3 right now.
message:
"SQL Server Enterprise Manger could not create a pull subscription to
publication 'XX'. Error 14053: Cannot load the DLL replincrementlsn
extended procedure, or one of the DLLs it references. ..."
Any suggestions on how to resolve this error. Thanks in advance.
Hi,
I feel that there is some installation issues. Did you install any service
packs recently whicgh didnt completed fully?Check for the procedures
sp_replincrementlsn and sp_replincrementlsn_internal (Extended proc) in
MASTER database.
If the procedures are not there then create it by scripting it out from some
other SQL servers and try
setting up the subscription again.
Thanks
Hari
MCDBA
"Scott" <scott@.jucovics.com> wrote in message
news:3fe08b2e.0406291147.18387555@.posting.google.c om...
> I am setting up a pull subscription and I keep getting an error
> message:
> "SQL Server Enterprise Manger could not create a pull subscription to
> publication 'XX'. Error 14053: Cannot load the DLL replincrementlsn
> extended procedure, or one of the DLLs it references. ..."
> Any suggestions on how to resolve this error. Thanks in advance.
|||Scott,
if you did a custom install, you need to have selected Replication Support.
If you have installed a service pack, check that it fully installed - have a
look at sqlsp.log file from the c:\windows directory this might shed some
light on any failed actions during the sp installation.
HTH,
Paul Ibison
|||"Hari" <hari_prasad_k@.hotmail.com> wrote in message news:<uKJ#q6mXEHA.3612@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
> Hi,
> I feel that there is some installation issues. Did you install any service
> packs recently whicgh didnt completed fully?Check for the procedures
> sp_replincrementlsn and sp_replincrementlsn_internal (Extended proc) in
> MASTER database.
> If the procedures are not there then create it by scripting it out from some
> other SQL servers and try
> setting up the subscription again.
> --
> Thanks
> Hari
> MCDBA
> "Scott" <scott@.jucovics.com> wrote in message
> news:3fe08b2e.0406291147.18387555@.posting.google.c om...
I tried to script out he sp_replincmentlsn and since it is an extended
stored procedure I'm not sure how? I tried various methods and when I
tried to create the extended stored proc manually, it said it is
"already an object in the database" even though I cannot see it under
the Master database. I do see "sp_replincrementlsn_internal", I'm
trying to rerun the SQL SERVER SP3 right now.
Friday, March 9, 2012
Puchasing only Enterprise Manager
hello!
I am interested in purchasing sql server.
Is it possible to purchase a Enterprise Manager only? So
I do not have to buy complete SQL server?
thanks,
DanielThe only thing you can DO with EM is connect and manage an existing instance
of SQL Server. This presupposes that you have already purchased a SQL
Server license. If you have a license for SQL Server you can install the
client tools (Query Analyzer, Enterprise Manager, etc...) on any number of
computers without additional licensing fees.
"Daniel Kim" <daekim_2000@.netzero.net> wrote in message
news:108901c3820b$9bcf6fa0$a001280a@.phx.gbl...
> hello!
> I am interested in purchasing sql server.
> Is it possible to purchase a Enterprise Manager only? So
> I do not have to buy complete SQL server?
> thanks,
> Daniel|||I believe this depends on if the existing license is per-processor or
per-seat.
One option would be to buy the Developer edition for $49, which comes with
the client tools.
Kevin3NF
"Don Peterson" <no1@.nunya.com> wrote in message
news:Otab9zggDHA.3616@.TK2MSFTNGP11.phx.gbl...
> The only thing you can DO with EM is connect and manage an existing
instance
> of SQL Server. This presupposes that you have already purchased a SQL
> Server license. If you have a license for SQL Server you can install the
> client tools (Query Analyzer, Enterprise Manager, etc...) on any number of
> computers without additional licensing fees.
> "Daniel Kim" <daekim_2000@.netzero.net> wrote in message
> news:108901c3820b$9bcf6fa0$a001280a@.phx.gbl...
> > hello!
> >
> > I am interested in purchasing sql server.
> > Is it possible to purchase a Enterprise Manager only? So
> > I do not have to buy complete SQL server?
> >
> > thanks,
> >
> > Daniel
>
I am interested in purchasing sql server.
Is it possible to purchase a Enterprise Manager only? So
I do not have to buy complete SQL server?
thanks,
DanielThe only thing you can DO with EM is connect and manage an existing instance
of SQL Server. This presupposes that you have already purchased a SQL
Server license. If you have a license for SQL Server you can install the
client tools (Query Analyzer, Enterprise Manager, etc...) on any number of
computers without additional licensing fees.
"Daniel Kim" <daekim_2000@.netzero.net> wrote in message
news:108901c3820b$9bcf6fa0$a001280a@.phx.gbl...
> hello!
> I am interested in purchasing sql server.
> Is it possible to purchase a Enterprise Manager only? So
> I do not have to buy complete SQL server?
> thanks,
> Daniel|||I believe this depends on if the existing license is per-processor or
per-seat.
One option would be to buy the Developer edition for $49, which comes with
the client tools.
Kevin3NF
"Don Peterson" <no1@.nunya.com> wrote in message
news:Otab9zggDHA.3616@.TK2MSFTNGP11.phx.gbl...
> The only thing you can DO with EM is connect and manage an existing
instance
> of SQL Server. This presupposes that you have already purchased a SQL
> Server license. If you have a license for SQL Server you can install the
> client tools (Query Analyzer, Enterprise Manager, etc...) on any number of
> computers without additional licensing fees.
> "Daniel Kim" <daekim_2000@.netzero.net> wrote in message
> news:108901c3820b$9bcf6fa0$a001280a@.phx.gbl...
> > hello!
> >
> > I am interested in purchasing sql server.
> > Is it possible to purchase a Enterprise Manager only? So
> > I do not have to buy complete SQL server?
> >
> > thanks,
> >
> > Daniel
>
Wednesday, March 7, 2012
Publisher configuration problem
I am trying to configure a MS SQL Server 2000 named \\MSSQL_NEW as a
publisher but I keep getting this
error:
SQL Server Enterprise Manager can not configure 'MSSQL_NEW' as the
distributor for 'MSSQL_NEW'
Error 18483:
Could not connect to server 'MSSQL_NEW' because 'distributor_admin' is not
defined as a remote login at
the server.
I've verified that 'distributor_admin' exists and has sysadmin rights on the
server (MSSQL_NEW).
I noticed that when I execute, 'select @.@.servername', in QA, I get,
'MSSQL_OLD'. But my machine name is, 'MSSQL_NEW'
and name registered in EM is 'MSSQL_NEW'. Tried replacing the registration
'MSSQL_NEW' to 'MSSQL_OLD' but I get a
server does not exist or access denied error.
Will updating @.@.servername to 'MSSQL_NEW' solve my problem? How?
Any comments or suggestions will be highly appreciated. Thanks in advance.
...
Carlo,
please try this...
Use Master
go
Sp_DropServer 'MSSQL_OLD'
GO
Use Master
go
Sp_Addserver 'MSSQL_NEW', 'local'
GO
Stop and Start SQL Services
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||This is a tricky problem to solve.
I normally solve it by issuing a
sp_adddistributor and an sp_adddistributiondb procs.
These should work. Then when you go to replicate it will bomb. So disable
replication, and then re-enable it. It should work this time.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:77815079-C1A6-477C-9794-391828479E38@.microsoft.com...
> I am trying to configure a MS SQL Server 2000 named \\MSSQL_NEW as a
> publisher but I keep getting this
> error:
> SQL Server Enterprise Manager can not configure 'MSSQL_NEW' as the
> distributor for 'MSSQL_NEW'
> Error 18483:
> Could not connect to server 'MSSQL_NEW' because 'distributor_admin' is not
> defined as a remote login at
> the server.
> I've verified that 'distributor_admin' exists and has sysadmin rights on
the
> server (MSSQL_NEW).
> I noticed that when I execute, 'select @.@.servername', in QA, I get,
> 'MSSQL_OLD'. But my machine name is, 'MSSQL_NEW'
> and name registered in EM is 'MSSQL_NEW'. Tried replacing the
registration
> 'MSSQL_NEW' to 'MSSQL_OLD' but I get a
> server does not exist or access denied error.
> Will updating @.@.servername to 'MSSQL_NEW' solve my problem? How?
> Any comments or suggestions will be highly appreciated. Thanks in
advance.
> --
> ...
publisher but I keep getting this
error:
SQL Server Enterprise Manager can not configure 'MSSQL_NEW' as the
distributor for 'MSSQL_NEW'
Error 18483:
Could not connect to server 'MSSQL_NEW' because 'distributor_admin' is not
defined as a remote login at
the server.
I've verified that 'distributor_admin' exists and has sysadmin rights on the
server (MSSQL_NEW).
I noticed that when I execute, 'select @.@.servername', in QA, I get,
'MSSQL_OLD'. But my machine name is, 'MSSQL_NEW'
and name registered in EM is 'MSSQL_NEW'. Tried replacing the registration
'MSSQL_NEW' to 'MSSQL_OLD' but I get a
server does not exist or access denied error.
Will updating @.@.servername to 'MSSQL_NEW' solve my problem? How?
Any comments or suggestions will be highly appreciated. Thanks in advance.
...
Carlo,
please try this...
Use Master
go
Sp_DropServer 'MSSQL_OLD'
GO
Use Master
go
Sp_Addserver 'MSSQL_NEW', 'local'
GO
Stop and Start SQL Services
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||This is a tricky problem to solve.
I normally solve it by issuing a
sp_adddistributor and an sp_adddistributiondb procs.
These should work. Then when you go to replicate it will bomb. So disable
replication, and then re-enable it. It should work this time.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:77815079-C1A6-477C-9794-391828479E38@.microsoft.com...
> I am trying to configure a MS SQL Server 2000 named \\MSSQL_NEW as a
> publisher but I keep getting this
> error:
> SQL Server Enterprise Manager can not configure 'MSSQL_NEW' as the
> distributor for 'MSSQL_NEW'
> Error 18483:
> Could not connect to server 'MSSQL_NEW' because 'distributor_admin' is not
> defined as a remote login at
> the server.
> I've verified that 'distributor_admin' exists and has sysadmin rights on
the
> server (MSSQL_NEW).
> I noticed that when I execute, 'select @.@.servername', in QA, I get,
> 'MSSQL_OLD'. But my machine name is, 'MSSQL_NEW'
> and name registered in EM is 'MSSQL_NEW'. Tried replacing the
registration
> 'MSSQL_NEW' to 'MSSQL_OLD' but I get a
> server does not exist or access denied error.
> Will updating @.@.servername to 'MSSQL_NEW' solve my problem? How?
> Any comments or suggestions will be highly appreciated. Thanks in
advance.
> --
> ...
Saturday, February 25, 2012
Publication Configuration Error
Hey Everyone,
I am trying to setup publishing on SQL Server 2000 Enterprise. I will be subscribing from a SQL Mobile 2005 database so I have installed the SQL Server 2000 SP3a Replication Components, .NET Framework 2.0, and the SQL Server 2005 Mobile Edition Server Tools.
I was able to go through the 2005 Mobile Web Synchronization Wizard with no problems. However, when I try to run the Configure Publishing and Distribution Wizard, I get the following message at the end:
SQL Server Enterprise Manager could not configure 'GISSERV' as the Distributor for 'GISSERV'
Error 14114: '(null)' is not configured as a Distributor.
The first option I choose is Make 'GISSERV' it's own Distributor. Then, I select the snapshot folder that I shared. And on the third screen, I've tried going with the standard default settings and customizing those settings.
Has anyone else come across this error? Is there anyone else out there replicating from SQL Server 2000 to SQL Server 2005 Mobile?
Thanks in advance,
Lee
Is this merge replication? If so, this configuration is not supported, you cannot have a SQL 2005 subscriber with a SQL 2000 publisher/distributor.
http://msdn2.microsoft.com/ms143241(en-US,SQL.90).aspx
|||Thanks for the link. I'm going to have to find another way of doing this. I was led to believe that it was possible by this article:
http://www.microsoft.com/sql/editions/sqlmobile/connectivity-tools.mspx
But regardless of what my subscriber is running, I still should not be getting this error, should I?
Thanks,
Lee
|||hold on, i wasn't paying attention when you said SQL Server Mobile 2005. Let me double-check.|||Yes, SQL 2005 Mobile is supported for a SQL 2000 publisher/distributor, I was incorrect.
Regarding the error message, have you renamed your machine along the way, or restored master database from a backup of another machine? Regardless, here's the KB article that most like fixes the situation:
http://support.microsoft.com/default.aspx?scid=kb;en-us;302223
Subscribe to:
Posts (Atom)