Modifing values from one database to another

I have several databases in a merge replication.
there are two servers linked so i can send data from one to the other. I
mean Server Fenix is linked to Neptune. Neptune is replicating an Feniz is
the Replicator.
When one table in one of the remote computers is changed the trigger make
price =0. This trigger is NOT FOR REPLICATION, because it was causing to many
conflicts before, because it also executed a Store Procedure that change the
Price to some value.
My problem is that I have a store procedure that once this price=0 it has to
delete some data in one databes of NEPTUNE that is not being replicated.
The problem is that I get an error message saying:
SERVER NEPTUNE IS NOT CONFIGURED FOR DATA_ACCESS
So I try to link Neptun to one of those remote machines, but it is not
posible because they are replicating, I guess...
The way I try to reach Neptune si:
DELETE [NEPTUNE].LABORATORIO.DBO.TABLAPUNTOSCOMPRA
WHERE...
I do not know if this is too confusing...
Thanks a lot if some one can help me,
Lina
try this. sp_serveroption 'Neptune', 'data access',true
or
sp_serveroption 'Neptune', 'data access','true'
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
"Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
news:81870ED4-8413-46A0-A522-9E43B586F41C@.microsoft.com...
>I have several databases in a merge replication.
> there are two servers linked so i can send data from one to the other. I
> mean Server Fenix is linked to Neptune. Neptune is replicating an Feniz is
> the Replicator.
> When one table in one of the remote computers is changed the trigger make
> price =0. This trigger is NOT FOR REPLICATION, because it was causing to
> many
> conflicts before, because it also executed a Store Procedure that change
> the
> Price to some value.
> My problem is that I have a store procedure that once this price=0 it has
> to
> delete some data in one databes of NEPTUNE that is not being replicated.
> The problem is that I get an error message saying:
> SERVER NEPTUNE IS NOT CONFIGURED FOR DATA_ACCESS
> So I try to link Neptun to one of those remote machines, but it is not
> posible because they are replicating, I guess...
> The way I try to reach Neptune si:
> DELETE [NEPTUNE].LABORATORIO.DBO.TABLAPUNTOSCOMPRA
> WHERE...
> I do not know if this is too confusing...
> Thanks a lot if some one can help me,
> Lina
|||Thank you, Hilary.
I have this two sentences inside the store procedure and they do no work.
exec sp_serveroption 'NEPTUNO','data access','true'
EXEC sp_serveroption 'NEPTUNO', 'collation compatible', 'true'
"Hilary Cotter" wrote:

> try this. sp_serveroption 'Neptune', 'data access',true
> or
> sp_serveroption 'Neptune', 'data access','true'
>
> --
> 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
> "Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
> news:81870ED4-8413-46A0-A522-9E43B586F41C@.microsoft.com...
>
>

model db

Hello,
Question.. why would the model db transaction log be growing and getting ful
l? No new activity such as adding new databases or user defined data has occ
urred.
Thanks!!There's always some activity in the log, like checkpointing etc. Shouldn't b
e much but over a long time
perhaps...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"nupee" <nupee@.discussions.microsoft.com> wrote in message
news:601B4E8D-7FC8-40BD-B9CD-215260441284@.microsoft.com...
> Hello,
> Question.. why would the model db transaction log be growing and getting full? No
new activity such as
adding new databases or user defined data has occurred.
> Thanks!!|||Hi,
As Tibor mentioned the growth will be very minimal, can you check the growth
by executing the below procedure during the growth situation
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
MCDBA
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OdP34WuXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> There's always some activity in the log, like checkpointing etc. Shouldn't
be much but over a long time
> perhaps...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "nupee" <nupee@.discussions.microsoft.com> wrote in message
> news:601B4E8D-7FC8-40BD-B9CD-215260441284@.microsoft.com...
full? No new activity such as[vbcol=seagreen]
> adding new databases or user defined data has occurred.
>

model db

