Showing posts with label sqlserver. Show all posts
Showing posts with label sqlserver. Show all posts

Monday, March 26, 2012

Push replication between SQL2k and SQL2k

Hi,

I am wanting to set up replication between two SQLServer 2000 databases. DB1 has the data, and DB2 is where I would like to replicate to. I have set up the publisher and distributor on DB1, and have set up DB2 as the subscriber. The replication is set up as transactional.

When the agent runs, it fails with the following error details:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Where do I set the user that the agent should be using?

I think that it is also worth noting that the two computers are not on the same domain. There are no firewalls involved either.I Think it uses the SQL Server Agent Sevice Startup Account security

Right click on the Agent in EM & Make sure that the account has access to both Servers.

or

Go into the server Services and look at the SQL Agent Startup Account

There are other areas but try this till someone explains it better than I can|||Aha! I found the answer!

The agent at the distributor is trying to start the agent at the subscriber. The correct permissions must be given on the agent at the subscriber so that the agent at the distributor can execute the app. I am not exactly sure what it requires yet, but this is what I did:

1) Run the dcomcnfg application from the Run box.
2) Select the 'Microsoft SQL Server Replication Remote Dist Agent 8.0'
3) Open the properties of the agent.
4) Select the Security tab.
5) Use custom configurations for all settings in this tab. Add the NETWORK group to each configuration group and give the same level of access as the other accounts in the configuration.

6) Select the Identity tab.
7) Select 'This user' and provide a local machine user name that has permissions to run this app.

8) Click OK to save the changes.

The next problem is that if you are running 2000 with SP3, then the user provided by the agent will not be trusted and will give you another error. Error number 18452 or something similar.

To make the user trusted, you must execute the xp_sqlagent_proxy_account stored procedure on the subscriber server.

xp_sqlagent_proxy_account

{N'GET' | N'SET' | N'DEL ,

N'agent_domain_name', N'agent_username', N'agent_password'

}

You can find more documentation on this stored procedure in MSDN under SQL Server 2000 and Replication Security.

Wednesday, March 21, 2012

Purchasing Rs2005

