Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts

Tuesday, February 14, 2012

cant use replication

ive installed sql 2005 enterprise and wanted to make a replication between 2 servers but when i rightclick the replication folder in the server management studio express - i can only create a subscriber. ive also tried going through tools but theres nothing in that menu.

ive wondered, is it maybe possible the i cant create a publisher because of the management studio express - do i also need a enterprise edition of the management studio?

ive also checked in add and remove programs - went to mssql 2005 and checked in change components and in there it ses that the replication components are installed =/

wud b gr8 if u cud help me, need this for an egsam i got on the 18th
thank you very very much in beforehand =P

sql server 2005 express edition only supports as subscriber...

May either you have connected to express edition sql server or ssms express may not support...

You may need to install regular client components from EE/SE/DE edtions cd...

Check the following link for SQL Server 2005 Features Comparison...

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

|||ive got the enterprise odition of mssql its just the management studio that is express.
in this case i need a different version of management studio?
where can i get it from? i havent got a cd - i downloaded it from the microsoft homepage

can someone PLEASE help me out here? even if its a "i doubt that it will work" =/
|||

Hi eniGMa,

You have to configure the Distributor firstly and then the Publisher.

Go to the Instance that you want to set Replication up. Right click on the Replication folder and click "Configure Distribution...".

After configuring the Distribution, configure the Publisher. Go to the Replication folder and click the + sign near it and expand the folder. Right click on the Local Publications folder and then click "New Publication" after setting it up you may configure the necessary Publications to Subscribers.

For more information visit the MSDN:

http://msdn2.microsoft.com/en-us/library/ms151198.aspx

Ekrem ?nsoy

MCP, MCDST, MCDBA, MCAD.Net, MCSD.Net, MCSA, MCSE

|||hi, ive checked the msdn page - the only thing i can create is a subscriber, nothing else
and when i click that, it tells me that it needs a publisher
|||

Hi eniGMa,

Replication system consists of Publisher, Distributor and Subscriber.

Publisher is the one what hosts the publications.

Distributor is the one which publishes the publications (from Publisher) to Subscribers.

Subscriber is the one what pulls (or pushed by the Publisher) data from Distributor.

Distributor and Publisher may be host on the same server if there is not huge workload on that SQL Server.

So according to this frame, you need to set Publisher and Distributor first.

You may configure these by help of the MSDN page which i posted before.

And then read my prior first answer again.

Ekrem ?nsoy
MCP, MCDST, MCDBA, MCAD.Net, MCSD.Net, MCSA, MCSE

|||thats egsactly my point - the only thing i can create is a subscriber
nothing else (ive read through the rest of the theory)

ive got the enterprise edition of mssql server installed, only thing where it sais express is the management studio (which i cant install from the sql server installation file, so i downloaded it from download.microsoft.com)

when i rightclick the replication folder - subscriber (no publisher and no distributor)
and when i click on tools (same thing)
|||

I see that you misconfigured setup of SQL Server.

Because you can install SSMS (SQL Server Management Studio) from the Components to Install menu which appears when you were setting up SQL Server.

When you see Components to Install dialog box, click Advanced and dig into the items to be installed.

After opening Advanced dialog box, you will see: "Workstation Components, Books Online, and Development Tools" There is SSMS in it. Expand the item and you'll see it.

My concern about your Replication problem is, you may be deselecting or forgetting selecting something when you were setting up the SQL Server. Replication choice is in the "SQL Server Database Services" item in the same Advanced dialog box.

Please check these items carefully while setting up SQL Server.

Try to set SQL Server up again by taking care of these things.

Ekrem ?nsoy

MCP, MCDST, MCDBA, MCAD.Net, MCSD.Net, MCSA, MCSE|||that worked - maybe it didnt work on the 1st time because ssms express was installed, when i installed it the 1st time and then i couldnt install it as an additional installation, even if removed afterwards

thnx a LOT!

Sunday, February 12, 2012

cant use functions on linked servers??

Hello

I'm having some problems with a couple of linked SQL servers. Basically I can get queries and SPs to work just fine, aklthough there is a little overhead. But I can't get functions to work! Can it really be that linked servers don't support functions? And if so, just out of curiosity, why on earth is it so? Linked servers only handle result sets, not scalar values?

I hope somebody can help me with this
MNJCan you explain "can't get functions to work" in more detail? I've never had it fail, so I'm probably missing something really basic here.

-PatP|||I thought you could never access the SPs and UDFs through a linked server. If you could, I would be interested to know how. Is this syntax valid. Can I execute this from Server 2
linkedserver1.database1.owner1.SP1|||EXECUTE linkedserver.master.dbo.sp_who

Works just fine for me. Does anyone else have trouble with it?

-PatP|||This is working for me:

select * from OPENQUERY ( linkedserver , 'select * from testDB2.dbo.testfunction()' )

but not working:

select * from linkedserver.testDB2.dbo.testfunction()|||Pat,

I get