Hello,
Question.. why would the model db transaction log be growing and getting full? No new activity such as adding new databases or user defined data has occurred.
Thanks!!There's always some activity in the log, like checkpointing etc. Shouldn't be much but over a long time
perhaps...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"nupee" <nupee@.discussions.microsoft.com> wrote in message
news:601B4E8D-7FC8-40BD-B9CD-215260441284@.microsoft.com...
> Hello,
> Question.. why would the model db transaction log be growing and getting full? No new activity such as
adding new databases or user defined data has occurred.
> Thanks!!|||Hi,
As Tibor mentioned the growth will be very minimal, can you check the growth
by executing the below procedure during the growth situation
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
MCDBA
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OdP34WuXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> There's always some activity in the log, like checkpointing etc. Shouldn't
be much but over a long time
> perhaps...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "nupee" <nupee@.discussions.microsoft.com> wrote in message
> news:601B4E8D-7FC8-40BD-B9CD-215260441284@.microsoft.com...
> > Hello,
> >
> > Question.. why would the model db transaction log be growing and getting
full? No new activity such as
> adding new databases or user defined data has occurred.
> >
> > Thanks!!
>

model db

Hello,
Question.. why would the model db transaction log be growing and getting full? No new activity such as adding new databases or user defined data has occurred.
Thanks!!
There's always some activity in the log, like checkpointing etc. Shouldn't be much but over a long time
perhaps...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"nupee" <nupee@.discussions.microsoft.com> wrote in message
news:601B4E8D-7FC8-40BD-B9CD-215260441284@.microsoft.com...
> Hello,
> Question.. why would the model db transaction log be growing and getting full? No new activity such as
adding new databases or user defined data has occurred.
> Thanks!!
|||Hi,
As Tibor mentioned the growth will be very minimal, can you check the growth
by executing the below procedure during the growth situation
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
MCDBA
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OdP34WuXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> There's always some activity in the log, like checkpointing etc. Shouldn't
be much but over a long time[vbcol=seagreen]
> perhaps...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "nupee" <nupee@.discussions.microsoft.com> wrote in message
> news:601B4E8D-7FC8-40BD-B9CD-215260441284@.microsoft.com...
full? No new activity such as
> adding new databases or user defined data has occurred.
>
sql

model databases

Hi,

When i create a new table in Model database how can i automatically create table in other user databeses. Thanks for your answers

FYI, any object you create in the model databas will be automatically created in any user database you create in the future. So say, you create a table named Table1 in your model database, there will be a table named Table1 in all the user databases you create after that|||

The model database is the mold for future databases that are created. There is no mechanism in place to have other databases "inherit" the structures that are put into model after the database is created.

You would want to either A. Run the create script yourself in existing databases or B. Write a tool to cursor through all databases (possibly using sp_MSforeachdb, which is undocumented, but you can find an abundence of info on the web) and create the objects like that.

I would build something in a UI tool that logs your actions personally, as you should need to do this in dev, test, preprod, and/or prod at some time.

Model Database Stored procedures are gone.

SQL Server 2000 SP3a. Just noticed that the stored procedures that were in the model database are gone. So any new databases will not contain these stored procedures. Is this a problem?
Thanks,
Warren
We cannot answer that question for you. That is a question that you =
must answer. =20
If stored procedures were placed within the model database I would =
expect that something or someone expects those stored procedures to be =
available in the user databases that are created. =20
It is easy enough to create the stored procedures...simply grab the =
scripts and execute them in each database...then add them to model so =
that they will exist within new databases as they are created.
--=20
Keith
"Warren" <Warren@.discussions.microsoft.com> wrote in message =
news:C2DB2B96-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...
> SQL Server 2000 SP3a. Just noticed that the stored procedures that =
were in the model database are gone. So any new databases will not =
contain these stored procedures. Is this a problem?
>=20
> Thanks,
>=20
> Warren
|||Dear Keith,
The only SP's in the model database are the ones that come with the SQL Server installation.. So your advice is to re-create them?
Thanks,
Chris Tyler
"Keith Kratochvil" wrote:

> We cannot answer that question for you. That is a question that you must answer.
> If stored procedures were placed within the model database I would expect that something or someone expects those stored procedures to be available in the user databases that are created.
> It is easy enough to create the stored procedures...simply grab the scripts and execute them in each database...then add them to model so that they will exist within new databases as they are created.
> --
> Keith
>
> "Warren" <Warren@.discussions.microsoft.com> wrote in message news:C2DB2B96-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...
>
|||Hmmm...I did not think that any (Microsoft supplied) stored procedures =
were stored within model. Which stored procedures are missing? (what =
are their names?)
--=20
Keith
"Warren" <Warren@.discussions.microsoft.com> wrote in message =
news:C588718C-438E-4801-9A14-513120C5FBDE@.microsoft.com...
> Dear Keith,
>=20
> The only SP's in the model database are the ones that come with the =
SQL Server installation.. So your advice is to re-create them?[vbcol=seagreen]
>=20
> Thanks,
>=20
> Chris Tyler
>=20
>=20
>=20
> "Keith Kratochvil" wrote:
>=20
must answer. =20[vbcol=seagreen]
expect that something or someone expects those stored procedures to be =
available in the user databases that are created. =20[vbcol=seagreen]
scripts and execute them in each database...then add them to model so =
that they will exist within new databases as they are created.[vbcol=seagreen]
news:C2DB2B96-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...[vbcol=seagreen]
that were in the model database are gone. So any new databases will not =
contain these stored procedures. Is this a problem?[vbcol=seagreen]
|||> The only SP's in the model database are the ones that come with the SQL
Server installation.
There are no such things, in any of my installations here. Can you name a
few of these "missing" stored procedures?
|||Hi Aaron,
There may not be any System SP's in the Model database.. What I find is most server have no SP's within Model, but some have dt_Stored procedures that say System. For example, dt_addsourcecontrol, dt_addsourcecontrol_u, dt_adduserobject...So this may hav
e come into Model by other means...
Thanks,
Warren
"Aaron [SQL Server MVP]" wrote:

> Server installation.
> There are no such things, in any of my installations here. Can you name a
> few of these "missing" stored procedures?
>
>
|||These are created automatically if you click on the diagram node in a
database. They don't need to exist, if they are missing, they will be
created by SQL Server. Not quite sure how they get into model (I think a few
other things trigger their creation as well) as there shouldn't be a diagram
node in EM for system databases.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Warren" <Warren@.discussions.microsoft.com> wrote in message
news:BC201722-6FE3-41BD-A22A-FAB84D3FEE37@.microsoft.com...
> Hi Aaron,
> There may not be any System SP's in the Model database.. What I find is
most server have no SP's within Model, but some have dt_Stored procedures
that say System. For example, dt_addsourcecontrol, dt_addsourcecontrol_u,
dt_adduserobject...So this may have come into Model by other means...[vbcol=seagreen]
> Thanks,
> Warren
> "Aaron [SQL Server MVP]" wrote:
SQL[vbcol=seagreen]
a[vbcol=seagreen]

Model Database Stored procedures are gone.

