Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts

Wednesday, March 28, 2012

Northwind and pubs default login/password ?

Hello,

What are the default login/password to access pubs and northwind databases ?
I remember the login = "sa", but nothing about the password.

Thanks

EricEricP (eric.piquot@.wanadoo.fr) writes:
> What are the default login/password to access pubs and northwind
> databases ? I remember the login = "sa", but nothing about the password.

Password are associated with logins and not with databases. And logins
are associated with servers and not with databases.

The default password for "sa" used to be blank, but hopefully this has
been changed on your server.

You can also log with in with Windows authentication. In this case you
don't provide a password, since you are already logged into Windows.
(Unless you are using Win 98 or somesuch.)

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Sorry for my badly English,

Erland Sommarskog a crit :
> EricP (eric.piquot@.wanadoo.fr) writes:
>>What are the default login/password to access pubs and northwind
>>databases ? I remember the login = "sa", but nothing about the password.
>
> Password are associated with logins and not with databases. And logins
> are associated with servers and not with databases.
I don't understand:
3 databases A, B, C on a server.
Hope one distinct (login,password) per database for the same user.
> The default password for "sa" used to be blank, but hopefully this has
> been changed on your server.
> You can also log with in with Windows authentication. In this case you
> don't provide a password, since you are already logged into Windows.
> (Unless you are using Win 98 or somesuch.)
Right

Thanks|||EricP (eric.piquot@.wanadoo.fr) writes:
> I don't understand:
> 3 databases A, B, C on a server.
> Hope one distinct (login,password) per database for the same user.

Not sure that I understand where you heading at.

But here is how security works in SQL Server. On server level you have
logins. A login can be an SQL login or a Windows login. SQL logins have
passwords, Winodws login have not (in SQL Server; they have in Windows
of course). A login can be associated with a user in a database. Most
often login name and user name are the same, but not there is no law
that requires this. Thus, once a person have logged into SQL Server,
he can access several databases, but if he is not added as user in
a database, he has no permission to it. (I'm bere overlooking the fact
that he may own a database ae well.)

If I understand you correctly, you want the same physical person have
three different (login, password) for three different databases. In
such case this person needs to have three different logins in SQL Server,
and this means that you need to use SQL logins, or else the person will
have to change between different Windows users.

There is one more alternative, and that is application roles. With an
application role you can get access to objects in a data to which
permissions have been granted to that role. To get access to an application
role, you need to supply the password. The typical use of an
application role is that you issue sp_setapprole from the application,
and the password is embedded in the application somewhere; thus the
users never supply it, or even know about it.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||
Erland Sommarskog a crit :
> If I understand you correctly, you want the same physical person have
> three different (login, password) for three different databases. In
> such case this person needs to have three different logins in SQL Server,
> and this means that you need to use SQL logins, or else the person will
> have to change between different Windows users.

That's quiet.
Thankssql

Monday, March 26, 2012

noob to SSIS package configure and deploy

Hi there

I am fairly new to SSIS, I got my package running fine in my development environment with the connection managers (connecting to 3 databases on the same server, with username and password, not Integrated security) and all.

The problem comes in when i want to deploy my package or execute it outside of the development environment.

When I execute the .dtsx file in my project it brings up the Execute Package Utility and I just click Execute, thinking it should work, but not, any ideas?

So I read some of the forums and got looking into the configuration file, suppose that it does not carry the connection manager settings thru, but dam that still doesn't work for me?

The whole idea is that I will be executing the package from my C# code, so does my package have to be just on the server in a folder or does it have to be installed in the db? which is best?

Hope anyone can help me!!

Thanks
Jamie

If the error you are getting is a failure to connect to the database, the problem is in the password not being stored in the package. If you search the forum for connection strings and configurations, you'll see a number of different solutions to this.

If that's not the problem, please include the error message that you are receiving.

Saturday, February 25, 2012

No. of Distribution Database