Hi, RS2000 was a separate from SQLServer2000 and a free download, only
requirement being you must have a SQLServer 2000 lic. For RS 2005 it looks
like its bundled up with SQLServer 2005. Must I purchase SQLServer 2005 in
order to upgrade to RS 2005, we don't wish to upgrade from SQL2000 just
Reporting Services. In there not a separate download and Licence for RS2005.
ThanksRS 2005 is part of SQL Server 2005. Nothing has changed. RS 2000 was part
(from a licensing perspective) of SQL Server 2000. The only reason it had a
separate download/CD was because it was released later. You can leave the DB
at 2000 and install RS 2005 but you must have a SQL Server 2005 license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Kerry" <Kerry@.discussions.microsoft.com> wrote in message
news:EEB251CF-0871-4530-A95C-F8ECBFE891D9@.microsoft.com...
> Hi, RS2000 was a separate from SQLServer2000 and a free download, only
> requirement being you must have a SQLServer 2000 lic. For RS 2005 it
> looks
> like its bundled up with SQLServer 2005. Must I purchase SQLServer 2005 in
> order to upgrade to RS 2005, we don't wish to upgrade from SQL2000 just
> Reporting Services. In there not a separate download and Licence for
> RS2005.
> Thanks|||Bruce,
Since we would like to do the same change (keep SQL2000 and upgrade from
RS2000 to RS2005), is only (1) one SQL2005 license necessary since we already
have licenses for SQL2000?
Thanks in advance
"Bruce L-C [MVP]" wrote:
> RS 2005 is part of SQL Server 2005. Nothing has changed. RS 2000 was part
> (from a licensing perspective) of SQL Server 2000. The only reason it had a
> separate download/CD was because it was released later. You can leave the DB
> at 2000 and install RS 2005 but you must have a SQL Server 2005 license.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Kerry" <Kerry@.discussions.microsoft.com> wrote in message
> news:EEB251CF-0871-4530-A95C-F8ECBFE891D9@.microsoft.com...
> > Hi, RS2000 was a separate from SQLServer2000 and a free download, only
> > requirement being you must have a SQLServer 2000 lic. For RS 2005 it
> > looks
> > like its bundled up with SQLServer 2005. Must I purchase SQLServer 2005 in
> > order to upgrade to RS 2005, we don't wish to upgrade from SQL2000 just
> > Reporting Services. In there not a separate download and Licence for
> > RS2005.
> >
> > Thanks
>
>|||Is your RS on the same box as SQL Server 2000 Database?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JACK (SQL DBA)" <JACK (SQL DBA)@.discussions.microsoft.com> wrote in message
news:D77D3ED1-72CF-4FC6-9019-C52967EDF6A3@.microsoft.com...
> Bruce,
> Since we would like to do the same change (keep SQL2000 and upgrade from
> RS2000 to RS2005), is only (1) one SQL2005 license necessary since we
> already
> have licenses for SQL2000?
> Thanks in advance
> "Bruce L-C [MVP]" wrote:
>> RS 2005 is part of SQL Server 2005. Nothing has changed. RS 2000 was part
>> (from a licensing perspective) of SQL Server 2000. The only reason it had
>> a
>> separate download/CD was because it was released later. You can leave the
>> DB
>> at 2000 and install RS 2005 but you must have a SQL Server 2005 license.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Kerry" <Kerry@.discussions.microsoft.com> wrote in message
>> news:EEB251CF-0871-4530-A95C-F8ECBFE891D9@.microsoft.com...
>> > Hi, RS2000 was a separate from SQLServer2000 and a free download, only
>> > requirement being you must have a SQLServer 2000 lic. For RS 2005 it
>> > looks
>> > like its bundled up with SQLServer 2005. Must I purchase SQLServer 2005
>> > in
>> > order to upgrade to RS 2005, we don't wish to upgrade from SQL2000 just
>> > Reporting Services. In there not a separate download and Licence for
>> > RS2005.
>> >
>> > Thanks
>>|||Bruce, I am like Jack. I own SQL2000 and use RS2000 but would like to
upgrade to RS2005 without purchasing SQL2005. But it looks like I have to.
Next question is, I only have one server, RS is on the same box as SQL Server
database and I own SQL Server2000 Standard Edition-1 Processor License.
Would I have to purchase the SQL2005 that costs about $5k or is there a
cheaper version I could purchase that would give me rights to use RS2005 on
this machine? Thanks for your help. Jerry
"Bruce L-C [MVP]" wrote:
> Is your RS on the same box as SQL Server 2000 Database?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "JACK (SQL DBA)" <JACK (SQL DBA)@.discussions.microsoft.com> wrote in message
> news:D77D3ED1-72CF-4FC6-9019-C52967EDF6A3@.microsoft.com...
> > Bruce,
> >
> > Since we would like to do the same change (keep SQL2000 and upgrade from
> > RS2000 to RS2005), is only (1) one SQL2005 license necessary since we
> > already
> > have licenses for SQL2000?
> >
> > Thanks in advance
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> RS 2005 is part of SQL Server 2005. Nothing has changed. RS 2000 was part
> >> (from a licensing perspective) of SQL Server 2000. The only reason it had
> >> a
> >> separate download/CD was because it was released later. You can leave the
> >> DB
> >> at 2000 and install RS 2005 but you must have a SQL Server 2005 license.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Kerry" <Kerry@.discussions.microsoft.com> wrote in message
> >> news:EEB251CF-0871-4530-A95C-F8ECBFE891D9@.microsoft.com...
> >> > Hi, RS2000 was a separate from SQLServer2000 and a free download, only
> >> > requirement being you must have a SQLServer 2000 lic. For RS 2005 it
> >> > looks
> >> > like its bundled up with SQLServer 2005. Must I purchase SQLServer 2005
> >> > in
> >> > order to upgrade to RS 2005, we don't wish to upgrade from SQL2000 just
> >> > Reporting Services. In there not a separate download and Licence for
> >> > RS2005.
> >> >
> >> > Thanks
> >>
> >>
> >>
>
>sql

Pulling stored Procs from a remote db

Hi all -
I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used under it at the host. I can get at the db by using
Access/ODBC with a URL but the migration facility seems only to let me get
at the tables.
There are about half a dozen SPs referred to in the ASP code ( eg EXEC
sp_www) and I want to get hold of the code as I am not sure at all what they
are doing.
How do I get the code for each SP and store it in the local copy of the db?
Can I just replicate the db and move the replica to a local area?
Any advice on this gratefully (!) receive
Thanks
Jim McDonaldYou can get the source code of a stored procedure using sp_helptext.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jim McDonald" <jim@.missile.demon.co.uk> wrote in message
news:ct7q5g$n7j$1$8302bc10@.news.demon.co.uk...
> Hi all -
> I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used
> under it at the host. I can get at the db by using Access/ODBC with a URL
but the migration
> facility seems only to let me get at the tables.
> There are about half a dozen SPs referred to in the ASP code ( eg EXEC sp_
www) and I want to get
> hold of the code as I am not sure at all what they are doing.
> How do I get the code for each SP and store it in the local copy of the d
b? Can I just replicate
> the db and move the replica to a local area?
> Any advice on this gratefully (!) receive
> Thanks
> Jim McDonald
>