SQL Server 2000 SP3a. Just noticed that the stored procedures that were in the model database are gone. So any new databases will not contain these stored procedures. Is this a problem?
Thanks,
WarrenWe cannot answer that question for you. That is a question that you =must answer.
If stored procedures were placed within the model database I would =expect that something or someone expects those stored procedures to be =available in the user databases that are created.
It is easy enough to create the stored procedures...simply grab the =scripts and execute them in each database...then add them to model so =that they will exist within new databases as they are created.
-- Keith
"Warren" <Warren@.discussions.microsoft.com> wrote in message =news:C2DB2B96-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...
> SQL Server 2000 SP3a. Just noticed that the stored procedures that =were in the model database are gone. So any new databases will not =contain these stored procedures. Is this a problem?
> > Thanks,
> > Warren|||Dear Keith,
The only SP's in the model database are the ones that come with the SQL Server installation.. So your advice is to re-create them?
Thanks,
Chris Tyler
"Keith Kratochvil" wrote:
> We cannot answer that question for you. That is a question that you must answer.
> If stored procedures were placed within the model database I would expect that something or someone expects those stored procedures to be available in the user databases that are created.
> It is easy enough to create the stored procedures...simply grab the scripts and execute them in each database...then add them to model so that they will exist within new databases as they are created.
> --
> Keith
>
> "Warren" <Warren@.discussions.microsoft.com> wrote in message news:C2DB2B96-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...
> > SQL Server 2000 SP3a. Just noticed that the stored procedures that were in the model database are gone. So any new databases will not contain these stored procedures. Is this a problem?
> >
> > Thanks,
> >
> > Warren
>|||Hmmm...I did not think that any (Microsoft supplied) stored procedures =were stored within model. Which stored procedures are missing? (what =are their names?)
-- Keith
"Warren" <Warren@.discussions.microsoft.com> wrote in message =news:C588718C-438E-4801-9A14-513120C5FBDE@.microsoft.com...
> Dear Keith,
> > The only SP's in the model database are the ones that come with the =SQL Server installation.. So your advice is to re-create them?
> > Thanks,
> > Chris Tyler
> > > > "Keith Kratochvil" wrote:
> > > We cannot answer that question for you. That is a question that you =must answer. > > > > If stored procedures were placed within the model database I would =expect that something or someone expects those stored procedures to be =available in the user databases that are created. > > > > It is easy enough to create the stored procedures...simply grab the =scripts and execute them in each database...then add them to model so =that they will exist within new databases as they are created.
> > > > -- > > Keith
> > > > > > "Warren" <Warren@.discussions.microsoft.com> wrote in message =news:C2DB2B96-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...
> > > SQL Server 2000 SP3a. Just noticed that the stored procedures =that were in the model database are gone. So any new databases will not =contain these stored procedures. Is this a problem?
> > > > > > Thanks,
> > > > > > Warren
> >|||> The only SP's in the model database are the ones that come with the SQL
Server installation.
There are no such things, in any of my installations here. Can you name a
few of these "missing" stored procedures?|||Hi Aaron,
There may not be any System SP's in the Model database.. What I find is most server have no SP's within Model, but some have dt_Stored procedures that say System. For example, dt_addsourcecontrol, dt_addsourcecontrol_u, dt_adduserobject...So this may have come into Model by other means...
Thanks,
Warren
"Aaron [SQL Server MVP]" wrote:
> > The only SP's in the model database are the ones that come with the SQL
> Server installation.
> There are no such things, in any of my installations here. Can you name a
> few of these "missing" stored procedures?
>
>|||These are created automatically if you click on the diagram node in a
database. They don't need to exist, if they are missing, they will be
created by SQL Server. Not quite sure how they get into model (I think a few
other things trigger their creation as well) as there shouldn't be a diagram
node in EM for system databases.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Warren" <Warren@.discussions.microsoft.com> wrote in message
news:BC201722-6FE3-41BD-A22A-FAB84D3FEE37@.microsoft.com...
> Hi Aaron,
> There may not be any System SP's in the Model database.. What I find is
most server have no SP's within Model, but some have dt_Stored procedures
that say System. For example, dt_addsourcecontrol, dt_addsourcecontrol_u,
dt_adduserobject...So this may have come into Model by other means...
> Thanks,
> Warren
> "Aaron [SQL Server MVP]" wrote:
> > > The only SP's in the model database are the ones that come with the
SQL
> > Server installation.
> >
> > There are no such things, in any of my installations here. Can you name
a
> > few of these "missing" stored procedures?
> >
> >
> >

Model Database Stored procedures are gone.