How many distribution databases can we have ? ... Say I have one publisher
/Published DB and multiple subscribers.
Can I have as many distribution dbs as the no. of subscribing dbs or just
one per published db or just one per publisher ? Can someone get my basics
straight ?
Each publisher can have its own distribution database, but only one.
You can have multiple distribution databases per distribution server with
one or more publisher's using each.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OHj4cDtFFHA.3732@.tk2msftngp13.phx.gbl...
> How many distribution databases can we have ? ... Say I have one publisher
> /Published DB and multiple subscribers.
> Can I have as many distribution dbs as the no. of subscribing dbs or just
> one per published db or just one per publisher ? Can someone get my basics
> straight ?
>
|||So even if the publisher has 4 published dbs, they all write to just one
distribution database.Right ?
Also how easy is to move the distribution db from a local server to a remote
server ?
Also what about once we do move to a remote server and say have multiple
distribution dbs, how easy is it to modify the properties ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OX7r73tFFHA.1740@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Each publisher can have its own distribution database, but only one.
> You can have multiple distribution databases per distribution server with
> one or more publisher's using each.
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:OHj4cDtFFHA.3732@.tk2msftngp13.phx.gbl...
publisher[vbcol=seagreen]
just[vbcol=seagreen]
basics
>
|||Also curious to know if multiple publishers can use the same distribution db
?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OX7r73tFFHA.1740@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Each publisher can have its own distribution database, but only one.
> You can have multiple distribution databases per distribution server with
> one or more publisher's using each.
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:OHj4cDtFFHA.3732@.tk2msftngp13.phx.gbl...
publisher[vbcol=seagreen]
just[vbcol=seagreen]
basics
>
|||That is correct - all publications from one publisher will use the same
distribution db.
It is simple to move the distribution db from a local server to a remote
one. All you do is drop all publications and subscriptions, disable
replication, reinstall replication and configure it for the remote
distributor, and then recreate all of your publications and subscriptions.
Modifying the properties of a distribution database is simple. It is best
done on the distributor.
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
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:uOtuzHuFFHA.3648@.TK2MSFTNGP10.phx.gbl...
> So even if the publisher has 4 published dbs, they all write to just one
> distribution database.Right ?
> Also how easy is to move the distribution db from a local server to a
remote[vbcol=seagreen]
> server ?
> Also what about once we do move to a remote server and say have multiple
> distribution dbs, how easy is it to modify the properties ?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OX7r73tFFHA.1740@.TK2MSFTNGP09.phx.gbl...
with
> publisher
> just
> basics
>
|||Multiple publishers by default will use the same distribution database,
unless you select another distribution database.
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
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:esvEUJuFFHA.3120@.TK2MSFTNGP12.phx.gbl...
> Also curious to know if multiple publishers can use the same distribution
db[vbcol=seagreen]
> ?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OX7r73tFFHA.1740@.TK2MSFTNGP09.phx.gbl...
with
> publisher
> just
> basics
>

No UDFs or SPs transferred from SQL 2000 to SQL 2005

Hi all
I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
all tables are transferred but the SPs and UDFs have not been
transferred.
Q1: Is there a way to "automatically" transfer these objects ?
Q2: Do I have to manually transfer each one of them and perhaps do
extra processing like "recompile" these UDFs and SPs ?
Thanks a lot in advance.You could easily generate a change script using tools like red-gate's SQL
Compare or Apex SQL Diff.
Aaron Bertrand
SQL Server MVP
<rtoss1@.yahoo.com> wrote in message
news:1184859771.869668.194260@.o61g2000hsh.googlegroups.com...
> Hi all
> I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
> all tables are transferred but the SPs and UDFs have not been
> transferred.
> Q1: Is there a way to "automatically" transfer these objects ?
> Q2: Do I have to manually transfer each one of them and perhaps do
> extra processing like "recompile" these UDFs and SPs ?
> Thanks a lot in advance.
>|||On Thu, 19 Jul 2007 12:07:31 -0400, Aaron Bertrand [SQL Server MVP] wrot
e:

> You could easily generate a change script using tools like red-gate's SQL
> Compare or Apex SQL Diff.
www.Quest.com has a free comparison tool, and I really like it.
-Chuck Lathrope
www.sqlwebpedia.com|||Use the backup / restore route to effect a complete migration of all
objects. Extended SPs, and those using deprecated functionality (like COM)
will need work to get them working, but all objects will be transfered.
<rtoss1@.yahoo.com> wrote in message
news:1184859771.869668.194260@.o61g2000hsh.googlegroups.com...
> Hi all
> I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
> all tables are transferred but the SPs and UDFs have not been
> transferred.
> Q1: Is there a way to "automatically" transfer these objects ?
> Q2: Do I have to manually transfer each one of them and perhaps do
> extra processing like "recompile" these UDFs and SPs ?
> Thanks a lot in advance.
>

No UDFs or SPs transferred from SQL 2000 to SQL 2005

Hi all
I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
all tables are transferred but the SPs and UDFs have not been
transferred.
Q1: Is there a way to "automatically" transfer these objects ?
Q2: Do I have to manually transfer each one of them and perhaps do
extra processing like "recompile" these UDFs and SPs ?
Thanks a lot in advance.You could easily generate a change script using tools like red-gate's SQL
Compare or Apex SQL Diff.
--
Aaron Bertrand
SQL Server MVP
<rtoss1@.yahoo.com> wrote in message
news:1184859771.869668.194260@.o61g2000hsh.googlegroups.com...
> Hi all
> I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
> all tables are transferred but the SPs and UDFs have not been
> transferred.
> Q1: Is there a way to "automatically" transfer these objects ?
> Q2: Do I have to manually transfer each one of them and perhaps do
> extra processing like "recompile" these UDFs and SPs ?
> Thanks a lot in advance.
>|||On Thu, 19 Jul 2007 12:07:31 -0400, Aaron Bertrand [SQL Server MVP] wrote:
> You could easily generate a change script using tools like red-gate's SQL
> Compare or Apex SQL Diff.
www.Quest.com has a free comparison tool, and I really like it.
-Chuck Lathrope
www.sqlwebpedia.com|||Use the backup / restore route to effect a complete migration of all
objects. Extended SPs, and those using deprecated functionality (like COM)
will need work to get them working, but all objects will be transfered.
<rtoss1@.yahoo.com> wrote in message
news:1184859771.869668.194260@.o61g2000hsh.googlegroups.com...
> Hi all
> I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
> all tables are transferred but the SPs and UDFs have not been
> transferred.
> Q1: Is there a way to "automatically" transfer these objects ?
> Q2: Do I have to manually transfer each one of them and perhaps do
> extra processing like "recompile" these UDFs and SPs ?
> Thanks a lot in advance.
>

No UDFs or SPs transferred from SQL 2000 to SQL 2005

Hi all
I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
all tables are transferred but the SPs and UDFs have not been
transferred.
Q1: Is there a way to "automatically" transfer these objects ?
Q2: Do I have to manually transfer each one of them and perhaps do
extra processing like "recompile" these UDFs and SPs ?
Thanks a lot in advance.
You could easily generate a change script using tools like red-gate's SQL
Compare or Apex SQL Diff.
Aaron Bertrand
SQL Server MVP
<rtoss1@.yahoo.com> wrote in message
news:1184859771.869668.194260@.o61g2000hsh.googlegr oups.com...
> Hi all
> I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
> all tables are transferred but the SPs and UDFs have not been
> transferred.
> Q1: Is there a way to "automatically" transfer these objects ?
> Q2: Do I have to manually transfer each one of them and perhaps do
> extra processing like "recompile" these UDFs and SPs ?
> Thanks a lot in advance.
>
|||On Thu, 19 Jul 2007 12:07:31 -0400, Aaron Bertrand [SQL Server MVP] wrote:

> You could easily generate a change script using tools like red-gate's SQL
> Compare or Apex SQL Diff.
www.Quest.com has a free comparison tool, and I really like it.
-Chuck Lathrope
www.sqlwebpedia.com
|||Use the backup / restore route to effect a complete migration of all
objects. Extended SPs, and those using deprecated functionality (like COM)
will need work to get them working, but all objects will be transfered.
<rtoss1@.yahoo.com> wrote in message
news:1184859771.869668.194260@.o61g2000hsh.googlegr oups.com...
> Hi all
> I just migrated by Databases from SQL Server 2000 to SQL Server 2005,
> all tables are transferred but the SPs and UDFs have not been
> transferred.
> Q1: Is there a way to "automatically" transfer these objects ?
> Q2: Do I have to manually transfer each one of them and perhaps do
> extra processing like "recompile" these UDFs and SPs ?
> Thanks a lot in advance.
>

Monday, February 20, 2012

No triggers, constraints

I have several sql server databases that were recently moved to a new
server. In the process of migrating the databases, any triggers and
constraints attached to tables were removed on accident. I need to add
these objects back into the databases, however I'm worried that I will
have problems with referential integrity since there is a chance
someone may have deleted or updated a record that should have cascaded
changes to other tables but did not since the triggers and constraints
were missing. Is there an easy way to check for problems of this
nature in the databases?

Also - I am planning on generating a script from the database on the
old server that scripts the triggers and constraints, and then use
Query Analyser to run this script against the database on the new
server. Is this the best way to add these objects back into databases
that are already populated with data and running on a live server?

In in a pretty bad position, but at least these are databases that are
not accessed too frequently, so I'm hoping any referential integrity
problems will be minor.
Any help or advice would be greatly appreciated.<jason_s_ford@.hotmail.com> wrote in message
news:1097705795.080513.155750@.c13g2000cwb.googlegr oups.com...
>I have several sql server databases that were recently moved to a new
> server. In the process of migrating the databases, any triggers and
> constraints attached to tables were removed on accident. I need to add
> these objects back into the databases, however I'm worried that I will
> have problems with referential integrity since there is a chance
> someone may have deleted or updated a record that should have cascaded
> changes to other tables but did not since the triggers and constraints
> were missing. Is there an easy way to check for problems of this
> nature in the databases?

Not really, since in order to check this you would need to know the
primary/foreign keys that should be there anyway. So you might as well just
add them back again, and see if you get any errors. Triggers are a bit more
of a problem, but if you're only using them for RI, then hopefully adding
the foreign keys will pick up any problems. If you have more complex
business rules in triggers, then there are no real shortcuts except to work
through your logic and see if any data is incorrect - hopefully you don't
have too many...

> Also - I am planning on generating a script from the database on the
> old server that scripts the triggers and constraints, and then use
> Query Analyser to run this script against the database on the new
> server. Is this the best way to add these objects back into databases
> that are already populated with data and running on a live server?

That's fine. If the script is large, make sure you run it in chunks to avoid
getting too many errors back in one go. And of course try it out on a test
copy of the database first.

> In in a pretty bad position, but at least these are databases that are
> not accessed too frequently, so I'm hoping any referential integrity
> problems will be minor.
> Any help or advice would be greatly appreciated.

For the future, you might want to review how you move databases to new
servers (backup/restore is usually an easy option, and you can't lose
anything that way), and perhaps look at some schema comparison tools, which
can help you find and fix schema issues. This one is quite good, but there
are plenty of others:

http://red-gate.com/SQL_Compare.htm

Simon

No tool to upgrade Access databases

sql server 2k has a tool to upgrade Access databases. I can't find any similar tool in sql server 2005. Am I missing something?

dennist

Do you mean the Import/Export Wizard? This will copy some of the schema and the data from an Access Database. Right click on a Database in SSMS and select import.

If you mean the Access Upsizing wizard this is part of Access and we are still closing those plans.

-Euan

Please reply only to the newsgroup/forum so that others can benefit. When posting,please state the version of SQL Server being used and the error number/exact error message text received, if any.

Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

This posting is provided "AS IS" with no warranties, and confers no rights.