Server: Msg 7411, Level 16, State 1, Line 1
Server 'QA' is not configured for RPC.|||Well that was easy..

Just go to properties in EM and select that you want to do RPC's

Why would that even be an option...

Wonder what the code is to enable it...|||Originally posted by snail
This is working for me:

select * from OPENQUERY ( linkedserver , 'select * from testDB2.dbo.testfunction()' )

but not working:

select * from linkedserver.testDB2.dbo.testfunction() Can you elaborate just a bit on what constitutes "not working" ?

-PatP|||I think you can't use the next for a function

select * from any_function(params)

Shouldn't this be:

select any_function(params)

Maybe this will solve the problem?|||Welcome Johan!

It depends. If they are using a table valued function, the original syntax would be fine as long as it had at least a two-part name.

-PatP|||Just one question from me ...

though from your post it seems the linked server is to a SQL server ...

is it really to a SQL server or some other db.|||Originally posted by Pat Phelan
Can you elaborate just a bit on what constitutes "not working" ?

-PatP
I got:

Server: Msg 170, Level 15, State 31, Line 1
Line 2: Incorrect syntax near '('.|||Pat: an off-topic question: what's a table valued function?|||Originally posted by jora
Pat: an off-topic question: what's a table valued function? You can think of a table valued function as a view that takes parameters. You can read about them in the CREATE FUNCTION (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_create_7r1l.asp) documentation, or an article at SQL Team (http://www.sqlteam.com/item.asp?ItemID=1955).

-PatP|||Thanks for the input everybody, and sorry I didn't respond until now. I've been looking further into the thing, and has come to the conclusion that my problem is really about linked servers and INSERTS.

I've started a new thread here:
http://www.dbforums.com/showthread.php?p=3673457#post3673457

Thanks
MNJ

Can't upgrade to RS SP1