SQL Server 2000 SP3a. Just noticed that the stored procedures that were in
the model database are gone. So any new databases will not contain these st
ored procedures. Is this a problem?
Thanks,
WarrenWe cannot answer that question for you. That is a question that you =
must answer. =20
If stored procedures were placed within the model database I would =
expect that something or someone expects those stored procedures to be =
available in the user databases that are created. =20
It is easy enough to create the stored procedures...simply grab the =
scripts and execute them in each database...then add them to model so =
that they will exist within new databases as they are created.
--=20
Keith
"Warren" <Warren@.discussions.microsoft.com> wrote in message =
news:C2DB2B96-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...
> SQL Server 2000 SP3a. Just noticed that the stored procedures that =
were in the model database are gone. So any new databases will not =
contain these stored procedures. Is this a problem?
>=20
> Thanks,
>=20
> Warren|||Dear Keith,
The only SP's in the model database are the ones that come with the SQL Serv
er installation.. So your advice is to re-create them?
Thanks,
Chris Tyler
"Keith Kratochvil" wrote:

> We cannot answer that question for you. That is a question that you must
answer.
> If stored procedures were placed within the model database I would expect
that something or someone expects those stored procedures to be available in
the user databases that are created.
> It is easy enough to create the stored procedures...simply grab the scrip
ts and execute them in each database...then add them to model so that they w
ill exist within new databases as they are created.
> --
> Keith
>
> "Warren" <Warren@.discussions.microsoft.com> wrote in message news:C2DB2B96
-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...
>|||Hmmm...I did not think that any (Microsoft supplied) stored procedures =
were stored within model. Which stored procedures are missing? (what =
are their names?)
--=20
Keith
"Warren" <Warren@.discussions.microsoft.com> wrote in message =
news:C588718C-438E-4801-9A14-513120C5FBDE@.microsoft.com...
> Dear Keith,
>=20
> The only SP's in the model database are the ones that come with the =
SQL Server installation.. So your advice is to re-create them?[vbcol=seagreen]
>=20
> Thanks,
>=20
> Chris Tyler
>=20
>=20
>=20
> "Keith Kratochvil" wrote:
>=20
must answer. =20[vbcol=seagreen]
expect that something or someone expects those stored procedures to be =
available in the user databases that are created. =20[vbcol=seagreen]
scripts and execute them in each database...then add them to model so =
that they will exist within new databases as they are created.[vbcol=seagreen]
news:C2DB2B96-5713-4EF3-A4B3-AC9F553ED07A@.microsoft.com...[vbcol=seagreen]
that were in the model database are gone. So any new databases will not =
contain these stored procedures. Is this a problem?[vbcol=seagreen]|||> The only SP's in the model database are the ones that come with the SQL
Server installation.
There are no such things, in any of my installations here. Can you name a
few of these "missing" stored procedures?|||Hi Aaron,
There may not be any System SP's in the Model database.. What I find is most
server have no SP's within Model, but some have dt_Stored procedures that s
ay System. For example, dt_addsourcecontrol, dt_addsourcecontrol_u, dt_addu
serobject...So this may hav
e come into Model by other means...
Thanks,
Warren
"Aaron [SQL Server MVP]" wrote:

> Server installation.
> There are no such things, in any of my installations here. Can you name a
> few of these "missing" stored procedures?
>
>|||These are created automatically if you click on the diagram node in a
database. They don't need to exist, if they are missing, they will be
created by SQL Server. Not quite sure how they get into model (I think a few
other things trigger their creation as well) as there shouldn't be a diagram
node in EM for system databases.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Warren" <Warren@.discussions.microsoft.com> wrote in message
news:BC201722-6FE3-41BD-A22A-FAB84D3FEE37@.microsoft.com...
> Hi Aaron,
> There may not be any System SP's in the Model database.. What I find is
most server have no SP's within Model, but some have dt_Stored procedures
that say System. For example, dt_addsourcecontrol, dt_addsourcecontrol_u,
dt_adduserobject...So this may have come into Model by other means...[vbcol=seagreen]
> Thanks,
> Warren
> "Aaron [SQL Server MVP]" wrote:
>
SQL[vbcol=seagreen]
a[vbcol=seagreen]