Pulling stored Procs from a remote db

Hi all -
I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used under it at the host. I can get at the db by using
Access/ODBC with a URL but the migration facility seems only to let me get
at the tables.
There are about half a dozen SPs referred to in the ASP code ( eg EXEC
sp_www) and I want to get hold of the code as I am not sure at all what they
are doing.
How do I get the code for each SP and store it in the local copy of the db?
Can I just replicate the db and move the replica to a local area?
Any advice on this gratefully (!) receive
Thanks
Jim McDonald
You can get the source code of a stored procedure using sp_helptext.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jim McDonald" <jim@.missile.demon.co.uk> wrote in message
news:ct7q5g$n7j$1$8302bc10@.news.demon.co.uk...
> Hi all -
> I am trying to rebuild a website abandoned by the builder and an SQLServer (I think 2k) db is used
> under it at the host. I can get at the db by using Access/ODBC with a URL but the migration
> facility seems only to let me get at the tables.
> There are about half a dozen SPs referred to in the ASP code ( eg EXEC sp_www) and I want to get
> hold of the code as I am not sure at all what they are doing.
> How do I get the code for each SP and store it in the local copy of the db? Can I just replicate
> the db and move the replica to a local area?
> Any advice on this gratefully (!) receive
> Thanks
> Jim McDonald
>

Pulling stored Procs from a remote db

Hi all -
I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used under it at the host. I can get at the db by using
Access/ODBC with a URL but the migration facility seems only to let me get
at the tables.
There are about half a dozen SPs referred to in the ASP code ( eg EXEC
sp_www) and I want to get hold of the code as I am not sure at all what they
are doing.
How do I get the code for each SP and store it in the local copy of the db?
Can I just replicate the db and move the replica to a local area?
Any advice on this gratefully (!) receive
Thanks
Jim McDonaldYou can get the source code of a stored procedure using sp_helptext.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jim McDonald" <jim@.missile.demon.co.uk> wrote in message
news:ct7q5g$n7j$1$8302bc10@.news.demon.co.uk...
> Hi all -
> I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used
> under it at the host. I can get at the db by using Access/ODBC with a URL
but the migration
> facility seems only to let me get at the tables.
> There are about half a dozen SPs referred to in the ASP code ( eg EXEC sp_
www) and I want to get
> hold of the code as I am not sure at all what they are doing.
> How do I get the code for each SP and store it in the local copy of the d
b? Can I just replicate
> the db and move the replica to a local area?
> Any advice on this gratefully (!) receive
> Thanks
> Jim McDonald
>

Tuesday, March 20, 2012

Pulling stored Procs from a remote db

Hi all -
I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used under it at the host. I can get at the db by using
Access/ODBC with a URL but the migration facility seems only to let me get
at the tables.
There are about half a dozen SPs referred to in the ASP code ( eg EXEC
sp_www) and I want to get hold of the code as I am not sure at all what they
are doing.
How do I get the code for each SP and store it in the local copy of the db?
Can I just replicate the db and move the replica to a local area?
Any advice on this gratefully (!) receive
Thanks
Jim McDonald
You can get the source code of a stored procedure using sp_helptext.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jim McDonald" <jim@.missile.demon.co.uk> wrote in message
news:ct7q5g$n7j$1$8302bc10@.news.demon.co.uk...
> Hi all -
> I am trying to rebuild a website abandoned by the builder and an SQLServer (I think 2k) db is used
> under it at the host. I can get at the db by using Access/ODBC with a URL but the migration
> facility seems only to let me get at the tables.
> There are about half a dozen SPs referred to in the ASP code ( eg EXEC sp_www) and I want to get
> hold of the code as I am not sure at all what they are doing.
> How do I get the code for each SP and store it in the local copy of the db? Can I just replicate
> the db and move the replica to a local area?
> Any advice on this gratefully (!) receive
> Thanks
> Jim McDonald
>

Monday, February 20, 2012

Public Domain Version Control

Hi,
I am looking for a public domain version control system for my SQL
server project. The public domain price is right, but if it works well
with either Enterprise Manager or Query Analyzer, that would be nice too.
Anyone got any recommendations or links?
JDIf by "public domain" you mean open source:
http://www.nongnu.org/cvs/
I'm not aware of any actual public domain SCM software.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"Joe Delphi" <delphi561@.nospam.cox.net> wrote in message
news:ZLwef.74$xu.64@.fed1read01...
> Hi,
> I am looking for a public domain version control system for my SQL
> server project. The public domain price is right, but if it works well
> with either Enterprise Manager or Query Analyzer, that would be nice too.
> Anyone got any recommendations or links?
> JD
>

PSSDIAG

Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:

> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.

PSSDIAG

Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:

> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.