I was able to install RS on my dev machine with no issues, but the SP1
upgrade package keeps crashing. I was able to upgrade our servers to
SP1, and other developers have been able to upgrade there PCs as well.
The error log says:
[Info] Calling MsiApplyPatch with szPatchPackage = c:\14763ee99882cc0c1d73512936\sp1patch.msp
and szInstallPackage = {null} and eInstallType = INSTALLTYPE_DEFAULT
and szCommandLine = RUNFROMSP1SETUP=TRUE REINSTALLMODE=romus
REINSTALL=Server_Components,RS_Server,RS_Manager,Client_Components,RS_Designer,RS_Admin_Tools,
[Info] MsiApplyPatch returned 1603
[Info] Reporting Error 1603 using Dr. Watson.
[Info] Setup exit code is 1603
Any ideas anyone?
Thanks,
BurtIs there an RSSp1msp#.log file? This log file should contain the actual
error.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Burt" <burt_5920@.yahoo.com> wrote in message
news:19e5f39f.0409151320.316d3abe@.posting.google.com...
> I was able to install RS on my dev machine with no issues, but the SP1
> upgrade package keeps crashing. I was able to upgrade our servers to
> SP1, and other developers have been able to upgrade there PCs as well.
> The error log says:
> [Info] Calling MsiApplyPatch with szPatchPackage => c:\14763ee99882cc0c1d73512936\sp1patch.msp
> and szInstallPackage = {null} and eInstallType = INSTALLTYPE_DEFAULT
> and szCommandLine = RUNFROMSP1SETUP=TRUE REINSTALLMODE=romus
>
REINSTALL=Server_Components,RS_Server,RS_Manager,Client_Components,RS_Design
er,RS_Admin_Tools,
> [Info] MsiApplyPatch returned 1603
> [Info] Reporting Error 1603 using Dr. Watson.
> [Info] Setup exit code is 1603
> Any ideas anyone?
> Thanks,
> Burt|||Daniel,
Thanks for getting back to me. The only part of the RSSp1msp#.log that
seems to contain an error is pasted below. My issues with that portion
are:
-I don't need to update my database, just the app server on my dev box
-ReportServer isn't the right name for the current database. That was
the name of the initial one we created and did not use.
-But the ReportServer database still exists and I am dbo, contrary to
what the message says.
Any addition help would be greatly appreciated.
Burt
SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed
database context to 'master'.
sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed
language setting to us_english.
SQL_ERROR (-1) in SQLExecDirectW
sqlstate=08004, level=14, state=1, native_error=916, msg=Server user
'BurtsDomain\burt' is not a valid user in database 'ReportServer'.
SQL_ERROR (-1) in SQLExecDirectW. sqlstate=08004, level=14, state=1,
native_error=916, msg=Server user 'BurtsDomain\burt' is not a valid
user in database 'ReportServer'..
SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed
database context to 'master'.
sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed
language setting to us_english.
SQL_ERROR (-1) in SQLExecDirectW
sqlstate=08004, level=14, state=1, native_error=916, msg=Server user
'BurtsDomain\burt' is not a valid user in database 'ReportServer'.
SQL_ERROR (-1) in SQLExecDirectW. sqlstate=08004, level=14, state=1,
native_error=916, msg=Server user 'BurtsDomain\burt' is not a valid
user in database 'ReportServer'..
Set_Sp1_Upgrade_Settings: Unexpected Database Version. Set will roll
back.
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message news:<eLcwTDBnEHA.1412@.tk2msftngp13.phx.gbl>...
> Is there an RSSp1msp#.log file? This log file should contain the actual
> error.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Burt" <burt_5920@.yahoo.com> wrote in message
> news:19e5f39f.0409151320.316d3abe@.posting.google.com...
> > I was able to install RS on my dev machine with no issues, but the SP1
> > upgrade package keeps crashing. I was able to upgrade our servers to
> > SP1, and other developers have been able to upgrade there PCs as well.
> > The error log says:
> >
> > [Info] Calling MsiApplyPatch with szPatchPackage => > c:\14763ee99882cc0c1d73512936\sp1patch.msp
> > and szInstallPackage = {null} and eInstallType = INSTALLTYPE_DEFAULT
> > and szCommandLine = RUNFROMSP1SETUP=TRUE REINSTALLMODE=romus
> >
> REINSTALL=Server_Components,RS_Server,RS_Manager,Client_Components,RS_Design
> er,RS_Admin_Tools,
> > [Info] MsiApplyPatch returned 1603
> > [Info] Reporting Error 1603 using Dr. Watson.
> > [Info] Setup exit code is 1603
> >
> > Any ideas anyone?
> >
> > Thanks,
> >
> > Burt|||I don't understand why you think you don't need to update the database. SP1
requires DB updates.
You said that you changed the name of the DB. How did you do this, with
RSConfig? Setup should be using the values in the rsreportserver.config
file for connecting to the DB. If you rename the DB does RS still work?
Finally, like setup for RS, SP1 uses the user running setup to talk to the
DB. This user needs to have system Admin rights in Sql Server. Please
ensure this is the case.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Burt" <burt_5920@.yahoo.com> wrote in message
news:19e5f39f.0409170944.7c45b429@.posting.google.com...
> Daniel,
> Thanks for getting back to me. The only part of the RSSp1msp#.log that
> seems to contain an error is pasted below. My issues with that portion
> are:
> -I don't need to update my database, just the app server on my dev box
> -ReportServer isn't the right name for the current database. That was
> the name of the initial one we created and did not use.
> -But the ReportServer database still exists and I am dbo, contrary to
> what the message says.
> Any addition help would be greatly appreciated.
> Burt
>
> SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
> sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed
> database context to 'master'.
> sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed
> language setting to us_english.
> SQL_ERROR (-1) in SQLExecDirectW
> sqlstate=08004, level=14, state=1, native_error=916, msg=Server user
> 'BurtsDomain\burt' is not a valid user in database 'ReportServer'.
> SQL_ERROR (-1) in SQLExecDirectW. sqlstate=08004, level=14, state=1,
> native_error=916, msg=Server user 'BurtsDomain\burt' is not a valid
> user in database 'ReportServer'..
> SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
> sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed
> database context to 'master'.
> sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed
> language setting to us_english.
> SQL_ERROR (-1) in SQLExecDirectW
> sqlstate=08004, level=14, state=1, native_error=916, msg=Server user
> 'BurtsDomain\burt' is not a valid user in database 'ReportServer'.
> SQL_ERROR (-1) in SQLExecDirectW. sqlstate=08004, level=14, state=1,
> native_error=916, msg=Server user 'BurtsDomain\burt' is not a valid
> user in database 'ReportServer'..
> Set_Sp1_Upgrade_Settings: Unexpected Database Version. Set will roll
> back.
>
>
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:<eLcwTDBnEHA.1412@.tk2msftngp13.phx.gbl>...
> > Is there an RSSp1msp#.log file? This log file should contain the actual
> > error.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Burt" <burt_5920@.yahoo.com> wrote in message
> > news:19e5f39f.0409151320.316d3abe@.posting.google.com...
> > > I was able to install RS on my dev machine with no issues, but the SP1
> > > upgrade package keeps crashing. I was able to upgrade our servers to
> > > SP1, and other developers have been able to upgrade there PCs as well.
> > > The error log says:
> > >
> > > [Info] Calling MsiApplyPatch with szPatchPackage => > > c:\14763ee99882cc0c1d73512936\sp1patch.msp
> > > and szInstallPackage = {null} and eInstallType = INSTALLTYPE_DEFAULT
> > > and szCommandLine = RUNFROMSP1SETUP=TRUE REINSTALLMODE=romus
> > >
> >
REINSTALL=Server_Components,RS_Server,RS_Manager,Client_Components,RS_Design
> > er,RS_Admin_Tools,
> > > [Info] MsiApplyPatch returned 1603
> > > [Info] Reporting Error 1603 using Dr. Watson.
> > > [Info] Setup exit code is 1603
> > >
> > > Any ideas anyone?
> > >
> > > Thanks,
> > >
> > > Burt