Model database recovery planning

I cannot think of any reason, in our environment, why I would recover the model database. Change framework has all databases coming from DEV & QA before landing on PROD. We have never used the model database as framework of new databases either.

So, if I discontinued backup of the database, what is my recovery method if it become corrupt? Since mine is not used, can I simply copy it from another server?

Just keep either a BACKUP or a copy of the mdf/ldf files in safe storage.|||Just use the create script in your \install folder to recreate your model db.|||

Just be aware that it is an ESSENTIAL database in your system. There is one circumstance under which you do use it automatically for creating a database, and that is the initialisation of your tempdb every time you start the SQL Server service.

My understanding is that if model is not available then tempdb cannot be initialised and SQL Server will not start.

mobile phone and databases

Can you please tell me what are the risks of customers using a mobile phone to send a request of information which will be automatically responded to as an entry is made into the database.

How do I ensure that the data intergrity is maintained, as this 'Table' in the database will take in many request a day and repond based on what the customer has type in on the text message.

I did not get your point. What are you trying to do ? Sending a message to a Service, processing it in the database and sending the processed data, evtl. with a customized text back to the caller ? Data integrity should be maintained either through constraint rules (Whatever rules you have) or your logic you are trying to implement in the midtier or the database level.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

MMC error with Enterprise Manager

When attempting to display a database's property window in Enterprise Manager
an error happens with MMC. On a machine that also has SQL Server 2005 client
tools installed Enterprise manager crashes. On other machines that do not
have SQL Server 2005 client tools installed, MMC throws an error similar to
the one below before Enterprise Manager crashes:
mmc.exe Application error The instruction at "0x7801094 referenced
memory.....
The exact memory address in the above error message is not correct. I copied
it from another reference (on Google) dealing with DTS / MMC errors. I do not
have the exact message because I was forced to reinstall SQL Server 2000 in
order to use the RTM version to get around this error. The bug does not
happen in the RTM version but does with both SP3 and SP4.
The problem started fairly recently and I suspect it has to do with a
Microsoft update. It is happening to every computer computer in our facility
that has service packs applied to SQL Server and affects more than the
ability to display a databases property page.
Does anyone have any knowledge as to what might be causing these errors with
MMC and whether or not there is a work around?
I have now applied SP4 again and can replicate the error again.
When I right click on a Database in Enterprise Manager and select properties
I receive the following message:
mmc.exe - Application Error
The instruction at "0x4247b98b" referenced memory at "0x0000001c". The
memory could not be read.
Click OK to terminate....
I am running SQL Server 2000 on Windows 2000 (SP4).

Mixing Types

Hello Group,
our company had a database on SQL Server 2000 Standard as the source for a
Report Server 2000 Standard. Well, the source databases had to be moved to a
brand new server. As it happened, the SQL Server 2000 on the new server is
Enterprise. Now, the report server will not work. We changed the connection
strings for the reports to point to the new server but no good. We just keep
getting "server not trusted".
Does the type of database server matter to the report server?
RichFirst, I assume that it is just the data that is an issue. Not the
reportserver database itself (where Report server keeps its metadata/object
caching).
My guess is that something else is going on with regards to the security. If
you are using integrated security there might be some issue with RS server
passing on credentials to
What I prefer to do is to have a read only SQL login. I use that for
credentials. I just use the windows domain login to determine who gets to
run what report.
It does not matter in the least where the data is coming from. I report off
of SQL Server standard, SQL Server Enterprise, Sybase, In-SQL (a real time
control historian).
Now, if you are not even having Report Manager come up (i.e. you never even
get where you can select the report to run) then it sounds like RS database
was moved. Again, you have a configuration/security problem going on.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:E44CB1AD-A386-40E2-BBE6-F1BB1872F817@.microsoft.com...
> Hello Group,
> our company had a database on SQL Server 2000 Standard as the source for a
> Report Server 2000 Standard. Well, the source databases had to be moved
> to a
> brand new server. As it happened, the SQL Server 2000 on the new server
> is
> Enterprise. Now, the report server will not work. We changed the
> connection
> strings for the reports to point to the new server but no good. We just
> keep
> getting "server not trusted".
> Does the type of database server matter to the report server?
> Rich|||Hello Bruce,
thanks...the Report Manger comes up just fine. It displays the folders and
reports and user just like always. I thought that if I changed the
Connection String in the Report Manager, this would be enough. I need to
come up with a stradigy as to how to narrow down the location of the problem.
Rich
"Bruce L-C [MVP]" wrote:
> First, I assume that it is just the data that is an issue. Not the
> reportserver database itself (where Report server keeps its metadata/object
> caching).
> My guess is that something else is going on with regards to the security. If
> you are using integrated security there might be some issue with RS server
> passing on credentials to
> What I prefer to do is to have a read only SQL login. I use that for
> credentials. I just use the windows domain login to determine who gets to
> run what report.
> It does not matter in the least where the data is coming from. I report off
> of SQL Server standard, SQL Server Enterprise, Sybase, In-SQL (a real time
> control historian).
> Now, if you are not even having Report Manager come up (i.e. you never even
> get where you can select the report to run) then it sounds like RS database
> was moved. Again, you have a configuration/security problem going on.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:E44CB1AD-A386-40E2-BBE6-F1BB1872F817@.microsoft.com...
> > Hello Group,
> >
> > our company had a database on SQL Server 2000 Standard as the source for a
> > Report Server 2000 Standard. Well, the source databases had to be moved
> > to a
> > brand new server. As it happened, the SQL Server 2000 on the new server
> > is
> > Enterprise. Now, the report server will not work. We changed the
> > connection
> > strings for the reports to point to the new server but no good. We just
> > keep
> > getting "server not trusted".
> >
> > Does the type of database server matter to the report server?
> >
> > Rich
>
>sql

Missing Triggers on SQL 2005/Server Management Studio

I have a few SQL 2005 databases set up, some of which have triggers.

Recently, the database triggers stopped appearing in SMS. They are still there. They still run. I can still manually CREATE, ALTER, or DROP triggers via SQL queries. However, when I open a database and navigate to Programmability > Database Triggers nothing shows up. Right clicking the folder produces no worthwhile options (just Reports and Refresh).

Until this puzzling change occured a few days ago, triggers were appearing in the aforementioned location. Right clicking yielded many options including the options to create, drop or whatever else. I thought this might be a permissions issue, but as I said, I can still work on triggers via queries.

Does anyone have any idea what is going on?

Thanks, Jeff

I don't think you found triggers under programmability. You found stored procedures there.

The triggers are the expansions of the tables not the database.

Drop down the table and you'll see the triggers.

Adamus

|||

i hope the trigger you mentioned is DDL trigger. you can make DDL triggers are of two scope. one database level and the other one at the server level. The database trigger can found in Database Programability -- Database triggers.

the server level trigger can be seen in Server Object -- Server Triggers

System objects for DDL Triggers

You can use the sys.triggers catalog view to see database-level DDL triggers. The parent_class column in this catalog view has 0 as the value for DDL triggers. You can use the sys.server_triggers catalog view to get a list of server-level DDL triggers. The sys.trigger_events and sys.server_trigger_events catalog views contain a row for each time a database-level and server-level trigger was fired, respectively.

also read these

Query System Object for DDL

SELECT Name, s.type_desc SQL_or_CLR,is_disabled, e.type_desc FiringEvents
FROM sys.server_triggers s
INNER JOIN sys.server_trigger_events e ON s.object_id = e.object_id

Where can I find DDL trigger in SSMO

Databaselevel DDL triggers are listed in the Programmability\Database Triggers folder in Object Explorer. The server-level triggers are listed under the Server Objects\Triggers folder in Object Explorer.

Delete DDL Trigger

The ON DATABASE or ON ALL SERVER clause should be used with DROP TRIGGER to delete a DDL trigger, ALTER TRIGGER to modify a DDL trigger definition, DISABLE TRIGGER to disable a DDL trigger, and ENABLE TRIGGER to enable a DDL trigger.

Permission
The CONTROL SERVER permission is required to create a DDL trigger at the server scope, and ALTER ANY TRIGGER permission is required to create a DDL trigger at the database scope

Madhu

|||Thank you both of you! Both posts were helpful, but Adamus more directly answered my question. I could swear that the triggers I had created were found in Programmability but now I see some of them in the table expansion themselves.

missing system databases folder from management studio

Hi All
My view of database on management studio does not have folder with system
databases. I am sysadmin on server and member of local admins group. Do you
know what could be a problem?In Management Studio take a look at Tools, Options, Hide system objects in
Object Explorer. Is the box checked?
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Hi All
> My view of database on management studio does not have folder with system
> databases. I am sysadmin on server and member of local admins group. Do you
> know what could be a problem?|||Hi Gene
There is an option available that turns system objects visible or invisible.
Look at the Options in the Tools menu. The General tab has the checkbox
"Hide system objects in Object Explorer"
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:FAEC8F2B-9E3E-467C-B368-756773D1BD16@.microsoft.com...
> Hi All
> My view of database on management studio does not have folder with system
> databases. I am sysadmin on server and member of local admins group. Do
> you
> know what could be a problem?|||Hi Ben, Kalen
This is genious!
I did not change those settings but that was a fix!
Thank you so much. I am happy again now.
"Kalen Delaney" wrote:
> Hi Gene
> There is an option available that turns system objects visible or invisible.
> Look at the Options in the Tools menu. The General tab has the checkbox
> "Hide system objects in Object Explorer"
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:FAEC8F2B-9E3E-467C-B368-756773D1BD16@.microsoft.com...
> > Hi All
> > My view of database on management studio does not have folder with system
> > databases. I am sysadmin on server and member of local admins group. Do
> > you
> > know what could be a problem?
>
>
>

Missing MDF files but databases run fine?

About two months ago, we had a problem with a couple SQL 2005 databases. We
got everything working and all has been fine. Today, I noticed that the
databases that we had a problem with have LDF file but no MDF files. I don't
know much about SQL but does that make sense? Is there any way to make the
MDF file at this point?
Thanks!
Arch WillinghamWhat do you mean by 'no MDF files'? You can have a scenario where the drive
that hosts a database file disappears and the database may still function as
usual for a while until it has to access the disk.
Linchi
"Arch Willingham" wrote:
> About two months ago, we had a problem with a couple SQL 2005 databases. We
> got everything working and all has been fine. Today, I noticed that the
> databases that we had a problem with have LDF file but no MDF files. I don't
> know much about SQL but does that make sense? Is there any way to make the
> MDF file at this point?
> Thanks!
> Arch Willingham
>
>|||Never mind....weird thing. I am a holdout thatstill uses the old file
manager (WINFILE.EXE). For whatever reason, teh MDF files are hidden to it
but they are there when you look at the directory with Explorer.
Weird as I can see all other hidden and system files.
Arch
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:CEE64FB0-73F3-483E-A4DF-3EEB750908DC@.microsoft.com...
> What do you mean by 'no MDF files'? You can have a scenario where the
> drive
> that hosts a database file disappears and the database may still function
> as
> usual for a while until it has to access the disk.
> Linchi
> "Arch Willingham" wrote:
>> About two months ago, we had a problem with a couple SQL 2005 databases.
>> We
>> got everything working and all has been fine. Today, I noticed that the
>> databases that we had a problem with have LDF file but no MDF files. I
>> don't
>> know much about SQL but does that make sense? Is there any way to make
>> the
>> MDF file at this point?
>> Thanks!
>> Arch Willingham
>>